Performance for the Tivoli Data Warehouse database is degraded or there are gaps where historical data is unavailable for a specified collection period

A number of symptoms indicate that your database or persistent data store is in need of maintenance. You might, for example, observe that your DB2® transaction logs are filling or that no historical data is available for a specified collection period.

You might also see degraded performance, such that database inserts take a very long time. To prevent the persistent data store from wrapping, inserts must complete between display intervals and operations must complete before the next collection interval.

There are several steps that you can take to prevent these problems:
  1. Practice good database maintenance. Schedule regular maintenance outages and reorganize your Tivoli Data Warehouse tables, including the summarization and pruning tables. Use a command to reorganize the table storage, such as the REORG command in DB2.
  2. Refer to the Relational database design and performance tuning for DB2 database servers topic in the Performance Tuning / Tivoli® Data Warehouse section of the IBM® Tivoli Monitoring: Installation Guide for database tuning information.
  3. Change your Send to warehouse setting from daily to hourly.
  4. Increase the size of your database transaction log.
  5. To eliminate gaps in displays of historical data less than 24 hours old, increase the size of the persistent data store on the mainframe using the Kpp_PD_CYL parameter in PARMGEN to change the PDS size in the agent and the KDS_PD_CYL parameter in PARMGEN to change the PDS size in the Tivoli Enterprise Monitoring Server.