|
Problem IT33186
|
Status: Closed |
LOCK-WAIT ON DECOUPLED DB2ADCBLD
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Lock wait on a decoupled db2adcbld application where the
db2adcbld application no longer exists on it's coordinating
member.
An application such as below is shown to be in a "Lock-Wait"
state:
Application :
AppHandl [nod-index] : 29969 [000-29969]
TranHdl : 209
(snip)
Coordinator EDU ID : 0
Application Status : Lock-wait
Further diagnostics will indicate TranHdl=209 belonging to
Application handle 29969 waiting for lock held by TranHdl 362.
Tranhdl belongs to application handle 790005 (db2adcbld) which
has been decoupled.
State Status Mode Dur CMode lrbFlag TrnHdl HldCnt
----- ------ ---- --- ----- -------- ------ ------
L G ..X 255 NON 00000000 362 0
L W ..X 0 NON 00000000 209 0
Application :
AppHandl [nod-index] : 790005 [012-03573]
TranHdl : 362
(snip)
Coordinator EDU ID : 0
Application Status : Decoupled
Application Name : db2adcbld
Checking in the coordinator node (12 in this example) using
db2pd -apinfo,
this db2adcbld application (with handle 12-3573) cannot be
found (i.e. coord does not exist). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.5.0 or higher *
**************************************************************** |
| Local Fix: |
NONE (restart DB2 instance) |
| Solution |
|
| Workaround |
See LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.06.2020
20.11.2020
20.11.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
