DB2 - Problem description
Problem IC89395 | Status: Closed |
TABLE MAY INHERIT WRONG COLLATION FROM A CATALOG TABLE OR VIEW | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
A standalone table may be created from a DB2 catalog table or view (schema SYSIBM or SYSCAT) using one of the following two statements: create table T like <catalog table> create table T as (select... from <catalog table>...) with no data The resulting table will inherit IDENTITY collation from the catalog table even though the database may have a different collation. A query of the table may get incorrect results due to the unexpected collation. Collation applies to columns of type CHAR, VARCHAR, CLOB, BLOB and XML. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 fix pack 8 * **************************************************************** | |
Local Fix: | |
Drop and recreate the table without referencing a catalog table or view | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 version 9.7 fix pack 8 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC89846 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.01.2013 01.04.2013 01.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |