DB2 FOR LUW / DB2FORLUW / 970 - DB2

DB2 will require a lock on a seemingly unrelated table when 
performing a select. This can cause unexpected lock timeouts 
when a reorg is active. 
 
The following scenario demonstrates the problem. 
 
Consider 3 tables, A, B and C 
Table A has a foreign key on table B. 
 
A reorg of table A is started. 
A select similar to the following is executed : 
 
select 
... 
from B left outer join 
        C on 
... 
 
In order to compile this query, DB2 will also evaluate 
constraints that may exist on the tables. 
As there is a foreign key constraint from A to B, table A will 
be locked but the lock mode is incompatible with the current 
lock due to the reorg. 
 
The fix for this APAR will relax the locking required so that 
table A will no longer need to be locked during query 
compilation

**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpack 10 or Later.                 * 
****************************************************************

First Fixed in DB2 LUW v9.7 Fixpack 10.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

06.05.2014
29.12.2014
29.12.2014

9.7.FP10