Dear all,
From logfiles the findings were:
In the work process log stack corrupted information this error are due to mainly kernel bugs. The recommendation was to apply the DW_416 kernel package as it consists of many fixes.
It should be noted that this problem only happens in my distributed system since the kernel was applied before in two centralized systems and the DUMP never appeared.
In this context I will apply again the DW_416 Kernel Package in order to fix the inconsistencies. I will let you know what happen next. Thanks for your suggestions.
ST22
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 19.02.2015 08:14:46
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short
text |
| Process terminated by signal
4. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What
happened? |
| Error in the SAP
kernel. |
| |
| The current ABAP "SAPLSKOM" program had to be terminated because
the |
| ABAP processor detected an internal system error.
Application server... "machine02"
Work process number.. 19
dev_w19
M Thu Feb 19 08:14:38 2015
M nobuf/trc_obj = ><
A EXCP> Attribute IS_RESUMABLE not found in class CX_ROOT.
M
M Thu Feb 19 08:14:46 2015
M si_code = 30
M Sending process ID = 0
M Real user ID of sending process = 0
M ILL_ILLOPC: Illegal opcode
-------------------------------------------
Signal 4 encountered.
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = 4294967296
=> Core limit = unlimited
=> File size limit = unlimited
=> Heap address = 0x116022f00
=> Stack address = 0xfffffffffff69c0
=> Stack low = 0xfffffffffff4110
=> Stack high = 0xffffffffffff730
-------------------------------------------
=> Stack Trace:
Unknown at 0xa000100001c98bc
!!! Invalid stack address encountered: 0x110d54d80
!!! Stack corrupted.
-------------------------------------------
=> CPU Registers:
msr = 0xa00000000000d032 iar = 0x0a000100001c98bc
ctr = 0x0000000000000000 lr = 0x0a000100001c98bc
xer = 0x0000000000000008 cr = 0x0000000022482848
r00 = 0x000000000000000a r01 = 0x0fffffffffff69c0
r02 = 0x09001000a2e4f898 r03 = 0x09001000a3064fe8
r04 = 0x09001000a3064fe8 r05 = 0x0000000000000066
r06 = 0x09001000a306504e r07 = 0x0000000000000000
r08 = 0xffd8ffd6fff5ffff r09 = 0x00270029000a0000
r10 = 0x0000000000000000 r11 = 0x0000000000000000
r12 = 0x0a000100001c98bc r13 = 0x0000000113caf3c0
r14 = 0x000000011020aac8 r15 = 0x000000011020aac8
r16 = 0x000000011020be10 r17 = 0x0000000000000001
r18 = 0x0000000110790668 r19 = 0x0000000000000003
r20 = 0x0000000000000000 r21 = 0x0000000102e9c5bc
r22 = 0x0000000110001dac r23 = 0x000000011020aa88
r24 = 0x0a000100001c98bc r25 = 0x0000000110000ebc
r26 = 0x00000001033b6760 r27 = 0x0000000000000000
r28 = 0x0a00010000437f30 r29 = 0x0000000110000ebc
r30 = 0x0a00010000438176 r31 = 0x0a00010000437ec0
-------------------------------------------
M ***LOG Q0E=> SigIGenAction, signal ( 4) [sigux.c 1801]
M in_ThErrHandle: 1
M DpVmcGetVmByTmAdm: no VM found for T19/M0/I1 (locked VMs ignored)
M ThResetEmMagic: reset em magic for T19/M0/I1
M ThSigHandler: signal (step 4, th_errno 11, action 4, signal no. 4)
*********************