Unification fails at Step 7/11 with 'ORA-54017: UPDATE operation disallowed on virtual columns' in RSA Identity Governance & Lifecycle
Originally Published: 2021-02-03
Article Number
Applies To
RSA Version/Condition: 7.2.1, 7.2.1 P01, 7.2.1 P02
Issue
01/20/2021 10:49:43.788 ERROR (Exec Task Consumer#0 - Main) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-54017: UPDATE operation disallowed on virtual columns ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 66 ORA-06512: at line 1 01/20/2021 10:49:43.790 INFO (Exec Task Consumer#0 - Main) [com.aveksa.server.xfw.UnificationExecutor] Failed method=Process subTask=CompleteMergeTasks Default User Population, 32900 com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-54017: UPDATE operation disallowed on virtual columns ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 66 ORA-06512: at line 1 at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1456) at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1388) at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:208) at com.aveksa.server.xfw.UnificationExecutor.executeTask(UnificationExecutor.java:125) at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:101) at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:129) at java.lang.Thread.run(Thread.java:748) Caused by: java.sql.SQLException: ORA-54017: UPDATE operation disallowed on virtual columns ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 66 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:1434) ... 6 more Caused by: Error : 54017, Position : 0, Sql = BEGIN UNFC_Processor.UnifyUsers(:1 ,:2 ); END;, OriginalSql = {call UNFC_Processor.UnifyUsers(?,?)}, Error Msg = ORA-54017: UPDATE operation disallowed on virtual columns ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 66 ORA-06512: at line 1 at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498) ... 30 more
Cause
Another way to confirm whether this issue applies to you is to run the following SQL query (as avuser). This query will list the attributes that are problematic (as also seen on the User Attributes screen shown above). If the SQL query returns at least a single row, your RSA Identity Governance & Lifecycle deployment is affected by this issue.
SELECT name FROM t_extensible_schema_columns WHERE table_name = 'T_MASTER_ENTERPRISE_USERS' AND type = 'USER' AND is_editable = 'y';
Resolution
- RSA Identity Governance & Lifecycle 7.2.1 P03
Workaround
Attachments
If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).
Related Articles
RSA Authentication Manager 8.2 hardware appliance fails to reboot when patch or upgrade is applied 165Number of Views Identity Data Unification longer in Step 8/11 Populate Role Metrics in RSA Governance & Lifecycle 258Number of Views Unification is failing at step 8 on "AVUSER.ROLE_MANAGEMENT_PKG", line 2469 in RSA Governance & Lifecycle 491Number of Views RSA Authentication Manager Operations Console fails to display virtual host certificates 342Number of Views Custom attributes defined for User and Account Mapping are missing in Public Views and potential failure in applying patch… 230Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?