DB2 FOR LUW / DB2FORLUW / B10 - DB2

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 : 
do_dequeue: Timed-out waiting for completion of RDMA write of an
link status buffer.  EP: 0x7f7ed01912d0
DATA #1 : 
If a CF return code is displayed above and you wish to get
more information then please run the following command:

DB2 detects and resends all the missing lock notifications and
refreshes all the remaining lock reclaims.

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

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.01.2019
18.01.2019
18.01.2019