Data Archiving fails in Data Purging step in RSA Identity Governance & Lifecycle

[#1]

Article Number

000039491

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.1, 7.2.0
 

Issue

RSA Identity Governance & Lifecycle Database Purging may fail after Data Archiving.

The Data Management tab on the Admin System menu shows the Archive Status as Completed but the Purge Status as Failed.   (Additional information may be displayed if the "Error Message" column is displayed.)

Image description

The following WARN and ERROR level messages are logged in the aveksaserver.log file
 

05/21/2020 16:27:28.812 WARN  (Exec Task Consumer#3 - Main) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 30926, SQLState: 99999
05/21/2020 16:27:28.812 ERROR (Exec Task Consumer#3 - Main) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-30926: unable to get a stable set of rows in the source tables
ORA-06512: at "AVUSER.ARCHIVEPURGE_PKG", line 839
ORA-06512: at line 1

05/21/2020 16:27:28.827 ERROR (Exec Task Consumer#3 - Main) [com.aveksa.server.xfw.TaskExecutor] Failed method=Execute ExecutionTask[TaskID=58858 RunID=25582 Source=68 Type=DataArchiving Status=InProgress]
com.aveksa.server.xfw.ExecutionException: 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.ARCHIVEPURGE_PKG", line 839
ORA-06512: at line 1

        at com.aveksa.server.xfw.DataArchivingTaskExecutor.executeTask(DataArchivingTaskExecutor.java:62)
        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: 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.ARCHIVEPURGE_PKG", line 839
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.DataArchivingTaskExecutor.executeTask(DataArchivingTaskExecutor.java:59)
        ... 3 more
Caused by: java.sql.SQLException: ORA-30926: unable to get a stable set of rows in the source tables
ORA-06512: at "AVUSER.ARCHIVEPURGE_PKG", line 839
ORA-06512: at line 1

        at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
        at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
        at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
        at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
        at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:223)
        at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:56)
        at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:907)
        at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1119)
        at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3780)
        at oracle.jdbc.driver.T4CCallableStatement.executeInternal(T4CCallableStatement.java:1300)
        at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3887)
        at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4230)
        at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1079)
        at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:442)
        at com.aveksa.server.db.persistence.work.PersistenceServiceBaseWork.executeCallableStatement(PersistenceServiceBaseWork.java:36)
        at com.aveksa.server.db.persistence.work.StoredProcedureCallWork.execute(StoredProcedureCallWork.java:80)
        at org.hibernate.jdbc.WorkExecutor.executeWork(WorkExecutor.java:37)
        at org.hibernate.internal.SessionImpl$3.accept(SessionImpl.java:2134)
        at org.hibernate.internal.SessionImpl$3.accept(SessionImpl.java:2131)
        at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.coordinateWork(JdbcCoordinatorImpl.java:332)
        at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:2153)
        at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:2138)
        at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1526)
        ... 6 more
Caused by: Error : 30926, Position : 0, Sql = BEGIN ArchivePurge_Pkg.archiveData(:1 ,:2 ,:3 ); END;, OriginalSql = {call ArchivePurge_Pkg.archiveData(?,?,?)}, Error Msg = ORA-30926: unable to get a stable set of rows in the source tables
ORA-06512: at "AVUSER.ARCHIVEPURGE_PKG", line 839
ORA-06512: at line 1

        at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
        ... 30 more

The "Database Logs for Run" for the Data Archive task shows the following event.

Error archiving data from T_AV_RULES

"Error Stack Trace: ORA-06512: at ""AVUSER.ARCHIVEPURGE_PKG"", line 975
ORA-06512: at ""AVUSER.ARCHIVEPURGE_PKG"", line 740"

 

Cause

This is a known issue in the following versions:

• RSA Identity Governance & Lifecycle 7.1.1 
• RSA Identity Governance & Lifecycle 7.2.0

This issue may occur if there are duplicate Rule names in some of the data to be archived. 

Resolution

This issue is resolved in the following versions:

• RSA Identity Governance & Lifecycle 7.1.1 P09
• RSA Identity Governance & Lifecycle 7.2.0 P03
• RSA Identity Governance & Lifecycle 7.2.1

The patch includes a migration script ACM-105801.sql that corrects the database issue as well as a code change that prevents it from occurring.

Workaround

If you are unable to patch to a version where this issue is resolved please contact RSA Customer Support and quote this article number.