Miscellaneous conditions test

Test Objective

This is a series of tests that exercises metadataAPI exception handling of the following:

     dbException:putMetaData:optional group name 1 PASSED
     dbException:putMetaData:optional group name 2 PASSED
     dbException:putMetaData:optional group name 3 PASSED
     dbException:putMetaData:test no group/table name PASSED
     dbException:putMetaData:test no seqid PASSED
     dbException:putMetaData:single set insertion PASSED
     dbException:putMetaData:test double set insertion PASSED
     dbException:putMetaData:bad data in ilwd PASSED
     dbException:putMetaData:skip comments metadata0101 PASSED
     dbException:putMetaData:skip comments comments PASSED
     dbException:getMetaData:notInvalidElement PASSED
     dbException:metadata:putMetaData:invalid data rollback PASSED
     dbException:getMetaData:invalid data rollback validate PASSED
     dbException:metadata:putMetaData:duplicate data rollback PASSED
     dbException:getMetaData:duplicate data rollback validate PASSED
     dbException:dataPipeline:non-standard DSO inspiral error PASSED
     dbException:dataPipeline:non-standard DSO slope error PASSED
     dbException:dataPipeline:non standard DSO inspiral ok PASSED
     dbException:dataPipeline:non standard DSO slope ok PASSED
     dbException:putMetaData:bad database name putMetaData PASSED
     dbException:getMetaData:bad database name getMetaData PASSED
     dbException:getMetaData:uppper case database name getMetaData PASSED
     dbException:putMetaData:uppper case database name putMetaData PASSED
     dbException:dataPipeline:dbquality channel on test database ok PASSED
     dbException:dataPipeline:gaps no database data PASSED
     dbException:putMetaData:ligolw exception from bad xml PASSED
     dbException:getMetaData:frame not supported PASSED
     dbException:getMetaData:invalid ilwd format PASSED
     dbException:getMetaData:getMetaData outputformat default PASSED
     dbException:putMetaData:unknown table PASSED
     dbException:putMetaData:out of range PASSED
     dbException:dataPipeline:Unofficial DSO PASSED
     dbException:putMetaData:database deadlock rollback PASSED
     

APIs affected by this test

• managerAPI: directs processing of the insertion user commands to the ligolwAPI and metadataAPI and returns the user command status to the user.
• ligolwAPI:
  • Retrieves the data to be ingested from the specified url to ilwd object and sends the ilwd to the metadataAPI for insertion.

• metadataAPI:
  • insert the metadata ilwd data from ligolwAPI into the specified database.

Setup

1. Using ligotools

   If ligotools is desired, check that ligotools is mounted:

           ldas:ldas:ldas-dev.ldas-dev:test> df /ligotools
           Filesystem           1K-blocks      Used Available Use% Mounted on
           /dev/dsk/c3t1d0s6    498316151 326700089 171616062  66% /export
           

   Set up a default ldas account and password via ligotools utility ldaspw. Currently ligotools does not support job submission via globus sockets.
2. Default is use the LDAS ldasJob package included in installation. Globus socket is supported.
3. Test driver dbException.tcl is found in /ldas/testbin and is part of ldas installation. Supporting generic test scripts are in /ldas/lib/test and /ldas/libexec.

The following test data files are part of the installation:

optname1.xml optname2.xml optname3.xml
test_bare_names.xml test_no_seqid.xml file4733_1.xml
try1.xml baddata.xml metadata0101.xml
txn2.ilwd rollback1.ilwd rollback.ilwd
out-of-range.ilwd nulldata.binary.ilwd

Test Execution

1. Login to site gateway box e.g. dev, as user ldas
2. cd <your work directory>
Usage: /ldas/testbin/dbException.tcl [options] >& dbException.log &

Options described are specific to dbException but when running generic options are included.

Option	Description
--database	database name at a site e.g. dev_1 or ldas_tst

e.g. with globus sockets:

        
   	dbException.tcl --site dev -debug 0 -verbose lpse --enable-globus 1 --enable-gsi 1 
    	--database dev_1 </dev/null >& dbException.log &

and with tcl sockets:

        dbException.tcl --site dev -debug 0 -verbose lpse --enable-globus 0 --enable-gsi 0 
        --database dev_1 </dev/null >& dbException.log &

To enable debugging, set debug level to 1 or greater:

        
   	dbException.tcl --site dev -debug 1 -verbose lpse --enable-globus 1 --enable-gsi 1 
    	--database dev_1 --qa-debug-level 1 </dev/null >& dbException.log &

• At times the database data needs to be cleared out again for subsequent tests. This is done inside the test script.
• For deadlock/rollback a database connection needs to be maintained on the database server so a helper script is used to accomplish this: rundb2cmds.tcl
  dbException.tcl directs the execution of db2 commands by rundb2cmds.tcl on the database server host via ssh pipe.

Test Validation:

If all the data has been cleared out successfully, the results obtained for each transaction to ldas should match the expected result in the script. e.g.

            dbException.tcl:        Total   33      Passed  33      Skipped 0       Failed  0