000033985 - How to resolve an issue of Account Data Collection failing in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Sep 20, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033985
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
 
IssueAccount Data collection fails with the following error:
Error ID: 638
Description: EC[30926] Context[RunID=837, ADC(Name=CORP AD ADC, ID=4)] Message[Unknown error code]
Type: Account Data Load
Created On: 9/8/16 9:53 AM

You will see the error below while testing the collector:
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.EDC_UPDATE_MASTER_TABLES", line 494 ORA-06512:
    at "AVUSER.COMMON_EXPLODER", line 1359 ORA-06512:
    at "AVUSER.ADC_DATA_COLLECTOR", line 244 ORA-06512:
    at "AVUSER.ADC_DATA_COLLECTOR", line 450 ORA-06512:
    at line 1 at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1473)
    at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1331)
    at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:235)
    at com.aveksa.server.xfw.DefaultAccountObjectDataFilter.loadData(DefaultAccountObjectDataFilter.java:104)
    at com.aveksa.server.xfw.DefaultAccountObjectDataFilter.process(DefaultAccountObjectDataFilter.java:72)
    at com.aveksa.server.xfw.DefaultAccountObjectDataFilter.process(DefaultAccountObjectDataFilter.java:60)
    at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:85) at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:64)
    at com.aveksa.server.xfw.DataObjectProcessingExecutor.executeFullTask(DataObjectProcessingExecutor.java:116)
    at com.aveksa.server.xfw.DataObjectProcessingExecutor.executeTask(DataObjectProcessingExecutor.java:58)
    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 ORA-06512:
    at "AVUSER.EDC_UPDATE_MASTER_TABLES", line 494 ORA-06512: at "AVUSER.COMMON_EXPLODER", line 1359 ORA-06512:
    at "AVUSER.ADC_DATA_COLLECTOR", line 244 ORA-06512:
    at "AVUSER.ADC_DATA_COLLECTOR", line 450 ORA-06512:
    at line 1 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523) at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:204)
    at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1007)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1315)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3576)
    at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3677)
    at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4694)
    at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1086)
    at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:404)
    at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1436)
...
12 more


 
CauseUsually such errors occur as a result of either duplicate data internal to RSA Identity Governance & Lifecycle or having collected duplicates from the data-source.
ResolutionA clean and quick way to address this is to recreate the collectors and then re-run collection and unification. This process also helps to narrow down if the culprit is from the data-source or not. The steps are:
  1. Export the collector that is giving the error.  
    1. Go to Admin > Import/Export.  
    2. Select Account collectors.  
    3. Select the Account Data collector that has the issue.  
    4. Click on Next and Export.
  2. Rename the current collector (you can append "old" to it for example).  
    1. Go to Collectors > Account Collectors.  
    2. Select the Account Data Collector that has the issue.
    3. Click on Edit.
    4.  Rename the collector and save.
  3. Import the collector back in (this will recreate it).  
    1. Go to Admin > Import/Export.
    2. Click on Import and select the exported collector file.
  4. Run the collector and unification
This will prevent the Account Data Collector to run without issues.

Attachments

    Outcomes