Kernel upgrade procedure in Windows

[Former Member]

This is my first attempt at a kernel upgrade in Windows environment as most everything else is on the AS/400.

Anyways, my questions are: Is the kernel upgrade as easy as this?

1. Download the related kernel file. (*.CAR or *.SAR)

2. Unzip with sapcar -xvf *.CAR/SAR

3. Stop SAP service

4. Take the backup of old kernel located in \usr\sap\<sid>\sys\exe

5. Copy the new kernel to \usr\sap\<sid>\sys\exe\run

6. Now, start the SAP service.

No stopping of the database? No stopping of any other SAP services? Also, do I leave the existing file there and overwrite the existing files leaving the ones not in the new kernel or completely remove it and replace it with the file with only the new files?

I searched for a note on this but didn't find one. Did I just miss it?

Thanks for any help.

Ryan

[Former Member · Accepted solution]

Hello. Best if you read the Note 19466.

Regards.

[Former Member]

Thanks for the responses.

I was hoping I had missed something. My disp+work.exe starts "Running, Message Server connection ok, Dialog Queue time: 0.00 sec" for about a minute but then fails and the service stops.

[Former Member]

Hello, are you patch Kernel in BOTH directories for Windows as in Note 19466 ? If you have trouble after start , first try restart server , after is still same error execute "R3trans -d" in CMD and after check the trans.log in directory where you execute this. Also check the dev_w0 file in work directory. Regards.

[Former Member]

Looks like you may not have copied the new kernel files to \exe\nuc\ or uc (as applicable) directories..

[Former Member]

Dear All,

I performed all steps of Kernel update and my SAP server is up after Kernel update in WINDOWS,but the patch level is not changed.

Trying to update from 720_REL patch level 70 to 720_REL patch level 300

(Operating System-WIN Server 2003(32-bit),Database-MaxD)

I am not able to understand why is it so...??

Please guide me...

Regards,

JUNAID AHMAD

[isaias_freitas]

Hello Junaid,

This thread is 8 years old...

Have you read the SAP note 19466?

Regards,

Isaías

[Former Member]

Hello Isaias,

I read SAP Note and i performed all the steps of Kernel update.

But the problem is after kernel update,patch level is not changed.

Where i went wrong....I need to know.

So please advice me ...!!

Regards,

JUNAID

[Former Member]

Yes,I successfully perform Kernel upgrade.

Kernel is upgraded to patch level-300.

I checked it by OS level :disp+work-It shows patch level-300.

But i am facing another problem:

When i started SAP server via MMC,the disp+work.EXE cannot connect

It shows error--"Not connected to message server,after some time :Dialog queue info unavailable then it stopped.

I also downloaded and copied SAPCRYPTOLIB 5.5.5 into /usr/sap/SID/SYS/exe/uc/NTI386...

But i am unable to start the server.Due to this i am unable to see the patch level via SAP-GUI.

Please guide me....!!

Regards,

JUNAID AHMAD

[raquel_gomez]

Hi Juanid,

As per your information, 'disp+work.EXE' goes into Stopped status, with error:

"Not connected to message server"

After some time

"Dialog queue info unavailable"

And then it is stopped.

Was Message Server up and running?
Please attach to this thread dev_disp and dev_ms trace file.

Regads,
Raquel

[Former Member]

Hello,

Yes.message server is running Ok.

Problem is only with disp+work.EXE

Error:-

"Not connected to message server"

After some time

"Dialog queue info unavailable"

And then it is stopped.

Attached :-  dev_disp trace & dev_ms trace file

Reply...

Regards,

JUNAID AHMAD

dev_disp.txt.zip

dev_ms.txt.zip

[feng_shi]

Hi,

dev_disp:

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

Mon Mar 14 10:00:06 2016

*** ERROR => DpHdlDeadWp: W0 (pid 2252) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W1 (pid 2260) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W2 (pid 2268) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W3 (pid 2280) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W4 (pid 2288) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W5 (pid 2304) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W6 (pid 2312) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W7 (pid 2320) died (severity=0, status=0) [dpxxwp.c     1740]

*** DP_FATAL_ERROR => DpWPCheck: no more work processes

*** DISPATCHER EMERGENCY SHUTDOWN ***

system(dispatcher) could not be started due to all workprocess died.

please upload dev_w0 trace file into this incident for further checking.

Thanks and best regards,

Shi

[Former Member]

Hello,

Please find the attached dev_w0 trace file.

Regards,

JUNAID AHMAD

dev_w0.txt.zip

[raquel_gomez]

Hi Junaid,

Error on the work process trace file is:

C Tue Mar 15 16:13:58 2016

   *** ERROR => different codepage: application=ASCII, application data=UNICODE

  [dbslsdb.cpp  5312]

C  Disconnecting from connection 0 ...

C  Now I'm disconnected from MaxDB

M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1524]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11535]

Is NSP system unicode or non unicode system ?

Regards,
Raquel

[Former Member]

Hi,

1.logon as sidadm

2.Stop the system <stopsap> .

3.Stop saposcol <saposcol -k> .

4.Go to /sapmnt/SID and rename exe to exe old <mv exe exeold> .

5.Uncar the kernel patch to a folder temp <sapcar u2013xvf (package)> .

6.logon to root user with sidadm environment <su root> .

7.Move temp to sapmnt/SID and rename it to exe<mv temp exe> .

8.Go into the exe folder and run saproot <./saproot.sh> .

9.Start the instance <startsap> .

10.Check the current kernel version <disp+work>

Hey check the steps again and gohead with it..

Rakesh