返回
-
标题
Purge process in PA repository not functioning -
说明
The Performance Analysis does not purge -
原因
The purge process is not running successfully.
PADB2 Repository manager automatically purges old time key records.In some situations as high load on the Repository and internal dependencies the purging mechanism might be slow and sometimes purging is not available.Starting from 7.0.5.6 Agent version and up the purging mechanism is enhanced and can be controlled by the user.- By default, two old time keys per aggregation thread invocation will be deleted
- The number of time keys deleted per thread invocation can be increased or decreased. Note that the Default should be sufficient in most cases
- PADB2_DELETE_MAX_EXPIRED_REC environment variable (on Middleware machine) controls the # of time key deletions
-
解决办法
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 exampleLevel 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: 7Mon May 11 10:14:59 2015: Delete time expired records for level: 8Looking 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. -
缺陷ID
SCDBII-1129