Sap kernel update not reflected on disp+work

[muhammadhafidz_binajis]

Hi,

I try to update kernel patch for my Dev server on Windows 2003 server from 133 to 185.

This is 1st time i try to do kernel patch on windows server. I want to change the kernel to 185 by follow "How to do a Manual Kernel Upgrade of an SAP Server" - by Hemant Kumar. And other kernel upgrade notes and guide from internet too.

Is there anything else i should do? Update profile or anything? BTW... im not sure if i put the new kernel update on the right folder. This is because, i copy the folder \usr\sap\SID\sys\exe\uc\NTAMD64. Even if put the same thing on \usr\sap\SID\DVEBMGS00\exe\, the same thing will still will occured.

So now, no matter what kernel that i put on. Apps server still run but disp+work and SM51 still not reflected to the new kernel but still show kernel no 133.

Any advice? Thanks in advance.

[former_member227283]

Hi Muhammad,

Pls let us know which of the file you have download from SAP SMP.

Pls paste the file name in forum.

Thanks

Anil

[Former Member]

- start your SAP system

- logon to it

- run transactoin SE38 and report rsparam

- check the value of DIR_CT_RUN (the source directory of the replictaion process)

this is the directory where you have to unpack the patches to

- check the value of DIR_EXECUTABLE (the destination directory of the sapcpe replication and the instance executable directory)

- if the replication still fails, see DVEBMGS00\work\sapcpe.log for details.

regards

Peter

[Former Member]

Hi,

Have a look in your start profile and see where the kernel is being loaded......

Keep an eye out for sapcpe.

Mark

[muhammadhafidz_binajis]

Hi,

Since this is my 1st time i patch the kernel server i've made a silly mistakes. I missout some of the file as what Sunny Pahuja told. So now DEV server is running. Disp+work and SM5 is showing the kernel no 185.

But i try the same steps on UAT server which is situated at the same physical server + sharing the same DEV Database (which i update the kernel no 185 earlier this forum). SapMMC show it in Yellow color. With status on Disp+work-Dispatcher - "'Running but Dialog Queue info unavailable." But i can still login into SAPGui, check on disp+work which is updated to kernel no 185.

I found this one link (below) in google. It says that i need to run sapstartsrv on my UAT folder. I try to run it but i'm not quite sure a what should i put in. Anyone had try this one before? I'm not sure about the NR and profile.

Thanks a lot...

Link - http://sap.ittoolbox.com/groups/technical-functional/sap-basis/kernel-upgrade-results-in-error-messa...

[sunny_pahuja2]

Hi,

Check SAP Note 396309 - Dispatcher remains yellow, although the system is running

Also, try following if above will not solve your problem:

Log into the NT machine as <SID>adm.

1) Stop All service first and the follow step below.

2) Run 'sapstartsrv.exe'.

3) Select "Uninstall Service + Unregister COM Interface"

4) Specify your SID and System Number (NR) and click ok.

5) Select "Install Service + Register COM Interface + Start Service

6) Specify your SID and System Number (NR).

7) Specify your startprofile (use the 'browse' button).

😎 Specify your user as (domain\<SID>adm or workgroup\<SID>adm).

9) Specify the passsword for <SID>adm.

10) Click OK.

Then start system again.

Thanks

Sunny

[former_member227283]

Hi ,

As you said you have copied the new kernal to NTAMD64

Pls login to SAP OS then goto to directory NTAMD64

then run the command :- disp+work -version and check what version of file shows in NTAMD64 directory and let us know.

If it shows version 185 , then you have to manually replicate the kernal from NTAMD64 to exe.

Thanks

Anil

[muhammadhafidz_binajis]

Hi all,

Thanks for the reply

Currently i tried all the steps above. But for latest one. This is what i did.

-I stop the apps server.

-Copy the original kernel no 133 at \usr\sap\SID\sys\exe\uc\NTAMD64 as a backup.

-Then overwrite the old 133 with the new one. Change their owner, security.

-Restart apps server using the sapMMC and start saposcol services.

I try to run the command disp+work at Drive:\usr\sap\SID\sys\exe\uc\NTAMD64. But it still show 133.

Then i try to check on the RUN folder in C:\usr\sap\SID\sys\exe\ as what Anindya Bose said earlier. The files still not update automatically. So I bring down the apps server again. So i copy the old Run133 as a backup before i overwrite with the new Run185 executeable files. Then start the apps server again.

