000029425 - How to clean up AFX logging tables in RSA Via Lifecycle & Governance

Document created by RSA Customer Support Employee on Jun 14, 2016•Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000029425
Applies ToRSA Product Set: Identity Management and Governance, RSA Via Lifecycle and Governance (L&G), Aveksa ACM
RSA Product/Service Type: Access Fulfillment Express (AFX)
RSA Version/Condition: 6.9
Platform: Suse Linux
IssueThere is currently no available feature to automate the retention date range or file size of AFX logs in version 6.9 and earlier. AFX logs can get quite large when viewed through UI via AFX > Connectors > Logs and there is no current automatic mechanism to purge the table that stores AFX log entries.  
Tasks

Should tablespace growth due to AFX logging become an issue, the below SQL can be leveraged to clean up and shrink the involved tables.


DELETE FROM T_AV_AFX_LOG_MESSAGE where TRUNC(CREATE_DATE)<'01-JAN-14'; 
commit;
alter table T_AV_AFX_LOG_MESSAGE enable row movement; 
alter table T_AV_AFX_LOG_MESSAGE shrink space; 
alter table T_AV_AFX_LOG_MESSAGE disable row movement;

 
The first 2 SQL statements above will delete all rows in the table T_AV_AFX_LOG_MESSAGE which were created before January 1, 2014 and then commit the transaction. SQL Statements 3-5 will release the deleted rows from the table from a table size perspective.
Please note if you choose to proceed as above, you will no longer be able to see AFX Log messages before January 1, 2014 (or whatever data you enter in the WHERE clause of TRUNC(CREATE_DATE)<'01-JAN-14')
ResolutionRetention control and automate cleanup functionality has been implemented in 6.9.1.

Attachments

    Outcomes