shadow system dispatcher getting down while upgrading 4.7 ECC - 6.0

[Former Member]

Hi ,

I was performing upgrade of 4.7 ECC to 6.0. Due to some power failure server was forcefully shutdown.

I started the server and tried to start the SAP system also. Main instance (4.7 ECC) is working fine but dispatcher of shadow process is getting down.

Developer trace:

Fri Dec 17 10:01:46 2010

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( infpw025sap) [dpxxdisp.c 11822]

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

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

Fri Dec 17 10:01:47 2010

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

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 144

Release check o.K.

Fri Dec 17 10:02:26 2010

• ERROR => DpHdlDeadWp: W0 (pid 3100) died [dpxxdisp.c 14532]

• ERROR => DpHdlDeadWp: W1 (pid 3996) died [dpxxdisp.c 14532]

• ERROR => DpHdlDeadWp: W2 (pid 2800) died [dpxxdisp.c 14532]

• ERROR => DpHdlDeadWp: W3 (pid 3176) died [dpxxdisp.c 14532]

my types changed after wp death/restart 0x1f --> 0x1e

• ERROR => DpHdlDeadWp: W4 (pid 656) died [dpxxdisp.c 14532]

my types changed after wp death/restart 0x1e --> 0x1c

• ERROR => DpHdlDeadWp: W5 (pid 2320) died [dpxxdisp.c 14532]

my types changed after wp death/restart 0x1c --> 0x18

• ERROR => DpHdlDeadWp: W6 (pid 2212) died [dpxxdisp.c 14532]

• ERROR => DpHdlDeadWp: W7 (pid 3296) died [dpxxdisp.c 14532]

• ERROR => DpHdlDeadWp: W8 (pid 2616) died [dpxxdisp.c 14532]

my types changed after wp death/restart 0x18 --> 0x10

• ERROR => DpHdlDeadWp: W9 (pid 1116) died [dpxxdisp.c 14532]

my types changed after wp death/restart 0x10 --> 0x0

• DP_FATAL_ERROR => DpWPCheck: no more work processes

• DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

NiWait: sleep (10000ms) ...

NiISelect: timeout 10000ms

NiISelect: maximum fd=1609

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Fri Dec 17 10:02:36 2010

NiISelect: TIMEOUT occured (10000ms)

dump system status

Kindly suggest some solution to it..

Thanks in advance...

Regards,

Sanjiv

[sunny_pahuja2 · Accepted solution]

Hi,

Have you tried to start shadow system manually ? You can also check SAP Note 525677 - Problems when starting shadow instance.

Also, check logs for shadow instance in the put directory.

Thanks

Sunny