AnsweredAssumed Answered

Schema Migration error while upgrading from v6.9 to 7.0.1

Question asked by shakti nayak on Jul 19, 2017
Latest reply on Jul 19, 2017 by Boris Lekumovich

We are trying to upgrade from v 6.9.1 to v7.0.1. Ours is setup in weblogic env.

After trying to access the console. It asked for schema migration. we gave the password and started the schema migration.

The schema migration led to the below error.

 

Errors found while migrating the schema
Schema Migration completed in 0h 8m 47s with errors.

/domain/aveksa_UAT/servers/aveksa/tmp/_WL_user/aveksa-1/r8il0j/aveksa.war/WEB-INF/database/migration/migrateMasterTableData.sql(25):
begin MTM_Accounts.Migrate; end;
java.sql.SQLSyntaxErrorException: ORA-02264: name already used by an existing constraint
ORA-06512: at "AVUSER.MTM_HELPER", line 100
ORA-06512: at "AVUSER.MTM_ACCOUNTS", line 147
ORA-06512: at "AVUSER.MTM_ACCOUNTS", line 47
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:198)
   at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:103)
   at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:94)
   at com.aveksa.migration.jdbctool.IncrementalUpdate.update(IncrementalUpdate.java:481)
   at com.aveksa.migration.jdbctool.MigrateSchema.execute(MigrateSchema.java:117)
   at com.aveksa.migration.jdbctool.CheckDatabase.migrateSchema(CheckDatabase.java:1432)
   at com.aveksa.migration.jdbctool.CheckDatabase.runMigration(CheckDatabase.java:2193)
   at com.aveksa.migration.jdbctool.CheckDatabase.run(CheckDatabase.java:2139)
   at java.lang.Thread.run(Thread.java:745)
/domain/aveksa_UAT/servers/aveksa/tmp/_WL_user/aveksa-1/r8il0j/aveksa.war/WEB-INF/database/migration/migrateMasterTableData.sql(27):
begin MTM_Groups.Migrate; end;
java.sql.SQLSyntaxErrorException: ORA-02264: name already used by an existing constraint
ORA-06512: at "AVUSER.MTM_HELPER", line 100
ORA-06512: at "AVUSER.MTM_GROUPS", line 741
ORA-06512: at "AVUSER.MTM_GROUPS", line 51
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:198)
   at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:103)
   at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:94)
   at com.aveksa.migration.jdbctool.IncrementalUpdate.update(IncrementalUpdate.java:481)
   at com.aveksa.migration.jdbctool.MigrateSchema.execute(MigrateSchema.java:117)
   at com.aveksa.migration.jdbctool.CheckDatabase.migrateSchema(CheckDatabase.java:1432)
   at com.aveksa.migration.jdbctool.CheckDatabase.runMigration(CheckDatabase.java:2193)
   at com.aveksa.migration.jdbctool.CheckDatabase.run(CheckDatabase.java:2139)
   at java.lang.Thread.run(Thread.java:745)
8 Errors detected:
ORA-06512: at "AVUSER.MTM_HELPER", line 100
ORA-06512: at "AVUSER.MTM_ACCOUNTS", line 147
ORA-06512: at "AVUSER.MTM_ACCOUNTS", line 47
ORA-06512: at line 1
ORA-06512: at "AVUSER.MTM_HELPER", line 100
ORA-06512: at "AVUSER.MTM_GROUPS", line 741
ORA-06512: at "AVUSER.MTM_GROUPS", line 51
ORA-06512: at line 1

Examine log file: /domain/aveksa_UAT/servers/aveksa/tmp/_WL_user/aveksa-1/r8il0j/aveksa.war/WEB-INF/../log/migrate.log for more information. Consult the installation guides if this is a known issue
Determine if you need to address the errors and redo the operation
Anybody aware of such a issue.

Outcomes