DB2 - Problembeschreibung
Problem IT06539 | Status: Geschlossen |
UNEXPECTED SQL0433N DURING SINGLE ROW UPDATE OF COLUMN-ORGANIZED TABLE WITH A CHAR[1] COLUMN IN DB2 V105 FIXPACK 5 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In db2_v105 fixpack 5, an unexpected SQL0433N may occur when updating a column-organized table. The following conditions must occur: - the table must have a CHAR[1] column that is not being updated by the statement and is not part of a unique key - the update is directed to one row by specifying in a WHERE clause the values for the unique key | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fixpack7 or higher * **************************************************************** | |
Local-Fix: | |
Modify the update statement to explicitly update any char[1] columns to be equal to the current value. e.g. for a table tab1 with columns: (i1 int, i2 int not null unique, c1 char(1): the update that incorrectly fails with a SQL0433 might be: update tab1 set i1 = ? where i2 = ? then changing this to update tab1 set i1 = ?, c1=c1 where i2=? | |
Lösung | |
First fixed in DB2 Version 10.5 Fixpack7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.01.2015 27.01.2016 27.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |