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 IC65896 Status: Geschlossen

DURING UPGRADE CATALOG TABLES' COLLATION MAY NOT BE SET TO
IDENTITY FOR UNICODE DATABASE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When a database is upgraded from any supported down level to 
Version 9.7, the table collation is not set to IDENTITY for the 
following catalog tables. 
 
- SYSIBM  .SYSBUFFERPOOLNODES 
- SYSIBM  .SYSCOLCHECKS 
- SYSIBM  .SYSCOLDIST 
- SYSIBM  .SYSCOLGROUPDIST 
- SYSIBM  .SYSCOLGROUPDISTCOUNTS 
- SYSIBM  .SYSCOLGROUPS 
- SYSIBM  .SYSCOLUSE 
- SYSIBM  .SYSCONSTDEP 
- SYSIBM  .SYSHIERARCHIES 
- SYSIBM  .SYSKEYCOLUSE 
- SYSIBM  .SYSLIBRARYBINDFILES 
- SYSIBM  .SYSNAMEMAPPINGS 
- SYSIBM  .SYSNODEGROUPDEF 
- SYSIBM  .SYSSERVEROPTIONS 
- SYSIBM  .SYSSERVERS 
- SYSIBM  .SYSTRANSFORMS 
- SYSIBM  .SYSVERSIONS 
- SYSIBM  .SYSWRAPPERS 
 
One of the symptoms seen is if RUNSTATS was run on any of the 
above tables prior to database upgrade, running RUNSTATS on the 
same catalog table after the upgrade may cause the instance to 
trap.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on V9.7 GA and FP1                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When a database is upgraded from any supported down level    * 
* toVersion 9.7, the table collation is not set to IDENTITY    * 
* forthefollowing catalog tables.- SYSIBM                      * 
* .SYSBUFFERPOOLNODES- SYSIBM  .SYSCOLCHECKS- SYSIBM           * 
* .SYSCOLDIST- SYSIBM  .SYSCOLGROUPDIST- SYSIBM                * 
* .SYSCOLGROUPDISTCOUNTS- SYSIBM  .SYSCOLGROUPS- SYSIBM        * 
* .SYSCOLUSE- SYSIBM  .SYSCONSTDEP- SYSIBM  .SYSHIERARCHIES-   * 
* SYSIBM  .SYSKEYCOLUSE- SYSIBM  .SYSLIBRARYBINDFILES- SYSIBM  * 
* .SYSNAMEMAPPINGS- SYSIBM  .SYSNODEGROUPDEF- SYSIBM           * 
* .SYSSERVEROPTIONS- SYSIBM  .SYSSERVERS- SYSIBM               * 
* .SYSTRANSFORMS- SYSIBM  .SYSVERSIONS- SYSIBM                 * 
* .SYSWRAPPERSOne of the symptoms seen is if RUNSTATS was run  * 
* on any oftheabove tables prior to database upgrade, running  * 
* RUNSTATS onthesame catalog table after the upgrade may cause * 
* the instancetotrap.                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to FixPack 2                                         * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
First fixed in V9.7 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.01.2010
29.07.2010
29.07.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList