cancel
Showing results for 
Search instead for 
Did you mean: 

Background Job Terminating with Signal 4 received by operating system

0 Kudos

Hi ,

There is a zee ABAP program which is working fine in foreground but the same was not working at BACKGROUND when I shedule the job with the same zee ABAP program. the job is terminating with "Job also cancelled due to process termination. See the system log" But the same was worked previous at background too, there are no changes to the program too.The problem was with only this zee ABAP program for remaining are all working fine.

St22:

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).

-

Last error logged in SAP kernel

Information on where termination occurred

The termination occurred in the ABAP/4 program "ZSDUZ980" in

"ADD_NO_ACTIVITY_RECORDS".

The main program was "ZSDUZ980".

The termination occurred in line 1174

of the source code of program "ZSDUZ980" (when calling the editor 11740).

The program "ZSDUZ980" was started as a background job.

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

Place................ "SAP-Server witco-10_NCQ_00 on host witco-10 (wp 1)"

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

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

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

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

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

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

Line................. 7209

The error reported by the operating system is:

Error number..... " "

Error text....... " "

System Environment

SAP Release.............. "31I"

Operating system......... "AIX"

Database type............ "ORACLE"

SAP kernel............... "31I"

SAP database version..... "31I"

Thanks

Sambi

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sambi,

Signal 4 is an ILL (illegal instruction) signal. On your platform (AIX with SAP 3.1I) there are a few notes you should look at:

- 115220 "Signal 11 and signal 4 on 32-bit AIX"

- 514798 "AIX - Memory leak - CLOSE DATASET"

Also check note 97497 (memory management for 3.1I) and particularly the AIX specifics.

The fact that your program works in dialog but fails in background might indicate that it is indeed a memory problem - dialog and batch processes use a different memory allocation scheme.

Good luck,

Mark

0 Kudos

Hi Mark,

Thanks for the reply,

Below are the memory details in our system, according to the Notes you send to me, They have set it as it is.

abap/heap_area_dia 188743680

abap/heap_area_nondia 400556032

abap/heap_area_total 838860800

abap/heaplimit 25165824

The same Zprogram was worked before in the BAckground, But from last week it stop working. But there are no chages happen to this zee ABAP program.

Thanks

Sambi

Answers (0)