Register Login

Dispatcher fails.

Updated May 18, 2018

In the sap console the dispatches fails after starting for few minutes. msg_server and igswd are running.
when I look at the system log
i see this error: SAP Basis System: Initialization DB-Connect Failed, Return Code 004096
and Database: Table SVERS is not in the database
I did a developer trace on the dispatcher foolowing is the info
-------------------------------------------------------------------------------------------
Wed Dec 20 16:38:05 2006
kernel runs with dp version 128(ext=102) (@(#) DPLIB-INT-VERSION-128)
length of sys_adm_ext is 312 bytes
systemid 560 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 21
intno 20020600
make: multithreaded, ASCII
pid 3992

***LOG Q00=> DpSapEnvInit, DPStart (02 3992) [dpxxdisp.c 1100]
shared lib "dw_xml.dll" version 21 successfully loaded
shared lib "dw_xtc.dll" version 21 successfully loaded
shared lib "dw_stl.dll" version 21 successfully loaded
shared lib "dw_gui.dll" version 21 successfully loaded

Wed Dec 20 16:38:10 2006
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3886]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: JAVA is not active
DpShMCreate: sizeof(wp_adm) 10768 (828)
DpShMCreate: sizeof(tm_adm) 2219848 (11044)
DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpShMCreate: sizeof(comm_adm) 192000 (384)
DpShMCreate: sizeof(vmc_adm) 0 (320)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: SHM_DP_ADM_KEY (addr: 04960040, size: 2509560)
DpShMCreate: allocated sys_adm at 04960040
DpShMCreate: allocated wp_adm at 049617A8
DpShMCreate: allocated tm_adm_list at 049641B8
DpShMCreate: allocated tm_adm at 049641E0
DpShMCreate: allocated wp_ca_adm at 04B82128
DpShMCreate: allocated appc_ca_adm at 04B86778
DpShMCreate: allocated comm_adm_list at 04B87EE8
DpShMCreate: allocated comm_adm at 04B87F00
DpShMCreate: allocated vmc_adm_list at 04BB6D00
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 04BB6D28
DpShMCreate: allocated wall_adm at 04BB6D30
MBUF state OFF
EmInit: MmSetImplementation( 2 ).
<es>client 0 initializing ....
<es>InitFreeList
<es>block size is 1024 kByte.
Using implementation std
<esnt>Memory Reset enabled as NT default
<esnt>EsIUnamFileMapInit: Initialize the memory 500 MB
<es>499 blocks reserved for free list.
ES initialized.
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( SAPSERV-2) [dpxxdisp.c 9719]
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.

Wed Dec 20 16:38:11 2006
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6400, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]
DpMsgAdmin: Set patchno for this platform to 21
Release check o.K.

