cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Kernel 721 ext PL 412 KNOWN ISSUES

former_member235282
Participant
0 Kudos

Dear experts,

Does anyone knows about known issues with SAP Kernel 721 ext PL 412?

I have applied to my CRM system and I having some dumps (SYSTEM_CORE_DUMPED), I don't know if  this kernel has any bug or if the problem is because  the system has other problem (I left the logs for further analysis).

I have been looking for Known Issues with this kernel (It is the last one) and I don’t find any relevant information regarding to this dumps, the only note I have found is 1728283 - SAP Kernel 721: General Information and in the last part the known issues make reference to other issues.


Please refer to note 2084437 for other known issues with SAP kernel 721 PL 401.


I appreciate any comments that help me to troubleshoot the issue.




Accepted Solutions (1)

Accepted Solutions (1)

former_member235282
Participant
0 Kudos

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)

*********************

alwina_enns
Employee
Employee
0 Kudos

Hello Daniel,

probably you will need to update also the dbsl library. It would be helpful if you could extract the call stack from the core file on the OS level and check, if you see calls to dbsl library in the call stack.

Regards,
Alwina

former_member235282
Participant
0 Kudos

Dear all,

Thanks for all your comments.

I let you know that after applying the package level 416 the SYSTEM_CORE_DUMPED  has disappeared.  It could have been a bug for the PL 412 in distributed system. 

Best regards,

DanielO

Answers (3)

Answers (3)

alwina_enns
Employee
Employee
0 Kudos

Hello Daniel,

the call stack in the traces is corrupt, could you please try to extract the call stack as described in the note

625271 - AIX call stack denoted as corrupted in trace files


Regards,
Alwina

manumohandas82
Active Contributor
0 Kudos

Hi Daniel ,

Check whether you have the recommended C/C++ Runtime

1780629 - AIX: Minimal OS Requirements for SAP Kernel


Thanks ,

Manu

Former Member
0 Kudos

Not sure that this issue is related to any kernel bug. At first the cause of CX_SY_DYN_TABLE_ILL_COMP_VAL exception is "a column of the table otab contains a prohibited value". According to explanation: "If a column of otab, has invalid content (NAME contains the name of a component that does not exist or an incorrect offset/length specification, DESCENDING and ASTEXT do not contain "X" or the initial value), this leads to a treatable exception of the class CX_SY_DYN_TABLE_ILL_COMP_VAL". In your case otab is lt_sortbytab. An exception has occurred in program ZRVEUR101_CALC_SEGMENTO. Try to debug (with help of the program owner) to investigate the root cause of this error.

In addition can you attach output of errpt command at time when system dump has been occurred?

ACE-SAP
Active Contributor
0 Kudos

Hi Daniel,

You should not be using that kernel sub-version without specific reason (Oss note or SAP support recommendation).

Only apply main SP Stack kernel patch (that is SP 401 for 721 EX6 Aix => SAPEXE_401-10011318.SAR)

Check on swdc, the 412 kernel has gone & is repalced by 415 (dw_415-10011318.sar)

Check page 8 of this document => Deployment Strategies for the Kernel of the SAP Application Server ABAP

The trace file is note the one of the process that did undergo the dump.

87 WP, it's starting to be a big instance...

If not already done, check instance profile & memory def. (1137734 - Assignment of memory areas, shared memories, and pools)

sappfpar check pf=/sapmnt/DIM/profile/DIM_DVEBMGS00_machine02

Regards