IBM Support

IT29468: DB2LOGGP CAN TRAP WITH SIGNAL #11 IN A FEDERATED ENVIRONMENT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • DB2 instance trapped in sqleuApplicationInit
    
    The following db2diag.log probe can occur for db2loggp:
    
    2019-06-13-09.06.44.247708+120 I537852E449           LEVEL:
    Warning
    PID     : 10217                TID : 47051769374464  PROC :
    db2sysc 0
    INSTANCE: db2inst              NODE : 000            DB   : TEST
    HOSTNAME: test
    EDUID   : 38                   EDUNAME: db2loggp (TEST) 0
    FUNCTION: DB2 UDB, RAS/PD component,
    pdEDUIsInDB2KernelOperation, probe:600
    DATA #1 : String, 28 bytes
    _Z23sqlpForceConflictingApp
    DATA #2 : String, 4 bytes
    sqlp
    
    ...
    
    2019-06-13-09.06.50.279399+120 E550835E1478          LEVEL:
    Severe
    PID     : 10217                TID : 47051769374464  PROC :
    db2sysc 0
    INSTANCE: db2inst              NODE : 000            DB   : TEST
    HOSTNAME: test
    EDUID   : 38                   EDUNAME: db2loggp (TEST) 0
    FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
    probe:90
    MESSAGE : ADM14011C  A critical failure has caused the following
    type of error:
              "Trap". The database manager cannot recover from the
    failure. First
              Occurrence Data Capture (FODC) was invoked in the
    following mode:
              "Automatic". FODC diagnostic information is located in
    the following
              directory:
    "/db2/db2dump/FODC_Trap_2019-06-13-09.06.44.030401_0000/".
    DATA #1 : Signal Number Recieved, 4 bytes
    11
    DATA #2 : Siginfo, 128 bytes
    ...
    
    
    And the following stack can occur:
    
    <Trap>
    <Header>
    DB2 build information: DB2 v11.1.3.3 s1807091300 SQL11013
    timestamp: 2019-06-13-09.06.44.040532
    instance name: db2inst.000
    EDU name     : db2loggp (TEST) 0
    EDU ID       : 38
    Signal #11
    uname: S:Linux R:3.10.0-862.9.1.el7.x86_64 V:#1 SMP Wed Jun 27
    04:30:39 EDT 2018 M:x86_64 N:test
    process id: 10217
    parent process id: 10215
    thread id : 47051769374464 (0x2ACB17FFE700)
    kthread id : 10419
    </Header>
    ...
    
    </Registers>
    <POFDisassembly>
     sqleuApplicationInit + 0x00e3
    (/db2/db2inst/sqllib/lib64/libdb2.so.1)
    
            0x00002ACDD4E3C2A3 : 4C8B3A4D85FF7424
    </POFDisassembly>
    <StackTrace>
    -----FUNC-ADDR---- ------FUNCTION + OFFSET------
    0x00002ACAD9E4E4A6
    _Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm +
    0x0356
                    (/db2/db2inst/sqllib/lib64/libdb2osse.so.1)
    0x00002ACAD9E4E0EB ossDumpStackTraceV98 + 0x002b
                    (/db2/db2inst/sqllib/lib64/libdb2osse.so.1)
    0x00002ACAD9E4A297 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
    0x00d7
                    (/db2/db2inst/sqllib/lib64/libdb2osse.so.1)
    0x00002ACAD234A967 sqlo_trce + 0x03c7
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD24B4851 sqloEDUCodeTrapHandler + 0x03b1
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACACAC52680 address: 0x00002ACACAC52680 ; dladdress:
    0x00002ACACAC43000 ; offset in lib: 0x000000000000F680 ;
                    (/lib64/libpthread.so.0)
    0x00002ACDD4E3C2A3 sqleuApplicationInit + 0x00e3
                    (/db2/db2inst/sqllib/lib64/libdb2.so.1)
    0x00002ACDD46AAD21 SQLCancel + 0x0091
                    (/db2/db2inst/sqllib/lib64/libdb2.so.1)
    0x00002ACD74F6BD21 _ZN14DRDA_Statement19interrupt_executionEv +
    0x0031
                    (/db2/db2inst/sqllib/lib64/libdb2drdaF.so)
    0x00002ACAD069CC82 _ZN8sqeAgent21InterruptFedStatementEv +
    0x0022
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD0762B0E
    _ZN14sqeAppServices17ForceApplicationsEP14sqeApplicationiP12SQLZ
    _APP_HDLiiii + 0x030e
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD062B6F9
    _Z15sqleForceAgentsiiP12SQLZ_APP_HDLP5sqlcaiii + 0x0159
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD28DFAF1
    _Z23sqlpForceConflictingAppP12SQLZ_APP_HDLmjP14SQLP_LOCK_INFO +
    0x0391
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD282957B
    _Z27sqlpScanTranTableForLowTranP14sqlpMasterDbcbP9SQLP_LSN8PP11S
    QLP_TENTRY + 0x05ab
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD282A613
    _ZN11sqpLoggpEdu33sqlpLoggpScanToUpdateRecoveryLsnsEv + 0x01d3
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD286F90D _ZN11sqpLoggpEdu6RunEDUEv + 0x028d
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD3F5026E _ZN9sqzEDUObj9EDUDriverEv + 0x01be
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACAD24B1798 sqloEDUEntry + 0x0578
                    (/db2/db2inst/sqllib/lib64/libdb2e.so.1)
    0x00002ACACAC4ADD5 address: 0x00002ACACAC4ADD5 ; dladdress:
    0x00002ACACAC43000 ; offset in lib: 0x0000000000007DD5 ;
                    (/lib64/libpthread.so.0)
    0x00002ACADAF59B3D clone + 0x006d
                    (/lib64/libc.so.6)
    </StackTrace>
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 for LUW users                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 Db2 11.1 M4FP5 or later.                      *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 V11.1 M4FP5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29468

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-17

  • Closed date

    2019-10-31

  • Last modified date

    2019-10-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IT30790

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 October 2019