000036744 - RSA Identity Governance & Lifecycle Role Collector (RDC) fails with ORA-30926 error

Document created by RSA Customer Support Employee on Oct 9, 2018Last modified by RSA Customer Support Employee on Oct 9, 2018
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000036744
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.0.2, 7.0.1
IssueThe RSA Identify Governance and Lifecycle Role Collector (RDC) shows as Failed in the step Role Data Relationship Processing.   The Task Progress shows that the processing is In Progress in Step 9/12: Relationship Processing Update Master Relationships.

In addition, in the Admin Errors for Run, the detailed errors for the run may show the following:
 

EC[212] Context[RunlD-502 RDC(Name=MyRoleCollector, ID=1)] Message[Role Data validation:
Membership Data is Invalid. Specified user(s) not found in associated IDC]


The following log event is logged in the aveksaServer.log file:.
 

08/24/2018 12:04:42.472 INFO (Exec Task Consumer#9) [com.aveksa.server.db.persistence.PersistenceServiceProvider]
executeCallableStatement giving up after hitting SQLException:
ORA-30926: unable to get a stable set of rows in the source tables
ORA-06512: at "AVUSER.RDC_UPDATE_MASTER_TABLES", line 490
ORA-06512: at "AVUSER.RDC_DATA_COLLECTOR", line 182
ORA-06512: at "AVUSER.RDC_DATA_COLLECTOR", line 297
ORA-06512: at line 1
...
08/24/2018 12:04:42.472 WARN (Exec Task Consumer#9) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper]
SQL Error: 30926, SQLState: 99999
08/24/2018 12:04:42.472 ERROR (Exec Task Consumer#9) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper]
ORA-30926: unable to get a stable set of rows in the source tables
ORA-06512: at "AVUSER.RDC_UPDATE_MASTER_TABLES", line 490
ORA-06512: at "AVUSER.RDC_DATA_COLLECTOR", line 182
ORA-06512: at "AVUSER.RDC_DATA_COLLECTOR", line 297
ORA-06512: at line 1


 
CauseThis issue occurs with certain types of Role Data.

This is a known issue in the following versions:
  • RSA Identity Governance and Lifecycle 7.0.1
  • RSA Identity Governance and Lifecycle 7.0.2 
  • RSA Identity Governance and Lifecycle 7.1.0
ResolutionThis issue is resolved in the following patches
  • RSA Identity Governance and Lifecycle 7.0.1

If you are using 7.0.1, please upgrade to a current version.



  • RSA Identity Governance and Lifecycle 7.0.2 P10
  • RSA Identity Governance and Lifecycle 7.1.0 P04
WorkaroundThere is no work around for this issue, but the error only occurs when the system is doing collections on previously collected data.  The failure does not occur on the first run of the Role Collector and does not occur if the Role Collector is targeted for a Full Refresh for Relationships.

You can force the collector to do a Full Refresh for Relationships by making a configuration change (it has to be a major change such as mapping attributes or resolution rules), and then changing the configuration back to the original.  You can check to make sure this is set by displaying the list of Roll Collectors with all columns displayed and checking the Requires Full Refresh column.
 
User-added image

Attachments

    Outcomes