cancel
Showing results for 
Search instead for 
Did you mean: 

MAIN_SWITCH/.../GETSYNC_SCS_FINISHED running very long time

Former Member
0 Kudos

Dear experts,

I am doing an upgrade Dual-stack on SOL MAN 7.1 with SUM1.0 SPs16 from Original Support Packages of SOL MAN 7.1 to SP Level 14.

Oracle Database 11.2.0.3

SOL MAN 7.1

Windows 2K8 Standard 64bit

I am facing with a problem in phase Execution :MAIN_SWITCH/SUBMOD_SWITCH_KERNEL/GETSYNC_SCS_FINISHED

This phase is running very long time without errors, approx ~2 days. But I realized that there was no changes anything in /SUM/abap/log/* from then until now. So, I don't know how to trace this problem.

Please help me to resolve and  see attached logfiles

SAPup.log

***********************************

# Executing module 'MAIN_SWITCH'.

# BEGIN MAIN MODULE Downtime I: Switch tables and Kernel

# Starting phase execution with maxpar = 3, scheduled: 18x'-'

...begin dialog at 20160406111957

...end dialog at 20160406112034

CURRENTPHASE MAIN_SWITCH/SUBMOD_SWITCH_KERNEL/GETSYNC_SCS_FINISHED

...started at 20160406112034

# Checking for syncpoint SCS=FINISHED

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

***********************************

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear

Is that correct ? I have searched on SAP Market Place abt SUM1.0 SP14, but didn't see. Could you show me the path to download SUM 1.0 SP14 (on SMP just only SUM1.0 SP16).

Thanks

Stijn
Explorer
0 Kudos

Hi Tran,

you can't find it anymore on the SMP, but we keep a small collection for cases like this.

I have uploaded it to WeTransfer so you can get it:

WeTransfer

Regards,

Stijn

Answers (13)

Answers (13)

RvA
Explorer
0 Kudos

Only use this if you are sure that the steps you take are conform your scenario (ABAP only stackfile for instance on a DUAL stack)

Look at the Log tail of the SUM sapup.log and you will get a clue of what you will have to add to the sync.dat file in. the sdt/data of SUM.

In my case sapup.log:

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...

I Added this line to sync.dat file in sdt/data of the main SUM directory:

V1: TOOL=SAPJup EVENT=SAPJUP_CHECK_FINISHED STATUS=FINISHED

And SUM went on smoothly

RvA
Explorer
0 Kudos

Look at the Log tail of the SUM sapup.log and you will get a clue of what you will have to add to de sync.dat file in. the sdt/data of SUM.

In my case sapup.log:

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...

# Java reached status "FINISHED", continuing.

...finished at 20221029020704 with status SUCCEEDED.

Added this line to sync.dat:

V1: TOOL=SAPJup EVENT=SAPJUP_CHECK_FINISHED STATUS=FINISHED

And SUM went on smoothly

0 Kudos

Thanks a lot guys

Former Member
0 Kudos

Hi all,

This issue happens due to a Deadlock. The JAVA processes are hanging and during the execution of GETSYNC methods the ABAP task that executed this method goes to blocked mode waiting for JAVA to write on the SYNC.DAT file (that works as sincronization checkpoint log). However, as I said JAVA is hanging and nothing will be written. Now both stacks upgrade are hanging.

I solved this issue in a way that is not recommended (in my case the system being updated was just a test system being used only for me). However it worked just fine. So here it goes, I manually wrote on the SYNC file what the GETSYNC method wanted to read. After the ABAP stack upgrade was finished I restarted the the upgrade only for the java stack though the flag -javaonly.

You have to make sure the event has sucessufully finished checking the log of the ABAP task being performed and adding the following line in the SYNC file:

V1: TOOL=SAPup EVENT=<EVENT_NAME> STATUS FINISHED

I think in your case the event is called SCS. It is very likely this problem will happen with other getsync methods so be prepared to edit this file more than once.

Hope it helps,
Hyago Sallet.

0 Kudos

Hi All ,

Was there any fix for the above issue ,

Can you please share the solution

regards

Mk

Former Member
0 Kudos
Former Member
0 Kudos

I shared it below.

Former Member
0 Kudos

Dear

Sorry for late response and thanks for your upload.

SUM1.0 SP14 uses SL Common UI or DSUGui ?

Regards

Stijn
Explorer
0 Kudos

Hi Tran,

SP14 uses DSUgui for dual stacks.

Regards

Former Member
0 Kudos

Dear Stijin De Regge

I have already done with SUM1.0 SP14 without any errors. Thanks a lot

Former Member
0 Kudos

Hi Stijn,

I am facing exactly the same issue. Could you please upload SUM SP 14 on we transfer again for me.

Thank you in advance.

Regards,
Hyago Sallet.

Former Member
Former Member
0 Kudos

Thank you very much. I already solved the issue.

Former Member
0 Kudos

Dear

Stijn
Explorer
0 Kudos

I ended up using SUM SP14 to do the upgrade - didn't have any issues anymore, so I presume the new SUM SP16 is the issue.

Former Member
0 Kudos

Dear experts,

Have any updates ?

regards

Stijn
Explorer
0 Kudos

Hi Tran,

having the exact same issue.

Also Solman 7.1 SP04 intial install - upgrade to SP14.

Oracle 12c - Windows 2012.

Did you find a solution/workaround for this?

Thanks.

Stijn

Former Member
0 Kudos
Former Member
0 Kudos

Dear experts,

Do I need to start instances manually. I do not see Instance 02 on MMC in this phase.

Former Member
0 Kudos

Dear experts,

please see more an attached file. Upgrading system process is in the Downtime (Execution phase)

Output Command:

#sapcontrol -nr 01 -function GetProcessList

06.04.2016 19:21:17

GetVersionInfo

FAIL: HTTP error, HTTP/1.1 401 Unauthorized

#sapcontrol -nr 01 -function GetProcessList

06.04.2016 19:21:35

GetVersionInfod

FAIL: NIECONN_REFUSED (WSAECONNREFUSED: Connection refused), NiRawConnect failed in plugin_fopen()

s

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

You probably need to expand the icons and refresh the screen to see an updated view. Have you checked the logs in upgrade directory?. Sort the logs by time stamp and provide them.

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Run the below commands for SCS and for the J<00> instance and check if the kernel files are updated.

sapcontrol -nr 00 -function GetVersionInfo

Replace 00 with the correct system numbers for DVEBMGS and SCS instances.

This will say whether the kernel has been updated or not. If not you might need to copy the kernel from the shadow instance kernel directory. Check the logs under <Drive>:\SUM\abap\tmp

Check the status of the ABAP and Java processes using this command or from MMC.

sapcontrol -nr 00 -function GetProcessList

If the instance failed to start then check trace files from the work directory.

former_member185239
Active Contributor
0 Kudos

Hi Tran,

Try to restart the java system manually and check if the phase get cleared.

With Regards

Ashutosh Chaturvedi