Optimal value for CollectorRawDataSetsToKeep in RSA Identity Governance & Lifecycle
Originally Published: 2015-04-21
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 6.9.1, 7.x
Issue
The default value of the CollectorRawDataSetsToKeep parameter is five.This means that each individual collector will retain the last five good runs of raw data in the T_DC_SOURCEDATA* tables.
Over time, as more and more collectors are added to directories and applications in RSA Identity Governance & Lifecycle and as the amount of data collected per existing collectors increases, the amount of raw data stored increases which can negatively impact performance. This can result in increased processing times in order to both gather the data during the collection steps and manipulate the data during the processing steps of the overall collection.
This RSA Knowledge Base Article describes how to modify the custom parameter CollectorRawDataSetsToKeep.
Resolution
Follow the steps below to modify this value:
- Check the existing value by logging into SQL*Plus as avuser and executing the following SQL:
select VALUE from T_SYSTEM_SETTINGS where PARAMETER='CollectorRawDataSetsToKeep'
If the value returned is 2, then stop as you have already completed these steps and this is the minimum recommended value.
- Log in to the RSA Identity Governance & Lifecycle application as the AveksaAdmin user.
- Navigate to Admin > System > Settings tab > Edit.
- Scroll to the bottom of the page and add the parameter CollectorRawDataSetsToKeep with a value of 2 > Save > OK.
After adding this parameter, you will see:
Now on every collector run, if database statistics runs successfully, the number of runs stored per collector in the T_DC_SOURCEDATA* tables will be reduced to the last two runs.
NOTE: Some customers find that their daily/nightly collections continue beyond the default scheduled time of 12:30 AM daily for the database statistics job. This setting can be modified under Collectors > Scheduling > Tasks tab (DB Statistics Refresh) > Edit. For more information on when and how to modify this schedule, please refer to RSA Knowledge Base Article 000034041 -- How to manage raw data cleanup in RSA Identity Governance & Lifecycle,
Related Articles
How to remove entitlements of a decommissioned application from user access in RSA Via Lifecycle and Governance 74Number of Views What is the Change Request Pending Submission State in RSA Identity Governance & Lifecycle 199Number of Views RSA Identity Management and Governance Change request item stays in Pending Verification even after successful collection … 337Number of Views What are the custom attribute data type limits in RSA Identity Governance & Lifecycle 122Number of Views A completed change request to remove Aveksa Application/Directory entitlements from a user does not remove the access from… 209Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?