000035588 - Unification fails with ORA-30926: unable to get a stable set of rows in the source tables at 'AVUSER.UNFC_PROCESSOR', line 60 in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Oct 18, 2017Last modified by RSA Customer Support Employee on Feb 27, 2020
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000035588
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.2
 
IssueUnification is showing a status of Failed under Admin > Monitoring > {run id}.

The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) shows:
 




9/25/2017 21:23:32.574 INFO (Exec Task Consumer#4) [com.aveksa.server.xfw.UnificationExecutor]
Failed method=Process subTask=CompleteMergeTasks Default User Population,
nnnnn 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 60

ORA-06512: at line 1
   at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1601)
   at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1459)
   at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:267)
   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:745)
Caused by: java.sql.SQLException: ORA-30926: unable to get a stable set of rows in the source tables


 
CauseThe problem occurs when Identity Data Collectors from multiple data sources collect different values for the same custom attribute and that attribute is used for reference resolution,

This is a known issue reported in engineering ticket ACM-76856.

 
ResolutionThis issue is resolved in the following RSA Identity Governance & Lifecycle patches:
  • RSA Identity Governance & Lifecycle 7.0.2 P04
  • RSA Identity Governance & Lifecycle 7.1.0 P01

Attachments

    Outcomes