|
Problem IC89846
|
Status: Closed |
TABLE MAY INHERIT WRONG COLLATION FROM A CATALOG TABLE OR VIEW |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 fix pack 3 *
**************************************************************** |
| Local Fix: |
Drop and recreate the table without referencing a catalog table
or view |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 version 10.1 fix pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.01.2013
08.10.2013
08.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
