Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

AES data retention is not working as defined

SA-42992

Summary



Autonomic Event Services (AES) Data is not cleaned up even after the retention date, as the cleanupAESData agent fails.


Error Messages



8/23/17 9:55:34:700 EDT] 0000012b SystemOut O 2017-08-23 09:55:34,690 [ WebContainer : 39] [ STANDARD] [ AES:07.13] (l.access.ConnectionManagerImpl) ERROR your_host|your_IP aesdeveloper - Not returning connection 8 for database "pegadata" to the pool as it previously encountered the following error
User ID: aesdeveloper
Last SQL: DELETE FROM PEGA7RULES.pegaam_alert "PC0" WHERE ( ( DAYS(CURRENT_TIMESTAMP)-DAYS("PC0".GENERATEDDATETIME) > (CAST(? AS INTEGER) + CAST(? AS DECIMAL(31,10))) ) ) AND "PC0".pxObjClass = ?
com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.17.29


Steps to Reproduce



Query the Database and note that older data is retained.


Root Cause



A defect or configuration issue in the operating environment.

The cleanup AES data Agent that is supposed to remove 'past retention days' records from AES tables was failing.


Over time large number of records have accumulated into the table and now the delete SQL fails as the database runs out of transaction log space.

Resolution



Here’s the explanation for the reported behavior:

Increase the transaction log space size or reduce the amount of data to be cleaned by manually running delete statements.

Suggest Edit

Published November 3, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us