HowTo exchange Kernel7.00 patchlevel58 to patchlev...

Former Member · ‎01-29-2007

Hi everybody.

I try to exchange the Kernel on a NW04s SAP ECC 6.0.

I followed the procedure as usual:

- Download Kernel Part 1&2 for basis 7.00 stack and DBATL. (patchlevel 83)

- Extracted the SARs, modified the special permissions for BR* and saposcol.

- stopped all running SAP and oracle-Prozesses.

- exchanged the extracted files with the "old" exe-directory

- started sap >startsap

SAP starts without errors. But the surprise is that no login is possible. The SAP-Gui hangs with "waiting for response". After some minutes the gui appears with the message: Connection to partner broken. Then most of the DW-Processes died.

When switching back to old kernel, everythin works fine again. In the work-directory I didn't find any helpfull errormessages.

I've been searching for notes about the way to patch a SAP-Kernel, but I didn't find any differences to thy way I tried.

I tried with patchlevel 58,75 and 83. Every try had the same result. So the mistake has to be on my side.

Does anybody have a hint what mistakes I make?

Former Member · ‎03-27-2007

it doesn't work at windows platform

Former Member · ‎01-29-2007

hi,

can you provide us output of

ls -ltr usr/sap/IDS/SYS/exe

and

disp+work -V without ./

Thanks

Ahmed

Former Member · ‎01-29-2007

You are right, there is a mismatch between dp_lib. But how to correct it?

And why 52 in dev_disp log. The running "old" kernel is level 58. I'm allready confused.

I started from scratch again. There is the protocol about what I did right now (16:00 loc.time) and then the logs:

in /sapmnt/IDS/exe_83

SAPCAR -xvf SAPEXE_83-20001346.SAR

SAPCAR -xvf SAPEXEDB_83-20001348.SAR

SAPCAR -xvf DBATL700O10_22-20001348.SAR

>chmod u+s saposcol br*

>chown root saposcol

>chown oraids br*

>stopsap

>mv /sapmnt/IDS/exe /sapmnt/IDS/exe_orig

>mv /sapmnt/IDS/exe_83 /sapmnt/IDS/exe

>startsap

Versions:

lacerta:idsadm 7> ./disp+work -version

-

disp+work information

-

kernel release 700

kernel make variant 700_REL

compiled on Linux GNU SLES-9 x86_64 cc3.3.3

compiled for 64 BIT

compilation mode UNICODE

compile time Oct 29 2006 20:19:48

update level 0

patch number 83

source id 0.083

-

supported environment

-

database (SAP, table SVERS) 700

operating system

Linux 2.6

lacerta:idsadm 11> ./gwrd -version

-

gateway information

-

kernel release 700

kernel make variant 700_REL

compiled on Linux GNU SLES-9 x86_64 cc3.3.3

compiled for 64 BIT

compilation mode UNICODE

compile time Oct 29 2006 20:04:48

update level 0

patch number 83

source id 0.083

-

supported environment

-

database (SAP, table SVERS) 700

operating system

Linux 2.6

-

trc file: "dev_disp.new", trc level: 1, release: "700"----

sysno 00

sid IDS

systemid 390 (AMD/Intel x86_64 with Linux)

relno 7000

patchlevel 0

patchno 52

intno 20050900

make: single threaded, Unicode, 64 bit, optimized

pid 6240

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 52

Release check o.K.

Mon Jan 29 16:00:43 2007

ERROR => gateway (pid 6272) died [dpxxdisp.c 15075]

DpGwCheck: appc_adm.stat = 2

DP_FATAL_ERROR => Gateway could not be started - I better exit now

dev_rp

[root@lacerta work]# vi dev_rd

Mon Jan 29 16:00:03 2007

***LOG S00=> GwInitReader, gateway started ( 6272) [gwxxrd.c 1686]

systemid 390 (AMD/Intel x86_64 with Linux)

relno 7000

patchlevel 0

patchno 83

intno 20050900

make: single threaded, Unicode, 64 bit, optimized

pid 6272

gateway runs with dp version 218000(ext=109000) (@(#) DPLIB-INT-VERSION-218000-UC)

gw/local_addr : 0.0.0.0

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for monitoring segment.

Bind service sapgw00 (socket) to port 3300

Mon Jan 29 16:00:04 2007

GwPrintMyHostAddr: my host addresses are :

1 : [146.159.24.106] lacerta.gd.srg-ssr.ch (HOSTNAME)

2 : [127.0.0.1] localhost.localdomain (LOCALHOST)

3 : [146.159.36.106] lacerta-giga.gd.srg-ssr.ch (NILIST)

***LOG Q0Z=> DpSysAdmExtCreate, bad version (lib=218000 krn=210000) [dpxxtool2.c 680]

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

*

LOCATION SAP-Gateway on host lacerta / sapgw00
ERROR dp lib version mismatch, please check installation

*

TIME Mon Jan 29 16:00:04 2007
RELEASE 700
COMPONENT DP
VERSION 218000
RC -9999
MODULE dpxxtool2.c
LINE 687

* DETAIL version of external and kernel dp lib mismatch (ext lib

version is 218000 / kernel lib version is 210000)* COUNTER 1

*

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

ERROR => DpIPCInit2: DpSysAdmExtCreate [dpxxtool2.c 368]

***LOG S0V=> GwStopGateway, gateway stopped () [gwxxrd.c 14096]

Former Member · ‎01-29-2007

Hi Andreas,

from the dispatcher trace you have provided we can see that the dispatcher

shutdown itself due to the fact that the gateway died.

For further analysis it would be helpfull to see the dev_rd tracefile. I have seen

problems like this before and most of the time the patchlevel of the dispatcher and

the gateway did not fit. Therefore you also have to check that the disp+work and the gwrd executable have the same patchlevel.

Kind Regards

Thomas Alt

Former Member · ‎01-29-2007

Hi,

for the log it seems you still have files from the old kernel...

-

trc file: "dev_disp.new", trc level: 1, release: "700"

-

sysno 00

sid IDS

systemid 390 (AMD/Intel x86_64 with Linux)

relno 7000

patchlevel 0

patchno 52

intno 20050900

make: single threaded, Unicode, 64 bit, optimized

pid 4955

Can you check this...if your files are different you cannot start SAP

What you can do rename the old exe directory to exe_old. create new exe directory and unpack the files to this new directory to have a clean point..

thanks

Former Member · ‎01-29-2007

Hi, thanks for answering.

J2ee is not installed on this system. I used JSPM on other systems. But on this system I have to try it manually.

The important parts of

dev_disp::

-

trc file: "dev_disp.new", trc level: 1, release: "700"

-

sysno 00

sid IDS

systemid 390 (AMD/Intel x86_64 with Linux)

relno 7000

patchlevel 0

patchno 52

intno 20050900

make: single threaded, Unicode, 64 bit, optimized

pid 4955

Mon Jan 29 14:51:26 2007

kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)

length of sys_adm_ext is 572 bytes

SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 4955) [dpxxdisp.c 1231]

