Dispatcher shutdown after system startup

[Former Member]

hi all,

i have just updated my kernel 7.00 from patch 133 to patch 185. after system startup, the dispatcher died down with the following entry in dev_disp trace file.

Sun Sep 6 10:15:24 2009

CCMS: Checking Downtime Configuration of Monitoring Segment.

CCMS: start to initalize 3.X shared alert area (first segment).

DpJ2eeLogin: j2ee state = CONNECTED

• ERROR => platform patchno is 133

• ERROR => but my patchno is 185

• DP_FATAL_ERROR => Release inconsistent with running system

• DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

kill(6842,0) successful -> process alive

killing W0-6842 (SIGUSR2)

kill(6843,0) successful -> process alive

any suggestions/advice would be very helpful.

kind regards,

Amer.

Edited by: Amer Zahid on Sep 6, 2009 10:05 AM

[Former Member · Accepted solution]

• ERROR => platform patchno is 133

• ERROR => but my patchno is 185

• DP_FATAL_ERROR => Release inconsistent with running system

Please let us know the environment details

Error shows inconsistency with release, may be wrong kernel files downloaded or may be not placed in both the directories required if it is windows.

drive/sapmnt/SID/exe

drive/usr/sap/SID/SYS/exe/run (uc/nuc)

May be just give a re-try after confirming the files and everything.

[Former Member · Accepted solution]

thanx for your reply.

environment details are as follows:

hardware: HP-UX IA64

OS: HP-UX 11i v3

DB: Oracle 10.2.0.2

i have installed the same kernel thru out my system landscape without any problems. just now, i downloaded the latest kernel patch 221 and installed it to see any positive results. i got the same error:

• ERROR => platform patchno is 133

• ERROR => but my patchno is 221

• DP_FATAL_ERROR => Release inconsistent with running system

• DISPATCHER EMERGENCY SHUTDOWN ***

only now, the second line reads 221 instead of 185.

any suggestions?

kind regards,

Amer

[Former Member · Accepted solution]

once check what version disp+work shows now

as sidadm, disp+work -v | more

and let's check this Note too

Note 409839 - Instance does not start due to inconsistent patch number

[anindya_bose · Accepted solution]

Amer

do you have Dialog instance(s)? If yes, can you shutdown those instances and then try to upgrade kernel in CI only?

In which folder you replaced new kernel files? Did you upgraded files from both SAPEXE and SAPDBEXE?

From SMLG--->F6 . What is the Kernel Patch Level being shown under REL_PATCHNO_00000XXX?

Is it showing the old kernel version or the new one?

[Former Member · Accepted solution]

hi anjali,

the dispmore version shows the latest patch 221. below is the output of the command dispmore -v | more

-

---

disp+work information

-

---

kernel release 700

kernel make variant 700_REL

DBMS client library OCI_102 ()

DBSL shared library version 700.08

compiled on HP-UX B.11.23 U ia64

compiled for 64 BIT

compilation mode UNICODE

compile time Aug 23 2009 21:10:00

update level 0

patch number 221

source id 0.221

-

---

still the error is the same. i am currently looking at note 409839.

kind regards,

Amer.

[Former Member · Accepted solution]

hi anindiya,

we do have a dialog instance running as well but i shut it down before upgrading the kernel. also, the dispatcher dies down after startup so i cannot log in and run SMLG.

any suggestions?

kind regards,

Amer.

[Former Member · Accepted solution]

*** ERROR => platform patchno is 133 
*** ERROR => but my patchno is 221

Please use the kernel lavel 133 .It will solve your issue.

Thanks..

Mohit

[anindya_bose · Accepted solution]

Keep your Dialog in shutdown mode. Just upgrade Kernel of CI and bring up CI only.. Are you getting the same error message?

On which folder you have placed all those new kernel files?

[Former Member · Accepted solution]

hi all,

i shut down both CI and dialog instances and rebooted the server. then i unpacked the kernel patch 221 again and started up CI only. now it is running successfully.

many thanx for all your inputs.

kind regards,

Amer.

[Former Member · Accepted solution]

Hello,

I was facing same problem and got following answer on saptechies which works

Hi,

on CI run tcode - smlg ->go to -> system diagnosis -> message server status area

check the patch level of kernel against dialog instance it is worng delete that entry

restart the application server

Regards,

Nitin Salunkhe