Dispatcher not starting

[Former Member]

Hi guys,

weve patched our sap ecc 6.0 system from 145 to 236 on restarting the service the dispatcher fails to start on win 2008 oracle 10.0.2.0.4. any ideas?

Basisman.

Case changed.

• Do NOT post in UPPERCASE*

Read the "Rules of Engagement"

Edited by: Juan Reyes on Mar 25, 2010 11:47 AM

[p330068]

Hi

Please check the server Defaut Trace log from /usr/sap/SID/j2ee/cluster/serverX/log/defaultTrace.#.trc in server directory

Hope it helps

Regards

Arun

[former_member126060]

Hello Basisman,

Did you checked the dev_disp trace file ?

whats the error appearing in this file ?

can you paste it here .

Regards

Niraj

[Former Member]

Hi guys,

this are the contents of the dev_disp trace file:

-

---

trc file: "dev_disp", trc level: 1, release: "700"

-

---

sysno 00

sid NGQ

systemid 562 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 144

intno 20050900

make: multithreaded, Unicode, 64 bit, optimized

pid 2756

Thu Mar 25 14:32:11 2010

kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)

length of sys_adm_ext is 576 bytes

• SWITCH TRC-HIDE on ***

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

shared lib "dw_xml.dll" version 144 successfully loaded

shared lib "dw_xtc.dll" version 144 successfully loaded

shared lib "dw_stl.dll" version 144 successfully loaded

shared lib "dw_gui.dll" version 144 successfully loaded

shared lib "dw_mdm.dll" version 144 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

Thu Mar 25 14:32:13 2010

• WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0198.qqq.nxst) took 2 seconds

Thu Mar 25 14:32:18 2010

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5371]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >NGQSAP_NGQ_00 <

DpShMCreate: sizeof(wp_adm) 34048 (1480)

DpShMCreate: sizeof(tm_adm) 5652128 (28120)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

DpShMCreate: sizeof(comm_adm) 552080 (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1864)

DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000D400050, size: 6357472)

DpShMCreate: allocated sys_adm at 000000000D400050

DpShMCreate: allocated wp_adm at 000000000D402150

DpShMCreate: allocated tm_adm_list at 000000000D40A650

DpShMCreate: allocated tm_adm at 000000000D40A6B0

DpShMCreate: allocated wp_ca_adm at 000000000D96E550

DpShMCreate: allocated appc_ca_adm at 000000000D974310

DpShMCreate: allocated comm_adm at 000000000D976250

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000D9FCEE0

DpShMCreate: allocated gw_adm at 000000000D9FCF60

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 000000000D9FCF90

DpShMCreate: allocated wall_adm at 000000000D9FCFA0

MBUF state OFF

DpCommInitTable: init table for 500 entries

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

<ES> Info: em/initial_size_MB( 4091MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 4092MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 1022 blocks reserved for free list.

ES initialized.

Thu Mar 25 14:32:19 2010

J2EE server info

start = TRUE

state = STARTED

pid = 1056

argv[0] = C:\usr\sap\NGQ\DVEBMGS00\exe\jcontrol.EXE

argv[1] = C:\usr\sap\NGQ\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=C:\usr\sap\NGQ\SYS\profile\NGQ_DVEBMGS00_NGQSAP

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=65000

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=NGQ

argv[7] = -DSAPMYNAME=NGQSAP_NGQ_00

argv[8] = -DSAPPROFILE=C:\usr\sap\NGQ\SYS\profile\NGQ_DVEBMGS00_NGQSAP

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1633]

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

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

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

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.

Thu Mar 25 14:32:20 2010

DpJ2eeLogin: j2ee state = CONNECTED

Thu Mar 25 14:32:48 2010

MBUF state ACTIVE

Thu Mar 25 14:32:49 2010

DpModState: change server state from STARTING to ACTIVE

Thu Mar 25 14:34:43 2010

J2EE server info

start = TRUE

state = ACTIVE

pid = 1056

http = 50000

https = 50001

load balance = 1

start_lazy = 0

start_control = SAP J2EE startup framework

Basisman.

[paul_power]

Hi,

Ensure you have downloaded and installed both the db dependent and db-indepentent parts of the kernel.

Check SAP note 19466

The standard way for updating kernel patch is:

1. Bring down system and database.

2. Kill any processes that did not die.

3. Cleanipc

4. Tar up/store the entire /sapmnt/<SID>/exe directory for possible need to revert

back to kernel.

5. Copy tar file to safelocation

6. SAPCAR the kernel SAR files in the EXE Directory.

7. Verify ownership/permissions of file for <sid>adm and those that need

to be for ora<sid> (such as brtools) and some for root (such as icmbnd)

(assume you're using ORACLE)

.

8. and FINALLY, start the SAP system

Please ensure that no processes are running on the system. It is also

vital to ensure that the library contained in the shared memory on the

system is updated correctly.

Please make sure your DBSL library is updated correctly also.

If issues persist, check the entries in the sdterr logs and dev_disp in the work directory.

Regards,

Paul

[Former Member]

Hi,

I think your kenal updation was not completed proper.

Please check it,

Thanks

Jibin.

[Former Member]

What error messages do you see in the dev_disp log file located under work directory.

Thanks,

Naveed