DB2 FOR LUW / DB2FORLUW / A10 - DB2

DB2 SQL Query Optimizer has improved the performance of the join 
operation for foreign key constraint enforcement when all of the 
following conditions are satisfied: 
 
(1) It is a partitioned (DPF) environment 
(2) There exists tables P (parent) and C (child) where P is the 
      parent table of C in a foreign key constraint. 
 
      P and C could be the same table (i.e. self-referencing 
      foreign key constraint). 
 
(3) the SQL statement being compiled contains an INSERT/UPDATE 
     operation (e.g. INSERT statement, 
 
     UPDATE statement, INSERT or UPDATE operation in a MERGE 
     statement) on table C, which 
 
     requires a scan on table P to check for the existence of 
     parent key. 
 
(4) P is also updated in the SQL statement prior to the 
     INSERT/UPDATE operation mentioned in (3) above. 
 
 
Example: (assuming table P is a parent of table C in a foreign 
key constraint in DPF) 
 
  begin atomic 
 
      insert into P values (1,1);-- 
      update C set i2 = i2 + 1;-- 
  end;

**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF customers                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1 or later              * 
****************************************************************

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

The issue is first fixed in DB2 Version 10.1 Fix Pack 1

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.06.2012
08.11.2012
08.11.2012