cancel
Showing results for 
Search instead for 
Did you mean: 

Portal upgrade from 7.02 to 7.31 fails during EXECUTION/OFFLINE-MIGRATION

0 Kudos

Hello,

Maybe someone can help here since we are experiencing a severe problem.

Following error occurs:

An error has occurred during the execution of the RUN_OFFLINE_MIGRATION phase.

Error while processing migration list /data/inst/sap/SUM/T57a/java/data/mig/MIGRATIONAUSF.LST. Could not migrate some archives from migration list.Possible reason is Database is down.Check if database running Error during migration of archive /data/inst/sap/SUM/T57a/java/data/mig/DEPLOYARCHIVES/com.sap.security.migration.sda which has been extracted to directory /data/inst/sap/SUM/T57a/java/migtool/com.sap.security.migration.Possible reason is Database is down.Check if database running Could not execute MTI process. See log files /data/inst/sap/SUM/T57a/java/log/JMT_FRAMEWORK_RDM_01.OUT and /data/inst/sap/SUM/T57a/java/log/JMT_FRAMEWORK_RDM_01.ERR. Return code condition success evaluated to false for process java for action RUN_MTI.

Steps taken:

1) When we first ran into this problem a restore was done from the database and the filesystem to the beginning of the DONWTIME phase.

2) The original 7.02 instance was started.

3) The UME consistency check was run under user administration per sap note 1016283.

4) A repair was carried out,  no inconsistencies remained.

5) SUM upgrade restarted

6) During the migration of the sap.security.migration.sda package it generates an error causing the upgrade to stop.

Did anyone encounter the same problems during a portal upgrade?

Thanks for your response.

Toon

PS: We are on the latest SUM version 1.0 SP 7 Patch 2.

Accepted Solutions (0)

Answers (1)

Answers (1)

balraj_giduturi
Explorer
0 Kudos

Hello,

I ran into the same problem.

The log file /SUM/java/log/JMT_FRAMEWORK_RDM_nn.ERR contains following error

com.sap.sdt.jmt.MigrationException: The RFC connection data in the source system are conflicting because they contain data for direct server connection (ASHOST/SYSNR) as well as for load balanced connection (MSGHOST/GROUP/R3NAME)

I wonder if your log file (JMT_FRAMEWORK_RDM_nn.ERR) contains the same error.

In my case the UME Coniguration is using both ASHOST/SYSNR and MSGHOST/GROUP/R3NAME


UME Keys for ASHOST/SYSNR

ume.r3.connection.master.ashost

ume.r3.connection.master.sysnr


UME Keys for MSGHOST/GROUP/R3NAME

ume.r3.connection.master.group

ume.r3.connection.master.msghost

ume.r3.connection.master.r3name

I removed ASHOST/SYSNR and repeated this phase.  Upgrade proceed to next phase.

Message was edited by: Balraj Giduturi

former_member243990
Discoverer
0 Kudos

Hi Balraj,

Thank you for your hints. I had the same situation and symptoms and your resolution WORKS.

Thank you

Marek