Validation of LDAS database functionality

The steps described below are to be executed under database user ldas.

At times, the database software have to be upgraded to new versions or have fixpaks applied, or the databases may have to be restored after a disk failure etc.

Remember to configure the database manager and databases for LDAS system as documented Creation of an LDAS database: configuring for LDAS applications'. You can use the script updatecfg.tcl in /ldas/doc/db2/doc/text to update all the database configurations listed in the LDAS configuration file /ldas_outgoing/metadataAPI/LDASdsnames.ini.

The following list the tests to be done to verify the integrity of the LDAS database functionality after such changes.

1. Check insertion of all tables - the Database insertion test inserts into the test database you specified data for all ldas tables, extracts the data inserted and validates the values are the same as the input ilwd data. This test should complete without errors and performance should not be degraded under normal circumstances.
2. Check databse web page update - Database web pages should be updated accordingly with the insertions and that there are no errors in the file /ldas_outgoing/cntlmonAPI/db2utils.log.
3. Submission of LDAS jobs - submit jobs like putMetaData, putStandAlone and dataPipelines that insert into the database through cmonClient test panel to verify that data can be inserted.
4. Creation/Recreation of database through user ldas - using cmonClient utilities function you should be able to create or recreate a test database without errors.
5. Run IBM DB2 utility runstats on each database to gather database statistics to improve query performance. You use the script runstats.tcl in /ldas/doc/db2/doc/text to update a single database supplied as argument or all ldas databases listed in the LDAS configuration file /ldas_outgoing/metadataAPI/LDASdsnames.ini.