DB2 - Problem description
Problem IT00790 | Status: Closed |
COLLATIONNAME IN SYSCAT.COLUMNS MIGHT BE CHANGED UNEXPECTEDLY TO NON_UNIQUE IF LENGTH OF COLUMN IS ALTERED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 Fix Pack 10 * **************************************************************** | |
Local Fix: | |
Not available. | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 10 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.04.2014 01.12.2014 01.12.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |