Unification is showing a status of
Failed under
Admin >
Monitoring > {
run id}. The unification failure is in
Step 2/11: Processing: Merge Collected Users.
Image descriptionThe
Admin error shows the following:
ORA-30927: unable to get a stable set of rows in the source tables at 'AVUSER.UNFC_PROCESSOR', line 66
Image description
The
aveksaServer.log file
($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) shows:
06/18/2019 07:54:04.498 INFO (Exec Task Consumer#2 - Main) [com.aveksa.server.xfw.UnificationExecutor]
Failed method=Process subTask=CompleteMergeTasks Default User Population, 6941211
06/18/2019 07:54:04.498 INFO (Exec Task Consumer#2 - Main) [com.aveksa.server.xfw.UnificationExecutor]
Failed method=Process subTask=CompleteMergeTasks Default User Population, 6941211
com.aveksa.server.db.PersistenceException:
java.sql.SQLException: ORA-30926: unable to get a stable set of rows in the source tablesORA-06512:
at "AVUSER.UNFC_PROCESSOR", line 66
ORA-06512: at line 1
at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure
(PersistenceServiceProvider.java:1548)
at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure
(PersistenceServiceProvider.java:1480)
at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:245)
at com.aveksa.server.xfw.UnificationExecutor.executeTask(UnificationExecutor.java:122)
at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:99)
at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:116)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLException:
ORA-30926: unable to get a stable set of rows in the source tablesORA-06512:
at "AVUSER.UNFC_PROCESSOR", line 66
ORA-06512: at line 1
The database log file for the unification run (
Admin >
Monitoring >
{Run Id} >
Database Logs) sorted by Job # smallest to largest shows the last SQL statement executed as:
Unification Processor Merge_Attributes SQLMERGE
Please refer to RSA Knowledge Base Article
000030327 -- Atifacts to gather in RSA Identity Governance & Lifecycle to find the location of the
aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform.
This is a known issue reported in engineering tickets ACM-103945 and ACM-98988.
This issue is resolved in RSA Identity Governance & Lifecycle 7.1.1 P04.
Please contact
RSA Identity Governance & Lifecycle Support for a possible workaround to this issue.