|
Problem IC67059
|
Status: Closed |
OTM fails with SQL20303N error when existing unique index no longer includes all partitioning keys on the target table |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
A unique index exists on a partitioned table, and then you
change the partitioning keys of the target table so that the
unique index definition no longer includes all the partitioning
keys, so OTM fails with the error SQL20303N when recreating this
unique index on the target table.
For example, you create a partitioned table which includes four
columns C1, C2, C3 and C4, specify the columns C1 and C2 as
partitioning keys, and create a unique index which includes the
columns C1 and C2. Then you change the partitioning keys of the
target table to the columns C2 and C3 so that existing unique
index definition doesn't include the partitioning key C3, so OTM
fails with the error SQL20303N when recreating this unique index
on the target table. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of ADMIN_MOVE_TABLE *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9,8 Fix Pack 3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Problem fixed in DB2 Version 9.8 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.03.2010
21.12.2010
21.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.8,
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
