DB2 FOR LUW / DB2FORLUW / A50 - DB2

The value of COLLATIONNAME in SYSCAT.COLUMNS might be changed 
unexpectedly to NON_UNIQUE if the length of column is altered. 
 
Here is an example: 
 
$ db2 "create table test (c1 varchar(256))" 
$ db2 "select substr(TABNAME,1,10) as TABNAME, 
substr(COLNAME,1,10) as COLNAME, substr(COLLATIONSCHEMA,1,15) as 
COLLATIONSCHEMA, substr(COLLATIONNAME,1,13) as COLLATIONNAME, 
substr(LENGTH,1,10) as LENGTH from SYSCAT.COLUMNS where 
TABNAME='TEST'" 
 
TABNAME    COLNAME    COLLATIONSCHEMA COLLATIONNAME LENGTH 
---------- ---------- --------------- ------------- ---------- 
TEST       C1         SYSIBM          IDENTITY      256 
 
  1 record(s) selected. 
 
$ db2 "alter table TEST alter column C1 set data type 
varchar(1024)" 
 
$ db2 "select substr(TABNAME,1,10) as TABNAME, 
substr(COLNAME,1,10) as COLNAME, substr(COLLATIONSCHEMA,1,15) as 
COLLATIONSCHEMA, substr(COLLATIONNAME,1,13) as COLLATIONNAME, 
substr(LENGTH,1,10) as LENGTH from SYSCAT.COLUMNS where 
TABNAME='TEST'" 
 
TABNAME    COLNAME    COLLATIONSCHEMA COLLATIONNAME LENGTH 
---------- ---------- --------------- ------------- ---------- 
TEST       C1         SYSIBM          NON_UNIQUE    1024 
 
  1 record(s) selected.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 Fix Pack 4                           * 
****************************************************************

Not available.

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
 

Problem was first fixed in DB2 UDB Version 10.5 Fix Pack 4

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

21.05.2014
15.09.2014
15.09.2014