cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade to NW7.3 - DOWNTIME: RUN_OFFLINE_MIGRATION phase

matthias_isenburg
Participant
0 Kudos

Hi there,

We are upgrading our portal from 7.01 SP7 to 7.3 SP8.

During the Downtime in the RUN_OFFLINE_MIGRATION phase we get the following error:

"
Error while processing migration
list /mnt/isps/sap/upg_dir/java/data/mig/MIGRATIONAUSF.LST. Could not
migrate some archives from migration list. Error during migration of
archive /mnt/isps/sap/upg_dir/java/data/mig/DEPLOYARCHIVES/com.sap.security.migration.sda which has been extracted to
directory /mnt/isps/sap/upg_dir/java/migtool/com.sap.security.migration. Could not execute MTI process. See log
files /mnt/isps/sap/upg_dir/java/log/JMT_FRAMEWORK_RDM_09.OUT
and /mnt/isps/sap/upg_dir/java/log/JMT_FRAMEWORK_RDM_09.ERR. Return
code condition success evaluated to false for process java for action
RUN_MTI.
"


MTI_COM_SAP_SECURITY_MIGRATION_DATABASE_MC_09.LOG:

"

<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[/mnt/isps/sap/upg_dir/java/log/MTI_COM_SAP_SECURITY_MIGRATION_DATABASE_MC_10.ERR]/-->
<!--PATTERN[MTI_COM_SAP_SECURITY_MIGRATION_DATABASE_MC_10.ERR]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %-40l [%t] %s: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Jan 3, 2013 9:08:46 AM   com.sap.security.core.migration.com_sap_security_migration.database_mcerr [Thread[main,5,main]] Error: Error while migrating controller com.sap.security.core.migration.UMEDatabaseController. CSN component - BC-JAS-SEC-UME . Reason: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=#UMERSTR;0000005707, DRIVER=3.63.75
        OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
Jan 3, 2013 9:08:46 AM   com.sap.security.core.migration.com_sap_security_migration.database_mcerr [Thread[main,5,main]] Error: com.sap.sdt.jmt.MigrationException: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=#UMERSTR;0000005707, DRIVER=3.63.75
        OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
        at com.sap.security.core.migration.UMEDatabaseController.migrateDatabase(UMEDatabaseController.java:148)
        at com.sap.sdt.jmt.mc.DatabaseMigrationExecuter.executeController(DatabaseMigrationExecuter.java:60)
        at com.sap.sdt.jmt.mc.AbstractMigrationControllerExecuter.executeMigrationController(AbstractMigrationControllerExecuter.java:401)
        at com.sap.sdt.jmt.mc.AbstractMigrationControllerExecuter.execute(AbstractMigrationControllerExecuter.java:364)
        at com.sap.sdt.jmt.migrationtool.MigrationToolImport.execute(MigrationToolImport.java:897)
        at com.sap.sdt.jmt.migrationtool.MigrationToolImport.migrateDatabase(MigrationToolImport.java:965)
        at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:607)
        at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1224)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)
Caused by: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=#UMERSTR;0000005707, DRIVER=3.63.75
        OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
        at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:125)
        at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
        at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
        at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
        at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1508)
        at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:375)
        at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:345)
        at com.sap.security.core.migration.UMEDatabaseController.executeUpdateStatement(UMEDatabaseController.java:346)
        at com.sap.security.core.migration.UMEDatabaseController.migrateDatabase(UMEDatabaseController.java:99)
        ... 12 more
Caused by: com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=#UMERSTR;0000005707, DRIVER=3.63.75
        at com.ibm.db2.jcc.am.fd.a(fd.java:675)
        at com.ibm.db2.jcc.am.fd.a(fd.java:60)
        at com.ibm.db2.jcc.am.fd.a(fd.java:127)
        at com.ibm.db2.jcc.am.yn.b(yn.java:2317)
        at com.ibm.db2.jcc.am.yn.c(yn.java:2300)
        at com.ibm.db2.jcc.t4.cb.l(cb.java:370)
        at com.ibm.db2.jcc.t4.cb.a(cb.java:62)
        at com.ibm.db2.jcc.t4.q.a(q.java:50)
        at com.ibm.db2.jcc.t4.tb.b(tb.java:220)
        at com.ibm.db2.jcc.am.zn.lc(zn.java:3314)
        at com.ibm.db2.jcc.am.zn.b(zn.java:4271)
        at com.ibm.db2.jcc.am.zn.dc(zn.java:757)
        at com.ibm.db2.jcc.t4.l.dc(l.java:165)
        at com.ibm.db2.jcc.am.zn.executeUpdate(zn.java:740)
        at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPreparedStatement.java:108)
        at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:372)
        ... 15 more
"

Anybody have any clue about this?


thanks
matthias

Accepted Solutions (0)

Answers (2)

Answers (2)

Reagan
Advisor
Advisor
0 Kudos
Former Member
0 Kudos

Hi,

The solution is....

If the migration process needs more memory and fails with an OutOfMemory error in the RUN_OFFLINE_MIGRATION phase, proceed as follows: 

  1. 1. Stop SUM.
  2. 2. Increase the default values of the heap size by editing the configuration file "JMTJVMArguments.xml" which is located in the SUM\java\config directory and save your changes.
  3. 3. Restart SUM and repeat the failed phase.

BR,

Prabhakar