cancel
Showing results for 
Search instead for 
Did you mean: 

Kernel Upgrade Message server entry problem

Former Member
0 Kudos

Hallo,

My system

kernel release 700

kernel make variant 700_REL

compiled on HP-UX B.11.23 U ia64

patch number 114

We patched the syste to 221. There are two instances on this system. But the error comes below - system does not comes up.

dev_disp

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

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

**ROR => platform patchno is 114 114 [dpxxdisp.c 18253]

      • ERROR => but my patchno is 221 [dpxxdisp.c 18254]

      • DP_FATAL_ERROR => Release inconsistent with running system

      • DISPATCHER EMERGENCY SHUTDOWN ***

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

I have seen note number 409839. I dont understand the solution.

Do I delete the message server entry in RZ03 -> Utilities-> diagnosis-> message server status area pertaining Rel_patch_number ?

Where do I take the message server entry from ?

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

Please help if you had similar problems and solved them.

Accepted Solutions (0)

Answers (2)

Answers (2)

JPReyes
Active Contributor
0 Kudos

platform patchno is 114 114 http://dpxxdisp.c 18253

      • ERROR => but my patchno is 221

Seems like you have patch the dialog instance and the CI is still 114...

kernel should be released on /sapmnt/SID/exe so it can be distribute... start first the CI and then the DI.

Regards

Juan

Former Member
0 Kudos

The usual procedure were followed.

I am still searching for the fault.

Former Member
0 Kudos

SAP note 409839 perhaps?

It seems you patched only one of your two instances.

Did you stop and restart both instances?

Edited by: Joe Bo. on Sep 30, 2009 9:42 AM

Former Member
0 Kudos

Thanks to both ,

We have patched the directory

/sapmnt/PCP/exe

and of course both AI and CI share this directory.

Also, we have a script stopsap_all So It starts CI and AI in order.

JPReyes
Active Contributor
0 Kudos

Well for some reason your CI seems to be sticking with your old kernel. Please start the CI on its own and check that the kernel is 221

Regards

Juan

Former Member
0 Kudos

I found something in the AI

actually the exe directory is not linked to the kernel. This looks unusual. As exe here should be linked to the /sapmnt/SID/exe

s96pnp20:pcpadm 43> pwd

/usr/sap/PCP/D01

s96pnp20:pcpadm 44> ls -ltr

total 22

drwxr-xr-x 7 pcpadm sapsys 96 Jun 1 2008 igs

drwxr-xr-x 2 pcpadm sapsys 96 Jun 1 2008 sec

drwxr-xr-x 2 pcpadm sapsys 96 Jun 1 2008 log

drwxr-xr-x 5 pcpadm sapsys 4096 Jul 3 20:38 exe

drwxr-xr-x 4 pcpadm sapsys 2048 Sep 30 10:00 data

drwxr-xr-x 2 pcpadm sapsys 5120 Sep 30 10:14 work

JPReyes
Active Contributor
0 Kudos

Then you need to create a softlink to the /sapmnt/<SID>/exe directory or copy the kernel manually

Regards

Juan

Former Member
0 Kudos

I will try this,

Ok thanks.

Lets see.

But my collegue says - CI also did not come up. But there kernel was fine,

anyways.

Will give feedback. Thanks.