We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-basis] Dispatcher Emergency Shutdown => Gateway could not be started

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by Maverick
on Mar 14 at 1:41 PM
I checked note Note 892800 - Dispatcher terminates due to gateway restart problems. I add parameter rdisp/ignore_gw_death = 1
It does not solve the problem, but it helps to troubleshot the error, I could startup SAP and access to SM21:

09:44:49 DIA 002 E1 0 Buffer RSCPCCC Generated with Length 3000000
09:44:50 ENQ 005 GJ 0 Incorrect lock handler configuration
09:44:50 SPO 006 GJ 0 Incorrect lock handler configuration
09:44:50 UP2 007 GJ 0 Incorrect lock handler configuration
09:44:50 UP2 007 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 UP2 007 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 UP2 007 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 UP2 007 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:50 SPO 006 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 SPO 006 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 SPO 006 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 SPO 006 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:50 UP2 007 GJ 0 Incorrect lock handler configuration
09:44:50 UP2 007 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 UP2 007 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 UP2 007 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 UP2 007 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:50 SPO 006 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 SPO 006 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 SPO 006 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 SPO 006 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:50 ENQ 005 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 ENQ 005 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 ENQ 005 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 ENQ 005 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:50 DIA 002 GJ 0 Incorrect lock handler configuration
09:44:50 DIA 002 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 DIA 002 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 DIA 002 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 DIA 002 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:50 DIA 000 GJ 0 Incorrect lock handler configuration
09:44:50 DIA 000 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 DIA 000 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 DIA 000 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 DIA 000 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:50 DIA 003 GJ 0 Incorrect lock handler configuration
09:44:50 DIA 003 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:50 DIA 003 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:44:50 DIA 003 GZ Z > rdisp/enqname=hostname_<SID>_19 enxxhead1393
09:44:50 DIA 003 GZ Z > rdisp/wp_no_enq=1 enxxhead1394
09:44:51 UP1 004 GJ 0 Incorrect lock handler configuration
09:44:51 UP1 004 GJ 2 > No. of enqueue processes in non-lock servers must be 0
09:44:51 UP1 004 GZ Z > rdisp/myname=XX.XX.XX.XX_<SID>_19 enxxhead1392
09:45:08 DP Q0 N Failed to send a request to the message server
09:45:08 DP Q0 N Failed to send a request to the message server
09:45:10 DP Q0 N Failed to send a request to the message server
09:45:10 DP Q0 N Failed to send a request to the message server
09:45:10 DP Q0 N Failed to send a request to the message server
09:45:10 DP Q0 N Failed to send a request to the message server
09:45:10 DP Q0 N Failed to send a request to the message server
09:45:11 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:11 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:11 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:11 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:11 DIA 001 000 SAPSYS GH 0 Error in Central Lock Handler
09:45:11 DIA 001 000 SAPSYS GI 4 > Dequeue All call failed
09:45:11 DIA 000 000 A1 0 Initialization complete
09:45:11 DP Q0 N Failed to send a request to the message server
09:45:12 DP Q0 N Failed to send a request to the message server
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:12 DIA 001 000 SAPSYS GH 0 Error in Central Lock Handler
09:45:12 DIA 001 000 SAPSYS GI 4 > Dequeue All call failed
09:45:12 DIA 001 000 SAPSYS D0 1 Transaction Canceled TK 732 ( )
09:45:12 DIA 001 000 SAPSYS D0 1 Transaction Canceled TK 732 ( )
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 4 > Dequeue All call failed
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 4 > Dequeue All call failed
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 2 > Unable to reach central lock handler
09:45:12 DIA 001 000 SAPSYS GI 0 Error calling the central lock handler
09:45:12 DIA 001 000 SAPSYS GI 4 > Dequeue All call failed
09:45:28 DP Q0 I Operating system call connect failed (error no. 239 )
09:45:43 DIA 002 Q0 2 Stop Workproc 2, PID 8505
09:45:43 ENQ 005 Q0 2 Stop Workproc 5, PID 8508
09:45:43 UP1 004 Q0 2 Stop Workproc 4, PID 8507
09:45:43 DIA 003 Q0 2 Stop Workproc 3, PID 8506
09:45:43 UP2 007 Q0 2 Stop Workproc 7, PID 8511
09:45:43 SPO 006 Q0 2 Stop Workproc 6, PID 8510
09:45:43 DIA 000 Q0 2 Stop Workproc 0, PID 8502
09:45:43 DIA 001 Q0 2 Stop Workproc 1, PID 8503
09:45:49 DP Q0 5 Stop SAP System, Dispatcher Pid 84

