000033887 - How to prune data that is no longer needed in RSA Identity Governance and Lifecycle

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

Article Content

Article Number000033887
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Product/Service Type: Appliance
 
IssueAt a number of customer sites we are seeing larger amounts of data.  Often some of this data does not appear to be vital to auditors and while important to ACM while doing the work, they are probably candidates for cleanup after the work is complete.  Similarly, there are a number of tables that may hold a few months worth of data instead of holding data forever. We will be seeing how to prune, that is, cleanup what is not needed long term, from the data in RSA Via Lifecycle and Governance.
Resolution

Access Request Pruning


Using your SQL tool of choice, run the stored procedure providing a date we should prune from the database.  We will clean data for any requests that are in a final state created on or before this date.


EXECUTE Data_Retention_Pkg.Prune_Access_Request(TO_DATE('27-08-2016','DD-MM-YYYY'));

This example will remove the unneeded data for any completed/cancelled change requests that was created on or before August 27, 2016. You could also use SYSDATE – n days rather than type an explicit date in if you wanted to do a relative n days type of call.
EXECUTE Data_Retention_Pkg.Prune_Access_Request(SYSDATE-30);


Monitoring Pruning


This will remove all logging information older than a given date.  Note we do keep the information used for the run detail pages.


EXECUTE Data_Retention_Pkg.Prune_Application_log(TO_DATE('27-08-2016','DD-MM-YYYY'));

Attachments

    Outcomes