000036247 - RSA Identity Governance & Lifecycle upgrade or migration error "ORA-00942: table or view does not exist"

Document created by RSA Customer Support Employee on Apr 18, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036247
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.2 P05 or earlier
 
IssueRSA Identity Governance & Lifecycle upgrade or migration fails when upgrading to 7.0.2 P05 or earlier.

The following error is logged in the aveksaServer.log
 

04/04/2018 23:41:17.752 ERROR (Schema Migration) [com.aveksa.migration.jdbctool.CheckDatabase] ORA-00942: table or view does not exist
ORA-06512: at "AVUSER_TEST.REPORT_VIEWS_PKG", line 10967
ORA-06512: at line 1

04/04/2018 23:41:17.753 FATAL (Schema Migration) [com.aveksa.migration.jdbctool.CheckDatabase]

****************************************

Migration has failed!

ORA-00942: table or view does not exist
ORA-06512: at "AVUSER_TEST.REPORT_VIEWS_PKG", line 10967
ORA-06512: at line 1


****************************************


The following error is logged in the migration.log
 

-------
SQL/line#: /usr/wls/domains/DOMAINNAME/servers/AveksaSrv1/tmp/_WL_user/aveksa/32gp3v/aveksa.war/WEB-INF/database/migration/createReportViews.sql(1):
Start time [Wed Apr 04 23:41:06 UTC 2018]
begin Report_Views_Pkg.create_av_report_views; end;
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
ORA-06512: at "AVUSER_TEST.REPORT_VIEWS_PKG", line 10967
ORA-06512: at line 1


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 weblogic.jdbc.wrapper.Statement.executeUpdate(Statement.java:535)
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)
CauseThis issue may occur if a database name other than the default AVUSER is used for the name of the remote database.   The problem occurs in several packages where the references to internal RSA tables incorrectly uses the AVUSER database name explicitly instead of using the configured database name.
ResolutionThis issue is resolved in the following RSA Identity Governance & Lifecycle patches.  If you need to upgrade, ensure you upgrade to one of the versions that are not susceptible 
  • RSA Identity Governance & Lifecyle 7.1.0 GA version
  • RSA Identity Governance & Lifecyle 7.0.2 P06

 
WorkaroundUse AVUSER for the remote database name. 
Notes
  • If possible, upgrade to the 7.1.0 version that does not have this issue. 
  • If you must upgrade to the 7.0.2 version:
  • If you are upgrading on WebSphere or WebLogic, you can upgrade directly to the patch by applying the 7.0.2 P06 ear file directly.
  • If you encounter this error while upgrading on WildFly, there is no supportable in-place upgrade path to 7.0.2. (There is no means of upgrading to a patch, you must first upgrade to the 7.0.2 GA version.)  Customers should install a new version of 7.0.2 and patch to 7.0.2 P06 and then import the database from a backup. 

Attachments

    Outcomes