DB2 - Problembeschreibung
Problem IC99404 | Status: Geschlossen |
MERGE STATEMENT RETURNS SQL0901N ("COLUMN NUMBER OUT OF RANGE") | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
Problem has been fixed in DB2 Version 10.5 Fix Pack 4 and above. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.02.2014 08.09.2014 08.09.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |