DB2 - Problem description
Problem IT16158 | Status: Closed |
DB2 PURESCALE HANG DUE TO MISSING LOCK NOTIFICATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem 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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 9 or higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Db2 10.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.07.2016 18.09.2017 03.01.2019 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) | |
11.1.1.1 |