home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC80111 Status: Geschlossen

THE CODE PAGE STORED IN SYSCAT.COLUMNS FOR A GRAPHIC TYPED COLUM N GETS
RESET TO 0 AFTER RUNNING THE ALTER COLUMN ... COMMAND

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
After altering the GRAPHIC typed column with ALTER TABLE 
command, the code page stored in the system catalog gets reset 
to 0. Example below illustrates the problem. 
 
select codepage from syscat.columns where tabname = 'TEST' and 
typename = 'GRAPHIC' 
 
CODEPAGE 
-------- 
    1200 
 
  1 record(s) selected. 
 
 
alter table test alter column id set with default null 
DB20000I  The SQL command completed successfully. 
 
select codepage from syscat.columns where tabname = 'TEST' and 
typename = 'GRAPHIC' 
 
CODEPAGE 
-------- 
       0 
 
  1 record(s) selected.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All the users of DB2 v9.7 FP5 and earlier.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After altering the GRAPHIC column with ALTER TABLE command,  * 
* you have noticed that the code page got reset. Example below * 
* illustrates the problem.                                     * 
*                                                              * 
* Before alter column:                                         * 
*                                                              * 
* db2 "select CODEPAGE, DBCSCODEPG, COMPOSITE_CODEPAGE from    * 
* sysibm.syscolumns where tbname = 'TEST'"                     * 
*                                                              * 
* CODEPAGE DBCSCODEPG COMPOSITE_CODEPAGE                       * 
* -------- ---------- ------------------                       * 
*       0      1200              1200                          * 
*                                                              * 
*   1 record(s) selected.                                      * 
*                                                              * 
* After alter column:                                          * 
*                                                              * 
* db2 "select CODEPAGE, DBCSCODEPG, COMPOSITE_CODEPAGE from    * 
* sysibm.syscolumns where tbname = 'TEST'"                     * 
*                                                              * 
* CODEPAGE DBCSCODEPG COMPOSITE_CODEPAGE                       * 
* -------- ---------- ------------------                       * 
*       0      1200              0                             * 
*                                                              * 
*   1 record(s) selected.                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP6                                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The problem was first fixed in DB2 v9.7 FP6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84193 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.12.2011
11.06.2012
11.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList