Skip to Content
avatar image
Former Member

SPRO Document Splitting terminated by signal 11

Dear SAP Masters,

After upgrade the SAP kernel from 7.00 (254) to 7.00 (278). Then my FI functional colleague have a problem with customizing document splitting, he execute "Define Zero-Balance Clearing Account" after he want to input new account with "new entries" button, system pops up the error message "work process restarted; session terminated". Then I check st22 tcode the system display short dump :

Runtime Errors SYSTEM_CORE_DUMPED

Short text

Process terminated by signal 11.

What happened?

Error in the SAP kernel.

The current ABAP "SAPLGLT1" program had to be terminated because the ABAP processor detected an internal system error.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference.

Error analysis

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 sapdev_D06_00 on host sapdev (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:

Error number..... " "

Error text....... " "

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 program: The source code of the program. In the editor, choose "Utilities->More Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which actions and input led to the error.

Anyone can help my problem ???

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jan 18, 2011 at 01:42 AM

    Hi Dwipoutra,

    Did you get a solution for this problem. I am getting the same problem after upgarde.

    Thanks

    Jitendra Tayal

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi ,

      Have you checked available free physical memory as well as Swap Space ?

      Please take a look at note 1121904 for some details. When the system is running short of memory and also the paging space is getting full , u will get system_core_dumped Abap runtime error ... mean while kindly check dev_W0,W1 .....files also .

      let me know which OS you are using . if its Unix ,usr/sap/SID/ ../work .. delete the core file also ..

      Regards

  • avatar image
    Former Member
    Jan 18, 2011 at 10:49 AM

    Hi,

    Could you specify the dev_w* log file entries. When the FI functional consutlant is using the functionality in SPRO check in SM50 to see which work process he is using. Once he gets the dump , check the dev_w* log file and paste here.

    Regards,

    Jyotish

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      There is an issue with the dynpro screen creation. The system is not able to create the UI screen . Extract from the log file "WARNING => -> waited too long, going ahead [dyrdyp.c 795] A A Tue Jan 18 09:17:05 2011 A TH VERBOSE LEVEL FULL A ** RABAX: end RX_GET_MESSAGE". RABAX means dump. It may be due to memory issue. You can search for SAP notes on term: OS semaphore.

      Regards,

      Jyotish

  • avatar image
    Former Member
    Jan 18, 2011 at 11:38 AM

    Hi,

    we have a similiar problem after upgrading our kernel from 254 to 278.

    We are running on Sun Solaris, the program is SAPLBUC3, but the rest sounds nearly as described above.

    There are 4 development-systems here with this problem, a 5th, which we had left on an older kernel-release works fine.

    Has anyone got an idea?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 30, 2011 at 04:22 AM

    Thanks to all of you guys....the answer is memory problem

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Dwiputra,

      I know it is a old issue that you had.

      But I am a very similar problem. I have some problems with a simple EXPORT/IMPORT in a abap program. We just found the message in workprocess log: "*GENER* starting inline generation: ZMELAP085_CONTAS_PAGAS (reason: explicit generation)."

      You sad the answer for your problem was memory.

      But, what did you do for fix it?

      Please, help me.

      Thanks in advance,

      Rogerio