Question
ANZ Asia Pacific Division
IN
Last activity: 12 Oct 2018 14:58 EDT
AES 7.1.7 and AES 7.2 health check for purging (clean up) the old AES data
how to check the AES 7.1.7 and AES 7.2 clean up happening or not , Please advise for health check of purging the AES data
***Edited by Moderator Marissa to update categories***
Pegasystems Inc.
US
The following article has lots of useful AES troubleshooting tips:
https://collaborate.pega.com/discussion/troubleshooting-deferred-write-operations
Including the query to run to see if the alert and exception data in the DB is being trimmed or not:
Modify the following pseudo SQL to see if data is being correctly trimmed in the alert and exception table. Modify the pseudo SQL as required by your database management system.
The following article has lots of useful AES troubleshooting tips:
https://collaborate.pega.com/discussion/troubleshooting-deferred-write-operations
Including the query to run to see if the alert and exception data in the DB is being trimmed or not:
Modify the following pseudo SQL to see if data is being correctly trimmed in the alert and exception table. Modify the pseudo SQL as required by your database management system.
-
Select count(*) from <data-schema>.pegaam_alerts where pxcreatedatetime < ‘fourteen-days-ago’;
-
Select count(*) from <data-schema>.pegaam_exceptions where pxcreatedatetime < ‘fourteen-days-ago’;
Pegasystems Inc.
US
Be aware that database may still grow even if clean-up / purge is working properly as the DBMS may not reclaim space from deleted rows automatically - especially space from the blob / pzpvstream columns. It may be necessary to engage a DBA to schedule DBMS maintenance jobs to reclaim / reorg / vacum / alter-table-move / etc tables. If your DBMS supports partitioning it is possible to partition specific tables and periodically truncate partitions to force space reclamation.