IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse range partitioning

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Specify range partitioned tables for the Summarization and Pruning Agent

Table partitioning only occurs when new tables are created in the Summarization and Pruning Agent. There is no change to existing tables that were created before Tivoli Monitoring V6.3.

You can configure database table partitioning from the agent configuration GUI, by editing the environment file, or through the Command-Line Interface (for more information, see the Warehouse Summarization and Pruning Agent User's Guide.)

When partitioning is enabled, the Summarization and Pruning Agent performs the following functions:

If you partition a table without following the Tivoli Data Warehouse partition naming scheme, the Summarization and Pruning Agent will not take advantage of the partitions and data pruning will use the old method of deleting rows in the table.

Each time the Summarization and Pruning Agent is executed, it looks to see if it needs to create a new summary table. The table is only created if it doesn't already exist. Each partition other than the catch all, only contains one day of data. However, separate partitions are created as follows:

The catch all partition might contain data older than the pruning window that is configured. The data will not be pruned until the catch all partition is dropped and recreated.

Figure 1. Configure Summarization and Pruning Agent - Database Table Partitioning

  1. Number of future partitions to maintain must contain a value, regardless of whether or not Database Table Partitioning is selected.

  2. If you are using DB2 for Linux, UNIX, and Windows, the DB2 LOCKTIMEOUT must not be set to the default value of -1, which means infinite wait. Adding and detaching partitions require a table lock, which might not be possible to obtain if there is a lot of activity on the table causing locks to be held. Not setting a table lock timeout can cause the Summarization and Pruning Agent to stop processing tables while it is waiting for the table lock.


Parent topic:

Tivoli Data Warehouse range partitioning

+

Search Tips   |   Advanced Search