SYSTEM_CORE_DUMPED "ab_CoreInfo" Process terminated by signal 11

[wagener-mark]

Short text

    Process terminated by signal 11.

What happened?

    Error in the SAP kernel.

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

    ABAP processor detected an internal system error.

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............ "NI (network interface)"

    Place................ "SAP-Dispatche****** on host ****"

    Version.............. 40

    Error code........... "-6"

    Error text........... "connection to partner '127.0.0.1:0' broken"

    Description.......... "NiIRead: 127.0.0.1:0"

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

    Module............... "nixxi.cpp"

    Line................. 4849

    The error reported by the operating system is:

    Error number..... " "

    Error text....... " "

System environment

    SAP-Release " "

    Application server... "*****"

    Network address...... "*****"

    Operating system..... "Linux"

    Release.............. "3.0.101-0.46-default"

    Hardware type........ "x86_64"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.. 31

    Shortdump setting.... "full"

    Database server... "******"

    Database type..... "DB6"

    Database name..... "PEC"

    Database user ID.. "SAPSR3"

    Terminal.......... "*****"

    Char.set.... "C"

    SAP kernel....... 721

    created (date)... "Dec 4 2013 12:39:33"

    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr131018"

    Database version. "DB6_81 "

    Patch level. 201

    Patch text.. " "

    Database............. "DB6 09.07.*, DB6 09.08.*, DB6 10.*"

    SAP database version. 721

    Operating system..... "Linux 2.6, Linux 3"

    Memory consumption

    Roll.... 0

    EM...... 20949000

    Heap.... 0

    Page.... 1163264

    MM Used. 4755120

    MM Free. 3621632

Information on where terminated

    Termination occurred in the ABAP program "SAPLSVSM" - in

     "VRM_QUEUE_FLUSH_SIGNATURE".

    The main program was "SAPMV45A ".

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

    of the (Include) program "LSVSMU07".

Error occurred during batch input processing

Active Calls in SAP Kernel

Lines of C Stack in Kernel (Structure Differs on Each Platform)

(LinStack+0x33)[0x5ec752]

(CTrcStack2+0x48)[0x5ece5c]

(_ZL16rabax_CStackSavev+0xc6)[0x76c81f]

(ab_rabax+0x27ea)[0x772c58]

(ab_CoreInfo+0xc6)[0x775860]

(ThrCoreInfo+0x9)[0x5a75a6]

(ThIErrHandle+0xf3f)[0x4a05b9]

(ThSigHandler+0xdb)[0x4dc16a]

(SigIGenAction+0x2da)[0x1422b8a]

/lib64/libpthread.so.0[0x7f0b8e636850]

(_ZL20ScanBaseRefsCallbackP8BaseAttaP10AB_DATASEGjjtjPKv+0x3c)[0x18d61dc]

(_Z11ab_ScanBasePFvP8BaseAttaP10AB_DATASEGjjtjPKvES4_+0xc8)[0x1776928]

(_ZL19gcInitializeRootSet8GC_MODUSP19SzkAlgTraverseGraph+0xcd)[0x18d8cbd]

(ab_ObjMgrPerformGCStep__+0x3a3)[0x18c0e43]

(_Z8ab_jloopv+0x663)[0x19569f3]

(_Z8ab_extriv+0x59e)[0x1758a9e]

(_Z9ab_xeventPKDs+0x23)[0x179b873]

(ab_dstep+0xfa)[0x17b945a]

(dynpctlcal+0x29a)[0x1642cba]

(dynpout0+0xe8)[0x166eac8]

(dynprctl+0x135)[0x1643ef5]

(dynpen00+0x7a8)[0x1638128]

(ThSoftCancel+0xbeb)[0x505e50]

(ThCleanPrevUser+0x529)[0x4a3311]

(ThCheckPrevUser+0x1d7)[0x4a39cc]

(TskhLoop+0x4df3)[0x15b5f13]

(ThStart+0x25e)[0x4aaa29]

(DpMain+0x395)[0x1566945]

/lib64/libc.so.6(__libc_start_main+0xe6)[0x7f0b8e2ccc36]

Internal notes

    The termination was triggered in function "ab_CoreInfo"

    of the SAP kernel, in line 8945 of the module

     "//bas/721_REL/src/krn/runt/abrabax.c#9".

    The internal operation just processed is "CALY".

    Internal mode was started at 20150331132215.

    Stack trace of 'core'.

[hugo_amo · Accepted solution]

Hi Mark,

This is not the correct forum for this problem as this is for DB2 on LUW issues. In any case, I would strongly recommend you to implement latest 721 kernel.

Regards,

Hugo

[wagener-mark · Accepted solution]

Hi Hugo,

thx for your answer. I chose this forum, cause we have a second system core dump. Here some extracts from the WP-trace file.

[...]

M                     C-STACK

(LinStack+0x33)[0x5ec752]