Wed Dec 20 16:38:50 2006
*** ERROR => W0 (pid 2376) died [dpxxdisp.c 12170]
*** ERROR => W1 (pid 2384) died [dpxxdisp.c 12170]
*** ERROR => W2 (pid 2392) died [dpxxdisp.c 12170]
*** ERROR => W3 (pid 2400) died [dpxxdisp.c 12170]
*** ERROR => W4 (pid 864) died [dpxxdisp.c 12170]
my types changed after wp death/restart 0xbf --> 0xbe
*** ERROR => W5 (pid 2408) died [dpxxdisp.c 12170]
my types changed after wp death/restart 0xbe --> 0xbc
*** ERROR => W6 (pid 2416) died [dpxxdisp.c 12170]
my types changed after wp death/restart 0xbc --> 0xb8
*** ERROR => W7 (pid 2424) died [dpxxdisp.c 12170]
*** ERROR => W8 (pid 2432) died [dpxxdisp.c 12170]
*** ERROR => W9 (pid 2456) died [dpxxdisp.c 12170]
*** ERROR => W10 (pid 2464) died [dpxxdisp.c 12170]
my types changed after wp death/restart 0xb8 --> 0xb0
*** ERROR => W11 (pid 2036) died [dpxxdisp.c 12170]
my types changed after wp death/restart 0xb0 --> 0xa0
*** ERROR => W12 (pid 2044) died [dpxxdisp.c 12170]
my types changed after wp death/restart 0xa0 --> 0x80
*** DP_FATAL_ERROR => DpWPCheck: no more work processes
*** DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
killing W0-2376 (SIGUSR2)
*** ERROR => DpWpKill(2376, SIGUSR2) failed [dpxxtool.c 2468]
killing W1-2384 (SIGUSR2)
*** ERROR => DpWpKill(2384, SIGUSR2) failed [dpxxtool.c 2468]
killing W2-2392 (SIGUSR2)
*** ERROR => DpWpKill(2392, SIGUSR2) failed [dpxxtool.c 2468]
killing W3-2400 (SIGUSR2)
*** ERROR => DpWpKill(2400, SIGUSR2) failed [dpxxtool.c 2468]
killing W4-864 (SIGUSR2)
*** ERROR => DpWpKill(864, SIGUSR2) failed [dpxxtool.c 2468]
killing W5-2408 (SIGUSR2)
*** ERROR => DpWpKill(2408, SIGUSR2) failed [dpxxtool.c 2468]
killing W6-2416 (SIGUSR2)
*** ERROR => DpWpKill(2416, SIGUSR2) failed [dpxxtool.c 2468]
killing W7-2424 (SIGUSR2)
*** ERROR => DpWpKill(2424, SIGUSR2) failed [dpxxtool.c 2468]
killing W8-2432 (SIGUSR2)
*** ERROR => DpWpKill(2432, SIGUSR2) failed [dpxxtool.c 2468]
killing W9-2456 (SIGUSR2)
*** ERROR => DpWpKill(2456, SIGUSR2) failed [dpxxtool.c 2468]
killing W10-2464 (SIGUSR2)
*** ERROR => DpWpKill(2464, SIGUSR2) failed [dpxxtool.c 2468]
killing W11-2036 (SIGUSR2)
*** ERROR => DpWpKill(2036, SIGUSR2) failed [dpxxtool.c 2468]
killing W12-2044 (SIGUSR2)
*** ERROR => DpWpKill(2044, SIGUSR2) failed [dpxxtool.c 2468]
NiWait: sleep (10000 msecs) ...
NiISelect: timeout 10000 ms
NiISelect: maximum fd=1617
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Dec 20 16:39:00 2006
NiISelect: TIMEOUT occured (10000 ms)
dump system status
Workprocess Table (long) Wed Dec 20 21:39:00 2006
========================

No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
-----------------------------------------------------------------------------------------------------------------------
0 DIA 2376 Ended no 1 0 0
1 DIA 2384 Ended no 1 0 0
2 DIA 2392 Ended no 1 0 0
3 DIA 2400 Ended no 1 0 0
4 DIA 864 Ended no 1 0 0
5 UPD 2408 Ended no 1 0 0
6 ENQ 2416 Ended no 1 0 0
7 BTC 2424 Ended no 1 0 0
8 BTC 2432 Ended no 1 0 0
9 BTC 2456 Ended no 1 0 0
10 BTC 2464 Ended no 1 0 0
11 SPO 2036 Ended no 1 0 0
12 UP2 2044 Ended no 1 0 0
Dispatcher Queue Statistics Wed Dec 20 21:39:00 2006
===========================

+------+--------+--------+--------+--------+--------+
| Typ | now | high | max | writes | reads |
+------+--------+--------+--------+--------+--------+
| NOWP | 0 | 3 | 2000 | 10 | 10 |
+------+--------+--------+--------+--------+--------+
| DIA | 5 | 5 | 2000 | 5 | 0 |
+------+--------+--------+--------+--------+--------+
| UPD | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| ENQ | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| BTC | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| SPO | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| UP2 | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+


max_rq_id 13
wake_evt_udp_now 0

wake events total 9, udp 8 ( 88%), shm 1 ( 11%)
since last update total 9, udp 8 ( 88%), shm 1 ( 11%)


Dump of tm_adm structure: Wed Dec 20 21:39:00 2006
=========================

Term uid man user term lastop mod wp ta a/i (modes)

Workprocess Comm. Area Blocks Wed Dec 20 21:39:00 2006
=============================

Slots: 300, Used: 1, Max: 0
+------+--------------+----------+-------------+
| id | owner | pid | eyecatcher |
+------+--------------+----------+-------------+
| 0 | DISPATCHER | -1 | *WPCAAD000* |

