DB2 FOR LUW / DB2FORLUW / A50 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fixpack7 or higher               * 
****************************************************************

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=?

First fixed in DB2 Version 10.5 Fixpack7

not known / see Local fix

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

16.01.2015
27.01.2016
27.01.2016