The goal is to upgrade RSA Identity Governance and Lifecycle 7.0.1 P02 to 7.0.2. The upgrade fails during the schema migration phase with the following error:
Found invalid object(s) in the database. Please check the log for error(s).
ORA-24344: success with compilation error
ORA-06512: at "AVUSER.SIEM_INTEGRATION", line 134
ORA-06512: at "AVUSER.PUBLIC_SCHEMA", line 69
ORA-06512: at line 4
Schema Migration completed in 0h 0m 39s with errors.
/home/oracle/wildfly/standalone/tmp/vfs/temp/tempef1a5d3803ad107d/content-beaf9ceb164c0311/contents/aveksa.war/WEB-INF/database/migration/createPublicSchema.sql(3):
DECLARE
v_user CONSTANT VARCHAR(30) := 'ACMDB';
BEGIN PUBLIC_SCHEMA.init(v_user);
commit;
end;
java.sql.SQLException:
ORA-24344: success with compilation error
ORA-06512: at "AVUSER.SIEM_INTEGRATION", line 134
ORA-06512: at "AVUSER.PUBLIC_SCHEMA", line 69
ORA-06512: at line 4
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:30)
at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:931)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1150)
at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1707)
at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1670)
at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:310)
at org.jboss.jca.adapters.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:375)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:221)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:107)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:98)
at com.aveksa.migration.jdbctool.IncrementalUpdate.update(IncrementalUpdate.java:481)
at com.aveksa.migration.jdbctool.MigrateSchema.execute(MigrateSchema.java:140)
at com.aveksa.migration.jdbctool.CheckDatabase.migrateSchema(CheckDatabase.java:1375)
at com.aveksa.migration.jdbctool.CheckDatabase.migrateSchema(CheckDatabase.java:1349)
at com.aveksa.migration.jdbctool.CheckDatabase.runMigration(CheckDatabase.java:2045)
at com.aveksa.migration.jdbctool.CheckDatabase.run(CheckDatabase.java:1991)
at java.lang.Thread.run(Thread.java:745)
The custom user attribute SUPERVISOR_NAME is conflicting with an existing identical attribute during the schema migration. This is a known issue reported in engineering ticket ACM-74441.
This issue is resolved in the following RSA Identity Governance & Lifecycle patches:
- RSA Identity Governance & Lifecycle 7.0.1 P04
- RSA Identity Governance & Lifecycle 7.0.2 P02