Tivoli Reporting and Monitoring table issue

After installation of Tivoli reporting and monitoring for TSM, you can't get in with following errors:

"RQP-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions' status='-201'." and "UDA-SQL-0196 The table or view "KSK_STORAGE_POOL" was not found in the dictionary"

This is because the KSK tables are not create correctly during the installation process and there is no error to indicate that. You will need to manually create the tables by:

1. Open the MTEMS and stop and restart the TSM Agent Instance

2. Open a command prompt and go to the following directory:

If on windows: C:\IBM\ITM\bin

If on Unix/Linux: /opt/tivoli/tsm/reporting/itm/bin

3. Run the following command:

tacmd.exe histconfiguregroups -u SYSADMIN -w <SYS_PWD> -t KSK -o "<attr_grp>"

-i 1h -c 1h -d YQMWDH

<SYS_PWD> is the password for SYSADMIN user ID.

Run this command for each of the following attr_grp (make sure you use the " "

around the attribute group name)

"KSK CLIENT NODE STORAGE"

"KSK CLIENT MISSED FILES"

"KSK CLIENT NODE STATUS"

"KSK DATABASE"

"KSK SCHEDULE"

"KSK STORAGE POOL"

"KSK TAPE USAGE"

"KSK TAPE VOLUME"

"KSK NODE ACTIVITY"

"KSK SERVER"

"KSK STORAGE DEVICE"

"KSK ACTIVITY LOG"

"KSK OCCUPANCY"

"KSK REPLSTATUS"

"KSK REPLDETAILS"

"KSK ACTIVITY SUMMARY"

4. Run the following command:

./tacmd histstopcollection -u sysadmin -w <sysadmin_pwd> -t "Tivoli Storage

Manager" -o "<attr_grp>"

./tacmd histstartcollection -u sysadmin -w <sysadmin_pwd> -t "Tivoli Storage

Manager" -o "<attr_grp>"

Do this for each attr_grp below:

"KSK CLIENT NODE STORAGE"

"KSK CLIENT MISSED FILES"

"KSK CLIENT NODE STATUS"

"KSK DATABASE"

"KSK SCHEDULE"

"KSK STORAGE POOL"

"KSK TAPE USAGE"

"KSK TAPE VOLUME"

"KSK NODE ACTIVITY"

"KSK SERVER"

"KSK STORAGE DEVICE"

"KSK ACTIVITY LOG"

"KSK OCCUPANCY"

"KSK REPLSTATUS"

"KSK REPLDETAILS"

"KSK ACTIVITY SUMMARY"

4. In the MTEMS, stop and restart the warehouse proxy agent

5. Verify the data exists in each workspace in the TEPS for this TSM Instance

6. After 2-3 hours check the warehouse proxy agent and see if any data has been stored.

It will show in this workspace if any data has been saved to the WAREHOUS database. Remember you have to wait a few hours before data will be stored in the warehouse database. 

Tivoli Warehouse file system space issue

You may find /opt/tivoli/tsm/reporting file system fills up really fast and doesn't matter how you change the prune history data.

Try to locate the biggest file, normally you will find this file: KSKTAPEUSA where is @ /opt/tivoli/tsm/reporting/itm/lx8266/sk/hist/instance_name

Resolving the problem:
1) Stop Tivoli collection agent
itmcmd agent -o instance_name stop sk
2) Delete the file - No worries, it will be recreated later and this is only a temp file.
rm KSKTAPEUSA
3) Start agent again
itmcmd agent -o instance_name start sk

The reason behind is because the KSKTAPEUSA temp file was growing faster than the ITM pruning process and caused the issue.

Tivoli admin center reporting error

Once you configured Tivoli reporting and monitoring and integrated with TSM AC, you may get the following error sometimes when you tried to access reporting function in AC:

Problem:

DPR-ERR-2109 The dispatcher cannot service the request at this time. The dispatcher is still initializing. Contact your administrator if this problem persists.

Cause

The derby database is no longer valid and needs to be initialized.

To fix it: 

1. Stop Tivoli Portal server

2. # export JAVA_HOME=/opt/IBM/tivoli/tipv2/java

3. # /opt/IBM/tivoli/tipv2Components/TCRComponent/cognos/bin/derby.sh start 1527

4. # /opt/IBM/tivoli/tipv2Components/TCRComponent/cognos/derby10.1.2.1/bin/ij.sh

5. ij> connect 'jdbc:derby://localhost:1527/cm;create=true;user=cognos;password=cognos';

6. ij> run '/opt/IBM/tivoli/tipv2Components/TCRComponent/cognos/contentstore/init_contentstore.sql';

7. ij> disconnect;

8. ij> quit;
9. Start Tivoli Portal server