Skip to Content
Former Member
Jun 13, 2009 at 07:46 AM

DISP+WORK Shutdown Immediately


Dear All,

I am facing an issue from past three days on our production server. Following is the explanation for the same:

We daily take backup from OS level in the night and start our SAP server after that(this is done through windows scripts, which are scheduled tasks). This has been a practice for a very long time with out any problems. However, last thursday, after backup when SAP started, I could see that disp+work process got stopped.

Upon further investigation in disp+work log file in /work directory, I could see the below details:

trc file: "dev_disp", trc level: 1, release: "46D"

Thu Jun 11 08:47:55 2009
relno      4640
patchlevel 0
patchno    2337
intno      0
pid        3404

***LOG Q00=> DpSapEnvInit, DPStart (00 3404) [dpxxdisp.c   921]

Thu Jun 11 08:48:01 2009
*** WARNING => DpNetCheck: NiAddrToHost( took 6 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust your DNS settings [dpxxtool2.c  3171]
MtxInit: -2 0 0
DpIPCInit: start server >syeungrp_GRP_00     <
MBUF state OFF
MBUF opmode USE
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation std
<ES> Memory Reset enabled as NT default
<EsNT> EsIUnamFileMapInit: Initialize the memory 2500 MB
<ES> 2499 blocks reserved for free list.
ES initialized.

Thu Jun 11 08:48:02 2009
***LOG Q0K=> DpMsAttach, mscon ( syeungrp) [dpxxdisp.c   8384]
MBUF set hwid_state to HWID_PENDING
DpStartStopMsg: send start message (myname is >syeungrp_GRP_00     <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 10000000 for monitoring segment.

Thu Jun 11 08:48:03 2009
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 4640, patchlevel 0
MBUF component UP
MBUF set hwid_state to SAP_O_K (Y0354306574                             )
DpMsgAdmin: Set patchno for this platform to 2337
Release check o.K.

Thu Jun 11 08:48:11 2009

From the above log, it was obvious that there was some Virtual memory issue. However, we maintain the following virtual memory settings: RAM=2GB; Virtual Memory=4GB