IBM Support

IT16158: DB2 PURESCALE HANG DUE TO MISSING LOCK NOTIFICATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem description
    When multiple members are requesting the same lock in a
    pureScale cluster and the lock notification to reclaim is lost
    then an application hang may occur and possibly an entire
    database hang depending on the current locks held by the
    application in a hang state.
    
    A missing lock notification can be triggered during cable pull
    when an adapter goes down,
    or a lock notification timeout where the following error is
    logged:
    
    2018-01-02-10.51.15.616046+060 I177825120E664        LEVEL:
    Severe
    PID     : 2931                 TID : 140189880018688 PROC :
    db2sysc 0
    INSTANCE: inst1             NODE : 000            DB   : TESTDB
    HOSTNAME: hostname
    EDUID   : 1240                 EDUNAME: db2LLMn12 (P2001) 0
    FUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876
    DATA #1 : <preformatted>
    do_dequeue: Timed-out waiting for completion of RDMA write of an
    link status buffer.  EP: 0x7f7ed01912d0
    DATA #1 : <preformatted>
    If a CF return code is displayed above and you wish to get
    more information then please run the following command:
    
    System setup
    A multiple member pureScale cluster setup is required to
    encounter this defect.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 10.5 Fix Pack 9 or higher                     *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 10.5 Fix Pack 9
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT16158

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-15

  • Closed date

    2017-09-18

  • Last modified date

    2019-01-03

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

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

    IT22434

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

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

Document Information

Modified date:
29 June 2020