SolMan Upgrade 7.1 SPS 04 Shadow won't start

[Former Member]

Hello we are currently upgrading SolMan to 7.1 SPS 4.

During the MAIN_NEWBAS/STARTSAP_NBAS for some reason the instance won't start! The system loops between SAPSTART and DLTOLDPKGS.

I would love to supply logs but the system doesn't generate any! I've looked everywhere and so far I haven't found any answers for this problem.

Here are some checks that I have made based on various suggestions:

file libsapcrypto.o in /usr/sap/SID/SYS/exe/run - Ok

entry /usr/sap/SID/SOLMANUP/abap/SID/SYS/global/ms_acl_info - Added HOST=* to the file.

entry Start_Program_06 = local $(DIR_EXECUTABLE)/DLTOLDPKGS DSM - commented out of the start program.

Error in the trouble ticket

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

SAPup broke during phase STARTSAP_NBAS in module MAIN_NEWBAS / Downtime II: Conversion, Main Import, XPRAs

Error Message: RFC call to subst_get_uvers failed with key RFC_ERROR_COMMUNICATION (open):

>>> RfcOpenEx ...

Got following connect_param string:

   CLIENT=000 USER=DDIC PASSWD=******* LANG=E ASHOST=sapdsm SYSNR=28 GWHOST=sapdsm GWSERV=sapgw28

<<< RfcOpenEx failed

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

Anyone have any ideas!

Thanks in advance for the help,

Yannick C.

[Former Member · Accepted solution]

Problem solved!

We solved the problem by re-applying the SAPEXE_100 and SAPEXEDB_100. We then shutdown SAP and all existing jobs running under user {sid}ADM and {sid}OFR in all other SBS; QUSRWRK, QINTER.

We then restarted the system.

A good indication that the solution worked, when we restarted the instance the SBS running SAP changed name. from R3_{nr} to SAP{nr}{sid}.

Many thanks for your opinions Volker!

Regards,

Yannick C.

[Former Member]

Hi Yannick,

do you by any chance use SAPEXE 201 ?

This contains ILE 201 and typically acts like this ;-(

You might want to patch to ILE 215 now.

Here is an ugly description, how to do that:

- place ILE_215.SAR to all of your exe directories

/usr/sap/SID/upg/abap/exe, /usr/sap/SID/upg/abap/exenew and /usr/sap/SID/upg/java/exe

- Then:

Call Qp2term

cd into each of the directories

SAPCAR -xvf ILE_215.SAR

- COPY the ILE to SAVF when no SAPHOSTAGENT is running

Copy ILE_TOOLS to SAVF qgpl/ILE_TOOLS with e.g. local FTP

perhaps 3 libs:

SAPSIDUPG

SAPSIDUPGJ

SAPSIDUPG2

- restore the ILE to the LIBs when no SAPHOSTAGENT is running

RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(ILE_TOOLS) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(SAPSIDUPG2)

Run as QSECOFR:

FIXSAPOWN SID(SID) LIB(SAPSIDUPGJ)

=> Restart ...

... good luck,

Regards

Volker Gueldenpfennig

[Former Member]

Thanks for the fast reply Volker, this is becoming a challenge,

Actually, no we are not upgrading using SAPEXE 201. We are installing using SAPEXE 100 and planed to upgrade to SAPEXE 201 post upgrade. Would you recommend to upgrade the kernel now?

Here is the sapmanifest.mf content.

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

Manifest-Version: 1.0

keyname: SAP_KERNEL

keyvendor: sap.com

keylocation: SAP AG

kernel release: 720

kernel patch number: 100

kernel os: as400_pase_64

compilation mode: Non-Unicode

compiled for: 64 BIT

make variant: 720_REL

supported OS releases:  OS400 3 5, OS400 4 5, OS400 1 6, OS400 1 7

supported runtime environment: PASE (with minimum ILE requirements)

downward-compatible to: 700 710 701 702 711 720 730

patch number ILE: 98

patch number LDAP Connector: 36

patch number R3check: 0

patch number R3ldctl: 5

patch number R3load: 98

patch number R3szchk: 5

patch number R3ta: 10

patch number R3trans: 92

patch number RSecSSFx: 0

patch number SAPCAR: 2

patch number SAPSLDREG: 4

patch number SAPinst: 0

patch number SAProuter: 7

patch number ccmagent: 8

patch number cleanipc: 1

patch number cpictlib: 0

patch number db2jcllib: 70

patch number db2radm: 98

patch number dbsl: 98

patch number disp+work: 100

patch number enqueue: 94

patch number gateway: 96

patch number icman: 96

patch number jcmon: 0

patch number jcontrol: 84

patch number jlaunch: 84

patch number jsmon: 43

patch number jstart: 63

patch number lgtst: 0

patch number librfc: 14

patch number msgserver: 92

patch number relinfo: 100

patch number rslgcoll: 4

patch number rslgsend: 2

patch number sapcpe: 6

patch number sapevt: 0

patch number sapftp: 3

patch number saphttp: 7

patch number sapiconv: 3

patch number saplicense: 9

patch number saplikey: 0

patch number sappfpar: 0

patch number sapstart: 5

patch number sapxpg: 5

patch number showipc: 1

patch number tp: 100

patch number vscan_rfc: 64

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

Thanks for your help regards,

Yannick C.

[Former Member]

Hi Yannick,

sorry, no clou what to recommend here ...

I think, I would stick to 100 and still update to ILE 215 ...

Please update to DW 215 on top of 201 after the upgrade, as 201 has some major issues ...

Regards

Volker Gueldenpfennig