DB2 FOR LUW / DB2FORLUW / A10 - DB2

A MERGE statement may result in SQL901N ("COLUMN NUMBER OUT OF 
RANGE") when the following conditions are satisfied: 
 
(1) The MERGE statement is on a target table (T1) and there are 
DELETE (or INSERT) as well as UPDATE operations in the MERGE 
statements. 
 
(2) a foreign key constraint (with ENABLE QUERY OPTIMIZATION) 
exists between T1 (as the parent) and T2 (as the child). 
 
(3) The merge target table (T1) has a dependent immediate MQT or 
a 
deferred MQT with staging table, and the MQT definition involves 
a join between T1 and T2 where the join predicates involve the 
corresponding parent key and foreign key columns.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4 or above.             * 
****************************************************************

A potential workaround is to DISABLE QUERY OPTIMIZATION for 
those foreign key constraints where the parent and child tables 
are referenced in the join of the MQTs being maintained.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem has been fixed in DB2 Version 10.1 Fix Pack 4 and above.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC99404 
follow-up : 

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

27.09.2013
02.06.2014
02.06.2014