000035588 - Identity Data Unification failing with "ORA-30926: unable to get a stable set of rows" in RSA Identity Governance & Lifecycle 7.0.2

Document created by RSA Customer Support Employee on Oct 18, 2017Last modified by RSA Customer Support Employee on Apr 10, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000035588
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.2
IssueWhen running an Identity Collection, it runs without error.  However, the Identity Data Unification may fail with the following error:
09/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 is caused by identity data from two sources having different values for a collected Custom Attribute, where that attribute is used for Reference Resolution.

This is a known issue that is tracked in ACM-76856.


This issue is resolved in the following patches

  • RSA Identity Governance & Lifecycle 7.0.2 P04
  • RSA Identity Governance & Lifecycle 7.1.0 P01
WorkaroundIn the first instance, please contact RSA Support to log a case, so that the current version, patches and hot fixes can be verified as suitable for running the DevFix.  The RSA Support Engineer can then access this note, and provide the correct DevFix SQL file.

When the case is logged, please provide the following files, that are available in the UI via Admin > System > Server Nodes (tab) > Nodes (column):
  • aveksaServerInfo.log (version and platform information).  
  • aveksaServer.log (actual log for the product).
Please note that the resolution steps are as follows.

  1. Stop ACM

acm  stop

  1. Login to the database as AVUSER, using SQL*Plus.
  2. Apply the DevFix (to be provided by the Support Engineer, after verifying that is is suitable for the current version, patches and hot fixes).
  3. Execute the following SQL statements:

UPDATE t_idc_groups SET requires_full_remerge = 'Y';

  1. Start ACM.

acm start

  1. Re-run Unification (as per the SQL in step 4, it is in full refresh mode).