NiWait: sleep (5000 msecs) ...
NiISelect: timeout 5000 ms
NiISelect: maximum fd=1617
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Dec 20 16:39:05 2006
NiISelect: TIMEOUT occured (5000 ms)
Shutdown server ...
DpModState: buffer in state MBUF_PREPARED

NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes...
Stop gateway
killing process (2352) (SOFT_KILL)
Stop icman
killing process (2368) (SOFT_KILL)
Terminate gui connections
[DpProcDied] Process lives (PID:2352 HANDLE:1596)
waiting for termination of gateway
NiWait: sleep (1000 msecs) ...
NiISelect: timeout 1000 ms
NiISelect: maximum fd=1617
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Dec 20 16:39:06 2006
NiISelect: TIMEOUT occured (1000 ms)
[DpProcDied] Process died (PID:2352 HANDLE:1596)
[DpProcDied] Process died (PID:2368 HANDLE:1588)
DpHalt: cancel all lcom connections
MPI CancelAll 2 -> 0
MPI DeleteAll 2 -> 0
NiIMyHostName: hostname = 'SAPSERV-2'
AdGetSelfIdentRecord: > AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 163 bytes

NiBufSend starting
NiIWrite: write 562, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name -, type 4, key -
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 9945]

NiBufSend starting
NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiSelClear: removed hdl 3 from selectset
MBUF state OFF
AdGetSelfIdentRecord: > AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/13
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 19)
MBUF component DOWN
NiBufClose: clear extensions for hdl 3
NiBufSetStat: bufstat of hdl 3 changed from OK to OFF
NiICloseHandle: shutdown and close hdl 3 / socket 1604
MsIDetach: detach MS-system
EsCleanup ....
***LOG Q05=> DpHalt, DPStop ( 3992) [dpxxdisp.c 8478]
Good Bye .....
---------------------------------------------------------------------------------

Thanks

RTR


Comments

  • 30 Jan 2014 4:13 am PrithviRaj Best Answer

    Hi,

    Its very simple... Stop your sap system in the mmc and then restart your db services...Later start your sap system...It should work :)   CHEERS!!!

  • 29 Nov 2008 10:54 pm Guest
    How did u solve the issue ?
  • 17 Jun 2009 3:20 pm Guest
    Could you please tell how you solve this problem,we also got same error in our system which got resolved by restarting the server & application.But if there is any other solution, please share it so as to avoid this problem in future.

    Warm Regards
    Joy Garg
  • 04 Jul 2009 11:47 am Guest
    in my case same error in our system which is not resolved by starting server & application.
    Please help if anybody know the solution.

    warm regards

    Muskan
  • 06 Jul 2009 6:16 am Guest
    Hi,

    Try going to services.msc and stop and restart all the oracle services for that instance. Then manually start the database and then start the SAP instance. I think it should work.

    Regards,
    ZK
  • 15 Sep 2009 7:00 am arun kumar
    The same problem arose for me when i tried to start the db server,can u please tell me the process of, how to overcome that issue.
  • 03 Feb 2010 5:26 am Anil Kumar
    you can check ur services. he is working fine.
  • 23 Feb 2010 11:42 am mayank seth
    hi there type r3trans -d at cmd and check the logs in the log file generally if it coming 0 that means connectivity to database is there otherwise if it is returning with some code then check it on net
  • 09 Apr 2010 8:44 pm Guest
    Realice un restore de la base de datos subio la instacion le cambien el
  • 21 Dec 2010 5:53 pm Guest
    i am also facing the same dispatcher stops working for some time i tried restarting the application & server so how to go around with this issue if any1 know a solution for this problem kindly help
  • 06 Jan 2011 8:13 am Guest
    Hi,
    First login to app server with oraSID user, check the lisnter status(in linix: lsnrctl -status) if it is not running, then you have to start the database, to start the db manually run the following command: sqlplus "/as sysdba", after login type startup. then exit from sql prompt then start the listner(lsnrctl -start).
  • 23 Apr 2012 9:55 am Nitin Joshi
    Hi I also faced same issue. I just login through SIDADM and SET environment variable MSSQL_FORCEOLEDB=1, restart the database services.. problem solved.. Note NO: 1082356

×