home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT01916 Status: Closed

COLLATIONNAME IN SYSCAT.COLUMNS MIGHT BE CHANGED UNEXPECTEDLY TO NON_UNIQUE
IF LENGTH OF COLUMN IS ALTERED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 Fix Pack 5.                          * 
****************************************************************
Local Fix:
Not available.
Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

21.05.2014
23.07.2015
23.07.2015
Problem solved at the following versions (IBM BugInfos)


Problem solved according to the fixlist(s) of the following version(s)


10.1.0.5

FixList