IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse range partitioning > Specify range partitioned tables for the Summarization and Pruning Agent
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configuration parameters
There are three parameters that must be set in the Summarization and Pruning Agent environment file.
For the KSY_DEFAULT_TABLE_CONTAINER and KSY_DEFAULT_INDEX_CONTAINER, see Environment variables in Specify where tables and indices are created.
- KSY_PARTITION
- Controls whether partitioning is enabled (Y) or disabled (N). When disabled, non-partitioned tables and non-partitioned indices are created and the old pruning behavior is in effect. When enabled, partitioned tables and partitioned indices are created (if supported by the database), and partitions are maintained. The default setting is N.
- KSY_PARTITIONS_UPWARD
- Number of partitions to maintain after the current date. This allows for an outage to occur and not cause disruption on the monitoring system, permitting agents to upload their collected historical data. Minimum value of 1, maximum value of 10. The default setting is 10.
- KSY_GROUP_BY_THRESHOLD
- Number of past days used in the Summarization and Pruning agent discovery query. This is used to improve the Summarization and Pruning agent runtime and to limit the number of partition locks placed on the table. The default setting is 0.
After the variables in the Summarization and Pruning Agent are set, schedule the Summarization and Pruning Agent to run at least every day. Only the Summarization and Pruning Agent is responsible for managing the partitioned tables. Otherwise insertions into tables will fail if there is not a partition defined for the data being inserted.
Partitions are added to the existing partitioned detailed tables, and the existing summarized tables only if the Summarization and Pruning Agent is running and when the upward partition(s) do not exist yet. If the Summarization and Pruning Agent runs every day, a new partition should be added every day at the detail, hourly, and daily level. Weekly aggregated tables will get a new partition once a week, monthly aggregated tables once a month, quarterly aggregated tables once a quarter, and yearly aggregated tables once a year.
Partitions are dropped or detached by the Summarization and Pruning Agent when pruning settings in the Tivoli Enterprise Portal exist against the corresponding attribute group.
Tip: SQL Queries that use the partitioned tables will not require any modification, although queries should always use the partitioning key, usually the WRITETIME table column, to avoid scanning all partitions. Failure to due so can result in locks being acquired which can prevent partitions from being dropped when the Summarization and Pruning Agent is running. Only the following values can be used with the partition key columns:
- Equals
- Not equals
- Less than
- Greater than
- Less than or equals
- Greater than or equals
If a function is used, the database query optimizer will not be able to eliminate partitions.
SQL queries against a DB2 z/OS Tivoli Data Warehouse database should use uncommitted reads via WITH UR to prevent unnecessary locks and failures during the Summarization and Pruning Agent runs.
Errors are treated as any regular error, meaning that the operation being attempted will fail and result in that upload (if Warehouse Proxy Agent) or aggregation (Summarization and Pruning Agent) to fail. Errors are reported via the appropriate Tivoli Data Warehouse agent and available for situation processing and workspaces.
Parent topic:
Specify range partitioned tables for the Summarization and Pruning Agent