on 10-17-2007 1:50 AM
Hi
We are getting the error "SYSTEM_CORE_DUMPED ->Process terminated by signal 11" with a one user only. We attach the logs from ST22, SM21 and ST11.
===========================================================================================
ST22:
Runtime Error SYSTEM_CORE_DUMPED
Occurred on 16.10.2007 at 19:05:52
Process terminated by signal 11.
What happened?
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "ZPMM_INTERFASE_MIGO" had to be terminated because the
ABAP
processor discovered an invalid system state.
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An SAP System process was terminated by an operating system signal.
-
Possible reasons for this are:
1. Internal SAP System error.
2. Process was terminated externally (by the system administrator).
-
============================================================================================
ST11:
M *****************************************************************************
M *
M * LOCATION SAP-Server prosap2_PDC_20 on host prosap2 (wp 0)
M * ERROR ThSigHandler: signal
M *
M * TIME Tue Oct 16 19:05:50 2007
M * RELEASE 640
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 11
M * MODULE thxxhead.c
M * LINE 9672
M * COUNTER 879
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
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: don't try rollback again
M ThIErrHandle: call ThrCoreInfo
M ThDelEnqInfo: del enq_own >20071016190325991774000420prosap2.........................</1
M ThDelEnqInfo: act enq info: 0
M ThDelEnqInfo: no enq infos
A TH VERBOSE LEVEL FULL
M SigIRegisterRoutine: handler for signal 11 installed (ab_catch_dumperror)
M SigIRegisterRoutine: handler for signal 10 installed (ab_catch_dumperror)
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_VMIT_CLEANUP entered.
A ** RABAX: level LEV_RX_VMIT_CLEANUP completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
================================================================================================
SM21:
19:05:46 DIA 01 800 I91681 R68 Perform rollback
19:05:47 DIA 00 800 I91681 R68 Perform rollback
19:05:47 DIA 00 800 I91681 R68 Perform rollback
19:05:48 DIA 00 800 I91681 R68 Perform rollback
19:05:48 DIA 00 800 I91681 R68 Perform rollback
19:05:50 DIA 00 800 AUTOMATICAS SE38 Q0E Signal 11 received by operating system
19:05:52 DIA 00 800 AUTOMATICAS SE38 Q02 Stop Workproc 0, PID 13803
19:05:54 DIA 00 800 AUTOMATICAS SE38 Q0E Signal 11 received by operating system
19:05:54 DIA 00 800 AUTOMATICAS SE38 R0H Error handling canceled
19:05:55 DIA 00 800 AUTOMATICAS SE38 Q02 Stop Workproc 0, PID 13803
19:06:11 DIA 02 800 I91681 R68 Perform rollback
19:06:11 DIA 02 800 I91681 R68 Perform rollback
19:06:12 DIA 02 800 I91681 R68 Perform rollback
19:06:12 DIA 02 800 I91681 R68 Perform rollback
19:06:18 DIA 01 800 I91681 R68 Perform rollback
==========================================================
Some one can help us about it ?
Best Regards
Reynaldo Rebolledo
Hi Reynaldo,
Pls refer Note 429635 -which might be useful.
Regards
Umesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Reynaldo,
I would start with a system restart to see if it happens again..............if it does open a oss call then start debugging the issues.
Regards
Ravi Raman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.