cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade stops during PHASE SETSYNC_EULCK_START_D1 - Urgent

Former Member
0 Kudos

Hi,

im now in an upgrade from a SAP Crm 5.0 system to CRM 6.0 (2007).

Its a double Stack system with following configuration

- Windows 2003 Server SP2

- Oracle 10.2.0.2

- SAPup Version 7.00/2, build 24.103 for unicode

- Java Upgrade Manager Version 1.1.1111

My Problem:

In the sapup program the upgrade runs without error, but nothing happens in the system (no logging entries, activity on the system or errors). The upgrade is in the PHASE SETSYNC_EULCK_START_D1 after the EU_Imports 1-7.

Concorrent on the system runs the Java Upgrade Manager (Jupgrade) for the later syncronize for an upgrade of a double stack system. The Java Manager are waiting in Phase 9 of 121 called GETSYNC_PREUPTIME_FINISHED.

The shadow instance SHD didn`t run in this phase. I checked it with the start in commandline: sapup -SHDstart and it tolds me that the shadow instance is not possible to start at this time.

Have anyone an idea what happen ? its really urgent...

Thks

Cheers Mario

Here is the last log form the sapup.log from the put directory:

  1. ************************* SAPup started in UPGRADE mode *************************

  2. This is SAPup version 7.00/2 patch level 24.103.

  3. This is UNICODE SAPup!

  4. Reading Parameter File "E:\usr\sap\put\bin\DBSYNC.PAR" at 20080608123023

  5. Condition level 1, total => TRUE '#if ( "ORA" == "ORA" )' => TRUE

  6. Reading Parameter File "E:\usr\sap\put\bin\R3CURENV.LST" at 20080608123023

...begin dialogue at 20080608123026

...end dialogue at 20080608123030

...STARTED at 20080608123030.

  1. Reading Parameter File "E:\usr\sap\put\bin\TRATTR.LST" at 20080608123030

  2. Reading Parameter File "E:\usr\sap\put\bin\TRGROUP.LST" at 20080608123030

  3. Reading Parameter File "E:\usr\sap\put\bin\R3CURENV.LST" at 20080608123030

  4. Reading Parameter File "E:\usr\sap\put\bin\DBSWTC.PAR" at 20080608123030

  5. Condition level 1, total => FALSE '#if "ORACLE" == "SAPDB"' => FALSE

  6. Condition level 1, total => FALSE '#elseif "ORACLE" == "DB2-z/OS"' => FALSE

  7. Condition level 1, total => FALSE '#elseif "ORACLE" == "DB2/400"' => FALSE

  8. Condition level 1, total => FALSE '#elseif "ORACLE" == "DB6"' => FALSE

  9. Condition level 1, total => FALSE '#elseif "ORACLE" == "INFORMIX"' => FALSE

  10. Condition level 1, total => FALSE '#elseif "ORACLE" == "MSSQL"' => FALSE

  11. Condition level 1, total => TRUE '#elseif "ORACLE" == "ORACLE"' => TRUE

  12. Condition level 1, total => FALSE '#if "Windows NT X86_64" ~= "Linux"' => FALSE

  13. Condition level 1, total => FALSE '#elseif "Windows NT X86_64" ~= "Windows NT INTEL"' => FALSE

  14. Condition level 1, total => FALSE '#elseif "Windows NT X86_64" ~= "Windows NT IA64"' => FALSE

  15. Condition level 1, total => TRUE '#elseif "Windows NT X86_64" ~= "Windows NT X86_64"' => TRUE

...begin dialogue at 20080608123033

...end dialogue at 20080608123341

...begin dialogue at 20080608123341

...end dialogue at 20080608123349

UPGRADEPHASE SETSYNC_EULCK_START_D1

...started at 20080608123349

  1. Reading Parameter File "E:\usr\sap\put\bin\SAPUPPHAS.BRK" at 20080608123351

...begin dialogue at 20080608123351

...end dialogue at 20080608123401

...begin dialogue at 20080608123401

...end dialogue at 20080608123406

  1. Setting syncpoint EU_LOCKED=STARTED in E:\usr\sap\put\mig\SYNC.DAT

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

Mario,

Have anyone an idea what happen ? its really urgent...

as said yesterday already in the other thread, it´s better to open an OSS call and to have support people look on the system. Without access it´s very cumbersome to find out what´s happening on your system, too many logs would need to be posted.

And: "urgent" shouldn´t be used in the forum (see the Forum rules). If something is urgent, open a priority one call and you will get help immediately.

Markus

Former Member
0 Kudos

Hi,

ok sorry for the urgent...but if anyone have an idea, what can be wrong in this phase, send me your advise. thks.

OSS call is open

Cheers

Mario

Former Member
0 Kudos

The problem is solved, but not from the sap suppurt, im still waiting for an answer ....->