I still get the kernel no 133 on disp+work command. However I notice that a few files in Drive:\usr\sap\SID\DVEBMGS00\exe\ has been update to a new 185.

I want to confirm. I find out that in Drive:\usr\sap\SID\sys\exe\uc\NTAMD64 files like stopsap, startsap sapstart and many more files is still not update to 185. File version is still 133 even after all of those steps above. Is this the cause of this problem? Any file that i missout to download somewhere? BTW, I update this job only by using the SAPEXEDB_185-20001356.SAR files.

Thank you.

[former_member204746]

stop the APPS server. when ficinshed, close SAPMMc

check SAP services, go for propertirs of SAP[SId]_00 servcie and set it to DISABLED.

nowm, copy the kernel again. when done test it:

C:

cd \usr\sap\SID\sys\exe\uc\NTAMD64

disp+work -V | more

to be safe, copy the kernel in these directories too:

C:\usr\sap\SID\sys\exe

C:\usr\sap\SID\DVEBMGS00\exe

when completed, enable the SAP[SID]_00 service again and start it.

start SAP with SAPMMC.

Good luck.

[sunny_pahuja2]

Hi,

Where is database independent part ?

You have to update your kernel using both SAPEXEDB_<version>.SAR and SAPEXE_<version>.SAR file ..

Thanks

Sunny

[anindya_bose]

>However I notice that a few files in Drive:\usr\sap\SID\DVEBMGS00\exe\ has been update to a new 185.

are those brtools executables?

It seems you have only downloaded database dependent execs but not the database independent part. Please also download

SAPEXE_185-<some number..SAR. This will contain rest of the executables

[anindya_bose]

Do you have more than One SAP Instances?

If you have changed something on the Dialog instances , then revert back the same.

Keep DIALOG instance down ( if you have). On your CI, just place the new executable in the directory \usr\sap\SID\sys\exe\uc\NTAMD64.

No need to keep anything anywhere else. SAPCPE.exe will take care of that. After placing the file, restart central Instance and from the command prompt of the CI , run "disp+work". It will tell you the Kernel patch level. If you see it is showing 185 , then only restart DIALOG instances ( if you have).

If still getting problem then perhaps you are doing some wrong mistake. If you are not sure about something, you can take a backup of your SYS/exe/run folder and then replace the new executables in the "run" folder. SAP reads from this folder during runtime.

Edited by: Anindya Bose on Oct 26, 2009 1:15 PM

[muhammadhafidz_binajis]

Hi Anindya Bose

Thanks for your reply.

1st of all, we are running 2 instance in one server. Development and UAT. The one that we try now is Dev. Is there any difference in kernel patching between running 2 instances and 1 instance?

Here is what we did:

1. Download kernel patch 185 from OSS.

2.Uncar the '185' file at my workstation and transfer the file to the server desktop.

3.then we shutdown the app server and saposcol service.

4.then we copied the '133' NTAMD64 folder and rename it to NTAMD64_old as a backup.

5. then we copied the content of the '185' kernel file and replace them in the '133' NTAMD64 folder.

6. then we changed the owner and security of the files n folders according to the backuped version.

7. lastly we bring up the app server and the saposcol service.

After completing these steps, the disp+work still shows the kernel number 133.

Do we need to run the sapcpe.exe manually?

Thank you,

Hafidz Ajis

[Former Member]

Procedure will be the same if you have one more SAP Applications servers installed in one physical host.

For Eg: Dev is your Dev server.

Login as SIDADM -- devadm user

Stop the SAP Application and as well as the SAP related services (services.msc).

Take a backup of the kernel (run) directory (/usr/sap/DEV/SYS/exe/run/NTAMD*)

over write the kernel files SAPEXE.SAR & SAPEXEDB.SAP in the /usr/sap/DEV/SYS/exe/run/NTAMD*.

after overwritting the files run the disp+work -v | more from /usr/sap/DEV/SYS/exe/run/NTAMD* dir.

Now you would be able to get the upgraded kernel verison

[anindya_bose]

you do not need to run SAPCPE.exe.. everytime you start SAP from MMC, SAPCPE program runs and copies executables from NTADM64 directory to SYS/exe/run if there is any difference between the version of the executables in those folder. It also copies executable for DIALOG instance.

UAT and DEV are two instances or two clients?