cancel
Showing results for 
Search instead for 
Did you mean: 

SAPPRD Group does not come up sql 2000 sp4

Former Member
0 Kudos

Hi

We are on standalone machine  now we have moved the production to cluster

windows 2003 sql 2000 sp4.After Applying the sql 2004 patch

we have restarted  both the nodes.and the SAPPRD Group does not come up.

SapserviceSID also stops when the sapprd groups tries to come up.

event log dispalyes a message have done the kernel upgrade as well

SAPRC: System died. Reason: (null)

Please suggest.

Regards

Jawwad Ali.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

What is your SAP release? How did you setup the MSCS for SAP, what guidelines did you use? See the SAP instance traces in the work directory (\usr\sap\<SID>\DVEBMSG<NR>\work) to figure out why the system is not starting.

Former Member
0 Kudos

Hi

Thanks for the quick response  im trying to start the sap system throught sap MMC

However the disp+work stops and right click on disp+work trace it says

Cannot open file \\sapdb2\saploc\BIG\D90\work\dev_disp

The system cannot find the file specified

Below is the dev_disp log

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


---------------------------------------------------
trc file: "dev_disp", trc level: 1, release: "640"
---------------------------------------------------

Thu Apr 04 18:56:33 2013
kernel runs with dp version 141(ext=102) (@(#) DPLIB-INT-VERSION-141)
length of sys_adm_ext is 312 bytes
sysno      90
systemid   560 (PC with Windows NT)
relno      6400
patchlevel 0
patchno    414
intno      20020600
make:      multithreaded, ASCII
pid        3948

***LOG Q00=> DpSapEnvInit, DPStart (90 3948) [dpxxdisp.c   1167]
call semaphore clean-up function ...
***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c   462]
                                                                                                                                                                                                    
Thu Apr 04 18:56:45 2013
*** WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0079.qqq.nxst) took 12 seconds

Thu Apr 04 18:57:02 2013
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 17 seconds
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  3883]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
***LOG Q06=> DpProfileRead, sapgparam (rdisp/appc_ca_blk_no) [dpxxtool2.c  1025]
*** ERROR => DpIPCInit2: DpProfileRead [dpxxtool2.c  400]
*** DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2
*** DISPATCHER EMERGENCY SHUTDOWN ***
NiWait: sleep (5000 msecs) ...
NiISelect: timeout 5000 ms
NiISelect: maximum fd=1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Thu Apr 04 18:57:07 2013
NiISelect: TIMEOUT occured (5000 ms)
DpHalt: shutdown server >90.sapdb1                               < (normal)
DpJ2eeDisableRestart
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
not attached to the message server
***LOG Q05=> DpHalt, DPStop ( 3276) [dpxxdisp.c   9268]
Good Bye .....

Regards

Jawwad Ali.

Former Member
0 Kudos

Also see the traces dev_w<nr> where <nr> is the work process number and dev_ms for the message server. If you send any additional traces for analysis, send them as attachments using the advanced editor instead of embedding in the message.