cancel
Showing results for 
Search instead for 
Did you mean: 

Solman SP14 Stuck into "MAIN_SHDIMP/GETSYNC_PREUP_FINI_D" phase

Former Member
0 Kudos

Hi experts,

During Solman upgrade SP4 to SP14 upgrade stuck in "MAIN_SHDIMP/GETSYNC_PREUP_FINI_D" phase alst 8 hrs.

and log not updating.

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member198540
Participant
0 Kudos

Hi,

Please chech the past post:

Hopefully this will resolve your issue


Regards,

0 Kudos

Hi Vevek,

I am facing the same issue but with SP13. Did you manage to solve that issue?

Thanks

former_member198540
Participant
0 Kudos

Hi,

Try to check the logs at DB level.

Former Member
0 Kudos

Hi Vivek,

Please refer to if not already checked.

Thanks,

Manas

Former Member
0 Kudos

Here is the output of SYNC.DAT file.

----------------------------------

V1: TOOL=SAPJup EVENT=COMMONPART STATUS=FINISHED

V1: TOOL=SAPJup EVENT=SAPJup_extract_syncevents_registered STATUS=FINISHED

V1: TOOL=SAPup EVENT=PREPARE STATUS=STARTED

V1: TOOL=SAPup EVENT=INFO STATUS=FINISHED

V1: TOOL=SAPJup EVENT=SAPJup_configure_syncevents_registered STATUS=FINISHED

V1: TOOL=SAPup EVENT=PREPARE STATUS=STARTED

V1: TOOL=SAPup EVENT=INFO STATUS=FINISHED

V1: TOOL=SAPup EVENT=PREPARE STATUS=STARTED

V1: TOOL=SAPup EVENT=INFO STATUS=FINISHED

V1: TOOL=SAPJup EVENT=COMMONPART STATUS=FINISHED

V1: TOOL=SAPJup EVENT=SAPJup_extract_syncevents_registered STATUS=FINISHED

V1: TOOL=SAPJup EVENT=SAPJup_configure_syncevents_registered STATUS=FINISHED

V1: TOOL=SAPJup EVENT=PREPARE STATUS=STARTED

V1: TOOL=SAPup EVENT=PREPARE STATUS=STARTED

V1: TOOL=SAPup EVENT=INFO STATUS=FINISHED

V1: TOOL=SAPup EVENT=SHDNUMDET 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=STARTED

V1: TOOL=SAPup EVENT=SHADOWINST STATUS=FINISHED

V1: TOOL=SAPup EVENT=PREUPTIME STATUS=FINISHED

---------------------------------------------------------------------------------------------------------

PHASES.LOG

1 ETQ201 Entering upgrade-phase "MAIN_SHDIMP/GETSYNC_PREUP_FINI_D" ("20160902082811")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399   dbs_ora_schema=SAPSR3

1 ETQ200 Executing actual phase 'MAIN_SHDIMP/GETSYNC_PREUP_FINI_D'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'PREUPTIME'

2 ETQ399 Arg[1] = 'FINISHED'

manish_singh13
Active Contributor
0 Kudos

Hi Vivek,

As per the link provided by Manas and logs provided by you it seems your SAPJup Prepare Status (V1: TOOL=SAPJup EVENT=PREPARE STATUS=STARTED) step is already started and now ABAP upgrade is waiting for that phase to complete.

What is it showing the status for Java stack upgrade in SUM?

Thanks,

Manish

Former Member
0 Kudos

But mainsh its stuck into the "MAIN_SHDIMP/GETSYNC_PREUP_FINI_D" phase in ABAP side.

i checked nothing in ruining SM66/ oracle session.

and java side we are getting below error.

manish_singh13
Active Contributor
0 Kudos

Hi Vivek,

As I mentioned in previous post that ABAP upgrade step is waiting for update from Java stack upgrade and you have currently Java Stack upgrade in error status.

I believe you have properly generated stack.xml file for your Solman Upgrade OR you are using default stack file provided with SPS14 DVD stack?

Please provide the output of TRANSFER-ABAP-USAGE-INFO_11.LOG to check.

Thanks,

Manish

Former Member
0 Kudos

Yes Manish you are absolutely right ABAP and waiting for the java upgrade. i read the same in below wiki

(SLTG)(SAPJUP) Problems-P12 - Technology Troubleshooting Guide - SCN Wiki

I'm using stack.xml SPS14 DVD.

TRANSFER-ABAP-USAGE-INFO_11.LOG mention bleow

-----------------------------------------------------------------------

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[E:\SUM_SP17\sdt\log\SUM\TRANSFER-ABAP-USAGE-INFO_11.LOG]/-->

<!--PATTERN[TRANSFER-ABAP-USAGE-INFO_11.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Sep 2, 2016 11:48:35 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DevelopmentSupportRequiredException: Assertion failed for (Usage with name:sap.com/CRM-APPwas not found in target release usages object (property: allUsages)) at com.sap.sdt.util.diag.SDT.check(SDT.java:38).

.----------------------------------------------------------------------------------------------------

Regards,

Vivek

Former Member
0 Kudos

Vivek - Did you check that the usage type for your system is correctly defined in Solution Manager?

http://<host>:<httpport>/utl/UsageTypesInfo page


Also what is the SUM version you are using for this upgrade.


Thanks,

Manas

manish_singh13
Active Contributor
0 Kudos

Hi Vivek,

Please update if logs are updating on regular basis. Please attach logs here to review.

Thanks,

Manish