home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT07450 Status: Closed

Explicit and implicit rebind may result in deadlock on rebind sequence lock

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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:                                              * 
* A10                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Commit or rollback after each statement that may cause a     * 
* package                                                      * 
* to get rebound.                                              * 
****************************************************************
Local Fix:
Commit or rollback after each statement that may cause a package 
to get rebound.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.03.2015
15.07.2015
15.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList