|
Problem IC65896
|
Status: Closed |
DURING UPGRADE CATALOG TABLES' COLLATION MAY NOT BE SET TO IDENTITY FOR UNICODE DATABASE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
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
|
| Solution |
First fixed in V9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.01.2010
29.07.2010
29.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