shared lib "dw_xml.so" version 52 successfully loaded

shared lib "dw_xtc.so" version 52 successfully loaded

shared lib "dw_stl.so" version 52 successfully loaded

shared lib "dw_gui.so" version 52 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

.

pShMCreate: allocated gw_adm at 0x2aa471e4a8

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 0x2aa471e4d8

DpShMCreate: allocated wall_adm at 0x2aa471e4e0

MBUF state OFF

EmInit: MmSetImplementation( 2 ).

MM diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation std

EsStdUnamFileMapInit: ES base = 0x0x2aae0a5000

EsStdInit: Extended Memory 4096 MB allocated

<ES> 1023 blocks reserved for free list.

ES initialized.

Mon Jan 29 14:51:29 2007

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1617]

***LOG Q0K=> DpMsAttach, mscon ( lacerta) [dpxxdisp.c 11414]

DpStartStopMsg: send start message (myname is >lacerta_IDS_00 <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Mon Jan 29 14:51:30 2007

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 52

Release check o.K.

Mon Jan 29 14:52:09 2007

ERROR => gateway (pid 4965) died [dpxxdisp.c 15075]

DpGwCheck: appc_adm.stat = 2

DP_FATAL_ERROR => Gateway could not be started - I better exit now

DISPATCHER EMERGENCY SHUTDOWN ***increase tracelevel of WPs

kill(4967,0) successful -> process alive

killing W0-4967 (SIGUSR2)

kill(4968,0) successful -> process alive

killing W1-4968 (SIGUSR2)

.

MiCleanup:

ShmCleanup( 62 )

ShmCreate( 62, 0, 2, 0x0x7fbfffd9d0 )

ShmProtect( 62, 3 )

ERROR => ShmProtect(62,3) shmat(238059539,0x0x2bae0a5000,(SHM_RND | 0)) (22: Invalid argument) [shmux.c 2630]
ERROR => ShmCreate: ShmProtect( 62, 3) failed [shmux.c 1254]
ERROR => ShmCleanup: ShmCreate(62,0,SHM_ATTACH,...) failed. rtc=1 [shmux.c 3017]
ERROR => ShmCleanup: Inv. Key=62 [shmux.c 3058]
ERROR => ShmCleanup(62) failed 2 [mpixx.c 3239]

MpiCleanup() -> 1

removing Semaphore-Management

removing request queue

ShmCleanup( 31 )

ShmCreate( 31, 0, 2, 0x0x7fbfffd9e0 )

ShmProtect( 31, 3 )

ShmProtect: shmat key 31 prot 3/0 done

ShmCreate( 31, 0, 2, -> 0x0x2aac6bc000 )

closing connect handles (dgm + tcp)

DpDelSocketInfo: del info for socket 0 (type=2)

NiICloseHandle: shutdown and close hdl 0 / sock 7

DpDelSocketInfo: del info for socket 1 (type=1)

NiICloseHandle: shutdown and close hdl 1 / sock 8 - sock 9

***LOG Q05=> DpHalt, DPStop ( 4955) [dpxxdisp.c 10347]

shutdown completed - server stopped ***

Good Bye .....

Former Member · ‎01-29-2007

Hi,

As NW04s you can use JSPM to patch you kernel, if you have java add-in installed with your ECC 6.0. As SAP put the exe files in another directory other than /sapmnt/SID/exe i think in /usr/sap/SID/DVEMBGSxx/exe and use sapcpe to synchronize.

go to /j2ee/JSPM...start X server and set DISPLAY variable...

launch ./go and log with SDM password the one you choose when you installed your system...choose single packages screens will help you to patch your kernel...

if you dont have j2ee so you have another problem...

can you send the output of dev_disp and dev_w*

thanks

HowTo exchange Kernel7.00 patchlevel58 to patchlevel83

Accepted Solutions (0)

Answers (7)

Answers (7)

Iterating through JSONModel with multiple nested a...

Re: Connecting SAP CAP with SAP Cloud ALM

How to use CopyProvider on Table created by TypeSc...

How to execute/fire onPost when user press enter o...

Re: Connecting SAP CAP with SAP Cloud ALM