Upgrade Assistant hangs on phase GETSYNC_PREUP_FINI_R2 forever

[Former Member]

Hello,

I tried to upgrade my ECC5.0 system to ECC6.0. I followed the

SAPERPCC6.0UpgradeGude by using Upgrade Assistant (PREPARE and SAPup).

I tested this upgrade on a test machine with clean SAP ECC5.0 ABAP+JAVA

instances and Oracle 10.2.0.2.0 installed. In my PREPARE phases had no

problem at all. In my SAPup, right after I passed REQSTOPPROD phase, it

stopped at GETSYNC_PREUP_FINI_R2 phase forever. I checked the SAPup.log

and searched SAP notes I couldn't find any clues. I also reset the

upgrade twice, but it still hung at the same spot with the same

message. On the upgrade assistant console window hung and showed ">>

12:01:38 UPGRADE/SHDINST: START OF PHASE GETSYNC_PREUP_FINI_R2

The parallel running J2EE upgrade needs some more time...

Please be patient..."

In the SAPup.log showed:

UPGRADEPHASE GETSYNC_PREUP_FINI_R2

...started at 20060723120138

1. Checking for syncpoint PREUPTIME=FINISHED in

c:\usr\sap\put\mig\SYNC.DAT

1. Java has status "", we'll wait and check every 20 second(s).

2. Java has status "", wait another 5 minutes before logging...

3. Java has status "", wait another 5 minutes before logging...

4. Java has status "", wait another 5 minutes before logging...

5. Java has status "", wait another 5 minutes before logging...

6. Java has status "", wait another 5 minutes before logging...

7. Java has status "", wait another 5 minutes before logging...

8. Java has status "", wait another 5 minutes before logging...

9. Java has status "", wait another 5 minutes before logging...

10. Java has status "", wait another 5 minutes before logging...

11. Java has status "", wait another 5 minutes before logging...

12. Java has status "", wait another 5 minutes before logging...

13. Java has status "", wait another 60 minutes before logging...

It looks like Java has status "" and waiting for logging. What is that

mean? Please help me I have struggling with this problem for two days.

I am also attached SAPup.log, CHECKS.log, SYNC.DAT and screenshots for

your reference. Please Let me know if you need any information or logs.

Regards,

Justin

[Former Member]

Hi,

In General it's not a bug actually, Your ABAP upgrade is waiting for the JAVA upgrade to start.. that means ABAP upgrade will wait for the java status at the time if synchronization. here you need to check the SAPJUP is runing or not if not you need to start java upgrade, Upgrade guide for the dual stack system will clearly expalains about this situation. please check the upgrade guides so that you will come to know clearly..

I had similar problems earlier while working on dual stack systems upgrade, i have started the java upgrade when ever i have seen java status information in log files. so that upgrade moved further with out any issues.

Hope the above information will shed some light on the issue.

-Srini

[Former Member]

We're upgrading a SRM 5.5 system (DUAL-stack) to SRM 7.01 and facing the same problem only in the

GETSYNC_PREUP_FINI_D fase.

1. Checking for syncpoint PREUPTIME=FINISHED

2. Java has status "", we'll wait and check every 20 second(s).

3. Java has status "", wait another 5 minutes before logging...

4. Java has status "", wait another 5 minutes before logging...

When the JAVA-Prepare has finished the SYNC.DAT is edited.

It adds the last two lines.

V1: TOOL=SAPup EVENT=PREPARE STATUS=STARTED

V1: TOOL=SAPup EVENT=INFO STATUS=FINISHED

V1: TOOL=SAPup EVENT=UPGRADE STATUS=STARTED

V1: TOOL=SAPup EVENT=PREUPTIME STATUS=STARTED

V1: TOOL=SAPup EVENT=EU_LOCKED STATUS=STARTED

V1: TOOL=SAPup EVENT=SHADOWINST STATUS=FINISHED

V1: TOOL=SAPup EVENT=PREUPTIME STATUS=FINISHED

V1: TOOL=SAPJup EVENT=PREPARE STATUS=STARTED

Start JAVA upgrade, so that JAVA will sync with ABAP.

The line beneath will be written to the SYNC.DAT file.

V1: TOOL=SAPJup EVENT=PREPARE STATUS=FINISHED

Now the ABAP part continue"s

Kind regards.

Marcel

[RvA]

A clue for what to add to the sync.dat file in sdt/data directory of SUM you can find in de sapup.log file (in SUM press More and the Log Tail: In my case

CURRENTPHASE MAIN_INIT/GETSYNC_CHECK_FINISHED

...started at 20221029020144
# Checking for syncpoint SAPJUP_CHECK_FINISHED=FINISHED
# Java has status "", we'll wait and check every 20 second(s).
# Java has status "", wait another 5 minutes before logging...

So I added the following line at the end of the sync.dat file in sdt/data

V1: TOOL=SAPJup EVENT=SAPJUP_CHECK_FINISHED STATUS=FINISHED

SUM went on smoothly from that point

[Former Member]

hi can you assist me upgrading my 4.7 to ecc6.0 need some initialising documents from where to start

thank uou

chennupaati_rams@yahoo.com

[Former Member]

Hi Justin,

Many thanks for your valuable information. Great!!!

[Former Member]

Our plan changed, we decided to upgrade ECC6.0 on an ABAP system only, so I deleted the Java add-in from the dual stack and reset the instance profile rdisp/j2ee_start = 0. (see note: 934615) However, upgrade assistant skipped the GETSYNC_PREUP_FINI_R2 phase. Now I am working on the rests. This could be a bug with dual stack when you do the ECC6.0 parallel upgrade.

[Former Member]

Here is the solution:

The JAVA upgrade (SAPjup) will write a enty in SYNC.DAT like

V1: TOOL=SAPJup EVENT=PREUPTIME STATUS=FINISHED

The ABAP upgrade in phase GETSYNC_PREUP_FINI_R2 will check if event

PREUPTIME has status FINISHED. If not it will wait till this entry is

there.

'Java has status "" ' means that SAPjup has not written any status yet

to this file (since the JAVA upgrade had not been started).

SAPup was waiting for an entry EVENT=PREUPTIME STATUS=FINISHED written

by SAPjup.

'Before logging' means before checking again.

I only start the ABAP upgrade using SAPup but did not perform a JAVA upgrade using SAPjup so SAPjup could not write any synchronisation information in SYNC.DAT.

Problem solved.