IBM Support

IT37537: ON DB2/AIX, POST FROM THREAD_POST CAN BE SKIPPED/DEFERRED BY WAITER INTERRUPTED IN THREAD_WAIT , LEADING TO PANIC/SHUTDOWN

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

  • A timing hole in db2's synchronization implementation on AIX can
    lead to an abnormal shutdown when a waiter is interrupted by a
    force/signal.
    
    A variety of symptoms could occur, but one common symptom is an
    ESRCH error resulting in a panic.
    Eample db2diag.log entry :
    EDUID   : 5399                 EDUNAME: db2pfchr (TEST1) 0
    FUNCTION: DB2 UDB, SQO Latch Tracing,
    SQLO_SLATCH_CAS64::releaseConflict, probe:340
    CALLED  : OS, -, unspecified_system_function
    OSERR   : ESRCH (3) "No such process"
    DATA #1 : String, 13 bytes
    post error!:
    DATA #2 : File name, 16 bytes
    sqloLatchCAS64.C
    DATA #3 : Source file line number, 8 bytes
    1089
    DATA #4 : Codepath, 8 bytes
    2:6:8:20:22:26
    DATA #5 : String, 126 bytes
    0x0000000004010000: {
       held X: 1
       reserved for X: 0
       shared holders: 0
       firstSharIndex: 0x40
       firstExclIndex: 0x0
    
    example stack
    sqle_panic__Fi
    dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T
    3T7
    releaseConflict__17SQLO_SLATCH_CAS64Fv
    sqlbReadAndReleaseBuffers__FP16SQLB_OBJECT_DESCUiUlN23P11SQLB_pf
    Misc
    
    demangled:
    sqle_panic
    SQLO_SLATCH_CAS64::dumpDiagInfoAndPanic
    SQLO_SLATCH_CAS64::releaseConflict
    sqlbReadAndReleaseBuffers
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * On AIX                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.5.6 or higher                              *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.5.6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT37537

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-07-07

  • Closed date

    2021-07-21

  • Last modified date

    2021-07-21

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

    IT35426

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5"}]

Document Information

Modified date:
22 July 2021