IBM Support

IT24955: DB2 CRASH IN DPF + SMP AFTER INTERNAL INTERRUPT (SQL0952N)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IN DPF+SMP environment traps Could happen with the following
    stacks:
    
    sqloCrashOnCriticalMemoryValidationFailure
    diagnoseMemoryCorruptionAndCrash
    sqloDiagnoseFreeBlockFailure
    sqlofmblk
    sqlristm
    sqlra_sqlW_mem_free_sibling_list
    
    db2diag.log Could have the following :
    
    
    FUNCTION: DB2 UDB, base sys utilities,
    sqeAgentServices::RequestAgentForAppl, probe:1808
    MESSAGE : Appl failed to start up on this node. Interrupt rqst =
    DATA #1 : Hexdump, 4 bytes
    0x0A0000004DFFD204 : 0000 0000
    ....
    
    FUNCTION: DB2 UDB, buffer dist serv, sqlkdDispatchRequest,
    probe:205
    RETCODE : ZRC=0xFFFFFC48=-952
              SQL0952N  Processing was cancelled due to an
    interrupt.
    
    ...
    FUNCTION: DB2 UDB, SQO Memory Management,
    sqloDiagnoseFreeBlockFailure, probe:10
    MESSAGE : Possible memory corruption detected.
    DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes
    0x820F0002
    DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8
    bytes
    0x0a0001000859f1b0
    DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
    0x0A0001000859F198 : 0000 FF0C 0000 0000 0A00 0100 0859 F9E8
    .............Y..
    0x0A0001000859F1A8 : 0A00 0100 0859 EE80
    .....Y..
    code: 0xff0c
    curSize: 0
    SMemBlkFileId: 167772416
    SMemBlkLOC: 2137
    SMemBlkNum: 63976
    CodedCSG: a0001000859ee80
    DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
    0x0A0001000859F1B0 : 5441 4F42 0000 0000 0001 F348 0000 0000
    TAOB.......H....
    0x0A0001000859F1C0 : 0000 0000 0000 0000 0000 0000 FF00 0001
    ................
    0x0A0001000859F1D0 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
      [0] 0x090000000C685BB4
    @88@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0xF8
      [1] 0x090000000E3ACC74 sqlofmblkEx + 0xC
      [2] 0x090000000E323404 sqlridrp__FP8sqlrr_cbP9sqlri_tao +
    0x1B0
      [3] 0x090000000E305EEC sqlridrp__FP8sqlrr_cbP9sqlri_tao + 0x80
      [4] 0x090000000E305C90
    sqlridrp__FP8sqlrr_cbP9sqlri_tao@glue2D4 + 0x3C
      [5] 0x090000000EB9CEB4 sqlricls_complex__FP8sqlrr_cbilN23 +
    0xE24
      [6] 0x090000000F8D85C8
    sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x1B34
      [7] 0x090000000F8D7E30
    sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x139C
      [8] 0x090000000CB95DAC
    @82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x1850
      [9] 0x090000000F4F358C RunEDU__8sqeAgentFv + 0x35A4C
      [10] 0x090000000F473738 RunEDU__8sqeAgentFv + 0x124
      [11] 0x090000000E288AE4 EDUDriver__9sqzEDUObjFv + 0x130
      [12] 0x090000000DF1A2D4 sqloEDUEntry + 0x3A0
      [13] 0x09000000011C8E10 _pthread_body + 0xF0
      [14] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
    
    .....
    FUNCTION: DB2 UDB, SQO Memory Management,
    sqloDiagnoseFreeBlockFailure, probe:10
    MESSAGE : ADM14001C  An unexpected and critical error has
    occurred: "Panic".
              The instance may have been shutdown as a result.
    "Automatic" FODC
              (First Occurrence Data Capture) has been invoked and
    diagnostic
              information has been recorded in directory
    
    ....
    

Local fix

  • Turn of SMP if possible.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT24955

  • 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

    2018-05-04

  • Closed date

    2018-11-27

  • Last modified date

    2018-11-27

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

    IT24299

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"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:
27 November 2018