cancel
Showing results for 
Search instead for 
Did you mean: 

system_core_dumped

Former Member
0 Kudos

Hi

I am getting following error . Process terminated by signal 0

The current ABAP "SAPLSD41" program had to be terminated because the

ABAP processor detected an internal system error.

An R/3 System process was terminated by an operating system signal.

-

Possible reasons for this are:

1. Internal system error.

2. Process was terminated externally (by the system administrator).

-

Last error logged in SAP kernel

Component............ "Taskhandler"

Place................ "SAP-Server sugarland_DE1_11 on host sugarland (wp 1)"

Version.............. 1

Error code........... 11

Error text........... "ThSigHandler: signal"

Description.......... " "

System call.......... " "

Module............... "thxxhead.c"

Line................. 10852

The error reported by the operating system is:

How to correct the Error

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often

contains a file called 'core'.

Save this file under another name.

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

Error number..... " "

Information on where terminated

Termination occurred in the ABAP program "SAPLSD41" - in "SYSTEM-EXIT".

The main program was "SAPMSRD0 ".

In the source code you have the termination point in line 0

of the (Include) program " ".

Need your advice on this?

Thanks

Srikanth

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member189546
Active Contributor
0 Kudos

Hello,

Please check note

note 1555682 Defective stack kernel 7.00 SP23, 7.01 SP08, 7.02

Please apply latest disp+work and dbsl patches.

regards,

John Feely

markus_doehr2
Active Contributor
0 Kudos

I would check the "analysis" section of the dump in ST22 to see, where the core dump occurs (database client, SAP kernel) - then go from there.

Markus

Former Member
0 Kudos

Thanks all for advice,

The kernel current level is 700 - package level 278.

Regards

Srikanth

former_member184473
Active Contributor
0 Kudos

Hello Srikanth,

This kernel version is from December 2010. Have you tried with version 330 (December 2011)?

Regards,

Eduardo Rezende

markus_doehr2
Active Contributor
0 Kudos

If you post what you see in the analysis section 8the stack) one can figure, where the error occurs. If it's e. g. in the database client then an exchange of a kernel is of no help.

Markus

Former Member
0 Kudos

Not tried yet version 330. This kind of error occurs for only particular user . I will upgrade kernel if this error comes often.

Thanks a lot for your suggestions.

Regards

Srikanth

Former Member
0 Kudos

Did you get a chance to look at Markus' advice too ?

Thanks

former_member188883
Active Contributor
0 Kudos

Hi,

Please upgrade your kernel to latest and then check. It should resolve the problem.

Hope this is useful.

Regards,

Deepak Kori

nicholas_chang
Active Contributor
0 Kudos

Hi,

Is this new installation on 2008 R2? If yes (or No), try to update to the latest kernel (SAPEXE + SAPEXEDB), dw, libdbsl to the latest.

Cheers,

Nicholas Chang

Former Member
0 Kudos

First you try to check if this core file in work directory is huge in size. Make sure you don't get full file system situation due to it (/usr/sap Filesystem). Delete it if you have to.

Then see what is your current SAP release and current kernel patch level. If this kind of dump is regular then problem is most probably due to current kernel patch level. You should try to go for highest kernel patch available.

Also try to discuss with your functional/abap team if you can find out some other reason of this ABAP dump.

Thanks