SAP Server went down automatically : DpSigInt: caught signal 15

[former_member624329]

Hi,

Yesterday one of our SAP system went down automatically .

On checking found that :

1) Database is up & running fine

2) whereas dpmon showing dpmonInit failed - possibly no dispatcher running

On restart of server, it started successfully

On analysing the issue , in workprocess files I have found

Sun Jun 6 09:36:47 2010

M DpSigInt: caught signal 15

M in_ThErrHandle: 1

M ThSigHandler: signal (step 1, th_errno 11, action 2)

M

M Info for wp 18

M

M pid = 4436

M severity = 0

M status = 0

M stat = WP_RUN

M waiting_for = NO_WAITING

M reqtype = DP_RQ_DIAWP

M act_reqtype = NO_REQTYPE

M rq_info = 0

M tid = -1

M mode = 255

M len = -1

M rq_id = 65535

M rq_source =

M last_tid = 0

M last_mode = 0

M semaphore = 0

M act_cs_count = 0

M csTrack = 0

M csTrackRwExcl = 0

M csTrackRwShrd = 0

M mode_cleaned_counter = 0

M control_flag = 0

M int_checked_resource(RFC) = 0

M ext_checked_resource(RFC) = 0

M int_checked_resource(HTTP) = 0

M ext_checked_resource(HTTP) = 0

M report = > <

M action = 0

M tab_name = > <

M attachedVm = no VM

M PfStatDisconnect: disconnect statistics

M ThIErrHandle: action changed to 2

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP

M TrThHookFunc: called for WP dump

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M ThrSaveSPAFields: save spa fields

M Entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workproc18 4436) [dpuxtool.c 269]

-

---

also in SM21 at that time I could see the error

Error calling the central lock handler

Unable to reach the central lock handler

-

---

Its a BW system with Kernel 700 release

<removed_by_moderator>

Thanks

Deepak Gosain

Edited by: Juan Reyes on Jun 7, 2010 5:16 PM

[Former Member]

Hello Deepak,

If your OS is AIX, then following is the SAPNote relevant to your issue:

Note 488036 - Unable to reach central lock handler, AIX only

This note has specific instructions to change the internal system communication to TCP/IP.

Warm Regards

[Former Member]

This is mainly due to memory unable to handle processess and abruptly shutting the instance - see if there are any stale processes inspite of SAP not running - clear shared memory and start sap again.

Regards

Shailendra