SecurID® Governance & Lifecycle Knowledge Base
Find answers to your questions and identify resolutions for known issues with knowledge base articles written by SecurID Governance & Lifecycle experts.
Article Number
000030107
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 6.9.1, 7.x
RSA Version/Condition: 6.9.1, 7.x
Issue
When collections run in RSA Identity Governance & Lifecycle, a certain number of raw data sets are kept for each collector run in the T_DC_SOURCEDATA* tables. The parameter that determines how many raw data sets to keep per each collector before purging them is a custom parameter called CollectorRawDataSetsToKeep.
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.
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
If you are running into performance and/or disk space issues due to the size of your T_DC_SOURCEDATA* tables, RSA Identity Governance & Lifecycle Support recommends that you retain two to three raw data sets per collection rather than the default value of five.
Follow the steps below to modify this value:
Image description
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:
Image descriptionNow 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,
In this article
