|
Problem IT03522
|
Status: Closed |
Explicit and implicit rebind may result in deadlock on rebind sequence lock |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Upon implicit or explicit rebind, DB2 acquires the rebind
sequence lock. However, this lock may not get released after the
statement is completed under certain circumstances and may lead
to deadlock and concurrency issues with other statements
attempting to rebind the same package. This lock would require
the transaction to commit or rollback to get released.
To confirm you're hitting this APAR, check the lock dumps for
contention on the rebind sequence lock.
For example, an application snapshot that shows the symptom:
Application handle = 15486
Application status = Lock-wait
Package name = P1593222409
Package name = SYSSH200
<corresponding statement from the applications that will on lock
wait >
ID of agent holding lock = 1124
Lock name =
0x97B2EF1B0000000001000062D3
Lock object type = Internal Sequence
Lock
Lock mode = Exclusive Lock (X)
Lock mode requested = Exclusive Lock (X)
This behavior can be seen starting from DB2 V10.1 FP2. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 FOR LUW *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to fixpack V10.5FP5 *
**************************************************************** |
| Local Fix: |
Commit or rollback after each statement that may cause a package
to get rebound. |
| Solution |
Upgrade to fixpack V10.5FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.07.2014
19.03.2015
19.03.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
