Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT01916 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 Fix Pack 5.                          * 
****************************************************************
Local-Fix:
Not available.
Lösung
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.05.2014
23.07.2015
23.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList