Performance of 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 datastore is in need of maintenance. You might, for example, note that your DB2® transaction logs are filling up. You might see gaps in the data in the middle or at the end where no historical data is available for a specified collection period. This problem also manifests itself as degraded performance, such that database inserts require an unusually long period of time. Inserts must be completed between display intervals. Operations need to completed before the next collection interval to prevent the persistent data store from wrapping.
Adhere to the following guidelines to prevent these problems:
- Practice good database maintenance. Schedule regular maintenance outages and reorganize your IBM® Tivoli® Data Warehouse tables, including the summarization and pruning tables, using a command to reorganize table storage, such as (in DB2) the REORG command.
- Review the appendix “Relational database design and performance tuning for DB2 database servers” appendix in the IBM Tivoli Monitoring: Administrator's Guide to learn about DB2 tuning considerations.
- Change your Send to warehouse setting from daily to hourly.
- Increase the size of your database transaction log.
- To eliminate gaps in displays of historical data less than 24 hours old, increase the size of the persistent data store on the mainframe.