|
Problem IC99404
|
Status: Closed |
MERGE STATEMENT RETURNS SQL0901N ("COLUMN NUMBER OUT OF RANGE") |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 4 or above. *
**************************************************************** |
| Local Fix: |
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. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem has been fixed in DB2 Version 10.5 Fix Pack 4 and above. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.02.2014
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