---------------Original Message---------------
From: Maverick
Sent: Sunday, March 13, 2011 1:34 PM
Subject: Dispatcher Emergency Shutdown => Gateway could not be started

Hello,

This a clone system refreshed...

When I try to starty SAP, it kills the process after few seconds. I think the problem is the communication between Message Server and the rest of the SAP Process:

NN: Means Instance number

dev_ms:

[Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 16087) [msxxserv_mt. 1847]
[Thr 01] SigISetDefaultAction : default handling for signal 18
[Thr 01] ***LOG Q0I=> NiIBindSocket: bind (226: Address already in use) [nixxi.cpp 3237]
[Thr 01] *** ERROR => NiIBindSocket: SiBind failed for hdl 1 / sock 9
(SI_EPORT_INUSE/226; I4; ST; 0.0.0.0:39NN) [nixxi.cpp 3237]
[Thr 01] *** ERROR => MsSCommInit: NiBufListen(39NN) (rc=NIESERV_USED) [msxxserv_mt. 10217]
[Thr 01] *** ERROR => MsSInit: MsSCommInit (internal) [msxxserv_mt. 1900]
[Thr 01] *** ERROR => main: MsSInit [msxxserv_mt. 5983]
[Thr 01] ***LOG Q02=> MsSHalt, MSStop (Msg Server 16087) [msxxserv_mt. 6025]

SIDadm> niping -c -H <hostname/IP> -S 39NN

***LOG Q0I=> NiPConnect: connect (239: Connection refused) [nixxi.cpp 2518]
*** ERROR => NiPConnect: SiConnect failed for hdl 0 / sock 3
(SI_ECONN_REFUSE/239; I4; ST; xx.xx.xx.xx:39NN) [nixxi.cpp 2518]
*** ERROR => NiTClientLoop: NiHandle (rc=-10) [nixxtst.cpp 2839]
* ERROR partner 'XX.XX.XX.XX:39NN' not reached
* RELEASE 701
* COMPONENT NI (network interface)
* VERSION 38
* RC -10
* MODULE nixxi.cpp
* LINE 2518
* DETAIL NiPConnect
* SYSTEM CALL connect
* ERRNO 239
* ERRNO TEXT Connection refused
* COUNTER 2

dev_disp

rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0I=> NiPConnect: connect (239: Connection refused) [nixxi.cpp 2518]
*** ERROR => NiPConnect: SiConnect failed for hdl 2 / sock 11
(SI_ECONN_REFUSE/239; I4; ST; xx.xx.xx.xx:39NN) [nixxi.cpp 2518]
*** ERROR => MsIAttachEx: NiBufConnect to 10.44.10.69/3919 failed (rc=NIECONN_REFUSED) [msxxi.c 647]
***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c 1816]
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
*** ERROR => MsISnd2: not_attached [msxxi.c 1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 4984]
*** ERROR => MsISnd2: not_attached [msxxi.c 1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 5105]
***LOG Q0I=> NiPConnect: connect (239: Connection refused) [nixxi.cpp 2518]
*** ERROR => NiPConnect: SiConnect failed for hdl 5 / sock 14
(SI_ECONN_REFUSE/239; I4; ST; xx.xx.xx.xx:39NN) [nixxi.cpp 2518]
*** ERROR => MsIAttachEx: NiBufConnect to xx.xx.xx.xx/39NN failed (rc=NIECONN_REFUSED) [msxxi.c 647]
*** ERROR => gateway (pid 16091) died [dpxxdisp.c 16622]
DpGwCheck: appc_adm.stat = 2
*** DP_FATAL_ERROR => Gateway could not be started - I better exit now
*** DISPATCHER EMERGENCY SHUTDOWN ***

I added the following entries in /etc/services:

sapmsSID 39NN/tcp #sap service for SID
lsnrSID 15NN/tcp #sap Oracle listener for SID

Profile Parameters:

rdisp/msserv_internal = 39NN
rdisp/sna_gw_service = sapgwNN

Checked the some notes, but at this momment I think the problem is at Operating System Level

Note 1341701 - partner 'hostname:service' not reached
Note 164937 - NiPBind: service 'sap????' in use
Note 540379 - Ports and services used by SAP
TCP/IP Ports Used by SAP Applications
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/d ocs/library/uuid/4e515a43-0e01-0010-2da1-9bcc452c280b

Thanks in advance,
Mav

__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
  
Most Popular White Papers

In the Spotlight
Get Fast, Reliable Enterprise-Class Storage. Learn About IBM Storwize v7000
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language