Raw Data counts and Task Result counts in Role Collector data runs are sometimes inconsistent in RSA Identity Governance & Lifecycle
2 years ago
Originally Published: 2020-03-13
Article Number
000042619
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 
Issue
When looking at data runs for role collections, the numbers in the task results do not always match the numbers in the raw data results.

The following is an example of a role collector run where the number of new roles collected differs in the task results and the raw data. The task results show zero new roles collected and the raw data for the same role collection run shows three new roles collected. Yet both screens show a total of seven roles collected.

 
User-added image
 
User-added image

 
Cause
The cause of these discrepancies is that the columns New/Changed//Reprocessed do not exactly reflect the same data and therefore do not necessarily equate to each other.
 
Resolution
The numbers in the New/Changed//Reprocessed columns of the task results section represent good data, i.e. those records that made it into the master tables. The numbers in the raw data fields represent both good and bad data (i.e., all the data that made it into the master tables and all the data that failed to make it into the master tables.)

For example, the New field of the raw data includes new entities as well as entities that were previously collected but need to be re-processed for various reasons. In this example the three entities labelled New in the raw collected data were previously collected but did not successfully get moved to the master tables and need to be reprocessed. The two records in green did not pass the reference resolution requirements because the owners did not exist in RSA Identity Governance & Lifecycle. The entity in red contains data in an invalid format and could not be stored in the raw data table.
 

Related Articles

Trending Articles

Don't see what you're looking for?