|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle|
RSA Version/Condition: 7.0.2, 7.1.0
|Issue||RSA Identity Governance & Lifecycle unification fails with the following error in the aveksaServer.log file:|
05/03/2018 14:10:51.048 INFO (Exec Task Consumer#1) [com.aveksa.server.xfw.UnificationExecutor] Failed method=Process subTask=CompleteMergeTasks Default User Population, 1026095
com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-30926: unable to get a stable set of rows in the source tables
ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 47
ORA-06512: at line 1
Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment.
|Cause||This issue may occur if the attribute used for the joins in the unification are not able to uniquely resolve the user resulting in a duplicate user entry.|
|Resolution||This issue is resolved in the following RSA Identity Governance & Lifecycle patches:|
The fix works as follows:
In versions where the patch has been applied, if the Identity Data Collectors (IDCs) have been collected before configuring the unification, then the unification screen will prevent the join from being created.
If the IDCs have not been collected before the unification join has been created, the unification change will be allowed, but duplicate users will be rejected during unification.
NOTE: If you still encounter this exact error after applying the above patches, please see RSA Knowledge Base Article 000037875 -- Unification fails with ORA-30926: unable to get a stable set of rows in the source tables, ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 47 in RSA Identity Governance & Lifecycle.
|Notes||Unification issues may appear similar but have different causes. If the error does not match exactly, suspect a different issue. |
See article 000035588 - Identity Data Unification failing with "ORA-30926: unable to get a stable set of rows" in RSA Identity Governance and Lifecycle 7.0.2 for similar errors with different causes.