(CTrcStack2+0x48)[0x5ece5c]

(SigIGenAction+0x205)[0x1422ab5]

/lib64/libpthread.so.0[0x7f0b8e636850]

(_ZL20ScanBaseRefsCallbackP8BaseAttaP10AB_DATASEGjjtjPKv+0x3c)[0x18d61dc]

(_Z11ab_ScanBasePFvP8BaseAttaP10AB_DATASEGjjtjPKvES4_+0xc8)[0x1776928]

(_ZL19gcInitializeRootSet8GC_MODUSP19SzkAlgTraverseGraph+0xcd)[0x18d8cbd]

(ab_ObjMgrPerformGCStep__+0x3a3)[0x18c0e43]

(_Z8ab_jloopv+0x663)[0x19569f3]

(_Z8ab_extriv+0x59e)[0x1758a9e]

(_Z9ab_xeventPKDs+0x23)[0x179b873]

(ab_dstep+0xfa)[0x17b945a]

(dynpctlcal+0x29a)[0x1642cba]

(dynpout0+0xe8)[0x166eac8]

(dynprctl+0x135)[0x1643ef5]

(dynpen00+0x7a8)[0x1638128]

(ThSoftCancel+0xbeb)[0x505e50]

(ThCleanPrevUser+0x529)[0x4a3311]

(ThCheckPrevUser+0x1d7)[0x4a39cc]

(TskhLoop+0x4df3)[0x15b5f13]

(ThStart+0x25e)[0x4aaa29]

(DpMain+0x395)[0x1566945]

/lib64/libc.so.6(__libc_start_main+0xe6)[0x7f0b8e2ccc36]

M

M Thu Mar 19 13:02:50 2015

M  ***LOG Q0E=> SigIGenAction, signal ( 11) [sigux.c      1801]

[...]

M Thu Mar 19 13:03:09 2015

M  kernel runs with dp version 138000(ext=120000) (@(#) DPLIB-INT-VERSION-138000-UC)

M  length of sys_adm_ext is 592 bytes

M  ThStart: taskhandler started

M  ThTHPInit: thp initialized

M  ThStart: prv_action of W10 = 0x8

M  ThInit: initializing DIA work process W10

M  ThInit: found previous user T176/M0/U30644

M  ***LOG Q01=> ThInit, WPStart (Workp. 10 2 17815) [thxxhead.c   1346]

M  ThInit: running on host jug1141

M  calling db_connect ...

B  Loading DB library '/usr/sap/PEC/D01/exe/dbdb6slib.so' ...

B  Library '/usr/sap/PEC/D01/exe/dbdb6slib.so' loaded

B  Version of '/usr/sap/PEC/D01/exe/dbdb6slib.so' is "721.02", patchlevel (0.137)

C  DbSl trace SM50: switch request to level 1

C  Registering callback for dynamic profile parameters

C  RLIMIT_STACK: current=8388608, max=-1

C

C  DB6 (DB2 UDB) UNICODE database interface 721.02 [opt]

C

C  DB6 shared library (dbdb6slib) patchlevels

C    (0.6) DB6: isolation RS for select in INDX type cluster tables (note 1678935)

C    (0.11) DB6: Global Compression Option (note 1690077)

C    (0.18) DB6: suppress location for internal SQL statements (note 1736676)

C    (0.21) DB6: reload connect passwords for table materialization (note 1746047)

C    (0.22) DB6: DBSL trace enhancements (note 31707)

C    (0.24) DB6: patch for DB6_DBSL_CLP_COMMAND (note 1755738)

C    (0.27) DB6: enhanced micro outage feature (note 1434153)

C    (0.32) DB6: patch collection 11/12 (note 1780383)

C    (0.39) DB6: patch collection 12/12 (note 1801754)

C    (0.44) DB6: Optimizer Profiles (note 1818503)

C    (0.112) DB6: Fetching NUMC NULL values into shorter output area (note 1835350)

C    (0.119) DB6: patch collection 05/13 (note 1859667)

C    (0.123) DB6: SYSTEM_CORE_DUMPED in dsql_db6_fetch (note 1870680)

C    (0.126) DB6: trace flush of cumulative trace at deactivation time (note 1880502)

C    (0.127) DB6: reconnect refused in batch work process (note 1884759)

C    (0.131) DB6: messages related to SQL_ATTR_DB2TRC_STARTUP_SIZE (note 1836451)

C    (0.137) DB6: DROP INDEX to DROP CONSTRAINT (note 1911087)

[...]

Is I saw the hint to DB6, I thought it might be a DB issue...

[hugo_amo · Accepted solution]

Hi Mark,

The dbsl is included in the kernel patches, I'd go for a kernel update to try to solve this issue.

Regards,

Hugo

[former_member182657]

Hi Mark,

You surely need to apply latest patch for the existing kernel to overcome the issue as already suggested by Hugo.

Good luck !!