WORKAROUND
None
STATUS
Upgrade the Performance Analysis for DB2 agent and middleware to 7.0.506 or higher, then change the default of 2 old time keys to be deleted (by setting PADB2_DELETE_MAX_EXPIRED_REC environment variable on Middleware machine) requires some stderr log analytic.
- PADB2_DELETE_MAX_EXPIRED_REC environment variable is set in Windows Control Panel\System and Security\System, or if Middleware is on *NIX flavor OS, use set env or export
There are two message sets in the stderr log that help deciding the value for _PADB2_DELETE_MAX_EXPIRED_REC:
- Level X has Y keys of expired records, where the smallest X in the set reflects the 1h aggregation level.
For example
Level 6 has 525 keys of expired records.
- If the number of the keys in the same level message is constantly decreased, the old records are deleted from the DB properly.
- If the message does not appear, it means that the old records have already deleted.
- If the number is going up, the number of key deleted per thread invocation must be changed!
- Delete time expired records for level: X.
Where the smallest X represents the 1h aggregation level.
For example:
Mon May 11 10:09:18 2015: Delete time expired records for level: 7
Mon May 11 10:14:59 2015: Delete time expired records for level: 8
Looking at the time difference between two messages shows how long it takes to delete the expired records per thread invocation.
Be sure, that the number of deleted time keys is bigger than the number of new added aggregation points.