The TBSM Database Checker Utility verifies that the TBSM databases created with the DbConfig install utility are ready for use by the TBSM Data server.
The TBSM Database Checker Utility will verify that the TBSM databases created with the DbConfig install utility are ready for use by the TBSM Data server. The checking includes:
1) Verifying that JDBC connections can be made to the database. For example, DB2 may not be correctly configured for TCP/IP. The tool will list possible reasons for connection failures.
2) Verifying that the userid to be specified in the TBSM datasource can connect to the database and has DBADM authority with privileges to access data. DBADM authority is a sufficient authorization to ensure the Data Server and XML Toolkit can perform all required tasks.
3) Verifying that all expected schema, tables, views, triggers, indexes, and functions are defined in the database(s).
4) Verifying that the databases do not convert empty strings to null, as is done when Oracle compatibility options are set in DB2. This will cause TBSM to fail with SQL exceptions, as empty strings are inserted into some database columns that are not nullable.
IBM Tivoli Business Service Manager Version 6.1
The TBSM Database Checker Utility zip file (TBSMDBChecker_61GA.zip) is attached to this document under Download Package. The TBSM Database Checker Utility zip file must be unzipped into the location where DbConfig installed the schema creation files and utilities. This defaults to /opt/IBM/tivoli/tbsmdb on Unix or C:\ibm\tivoli\tbsmdb on Windows. The contents must be unzipped into the "tbsmdb" directory and will add new parts to the "bin" and "tools" directories found in "tbsmdb".
The database checker utility is found in the bin directory relative to the install directory created by DbConfig. This is the same location as the tbsm_db.bat(sh) utility. Run TBSM_Check_DB.bat(sh) from a command prompt and provide input as follows when prompted:
Enter administrative database userid. This user should have SYSADMIN or SECADMIN authority and will be used to check authority of data server userid:
(Provide a userid with DB2 SYSADMIN and/or SECADMIN authority. It is used to verify the connection to the database and then to check that the TBSM data server userid specified below has DBADM authority with privileges to access the data.)
Enter the password for administrative database userid adminuser:
(Provide the password for adminuser, which is the userid you specified for the previous prompt.)
Enter database userid that will be used to connect the database from the TBSM data server: [adminuser]
(Provide the userid that will be used to connect the database from the TBSM datasource defined in the the TBSM data server. This is the userid that will be provided during the install of the TBSM data server.
Just hit enter to use adminuser, which is the default value, as shown in the brackets at the end of the prompt.)
Enter the password for data server database userid tbsmuser: [adminpassword]
(Provide the password for tbsmuser, which is the userid you specified for the previous prompt. Just hit enter for the default, the administrative userid password provided above, as shown in the brackets at the end of the prompt.)
Enter database(s) to be checked:
S = Service Model
H = Metric History
M = Metric Marker
(Make a selection for the database(s) to be checked. To check all the databases take the default value by just hitting enter. To check a single database, enter S, H, or M. You must enter only one selection or take the default of ALL, otherwise the utility will not continue.)
The utility will indicate success or failure at completion of the Ant script called by the utility. You should check the logs for warning messages even if the utility reports success. Switch to the logs directory relative to the DbConfig install directory
and look for the following logs, depending on which databases you requested to be checked: