home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66998 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 / 970 - 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,7 Fix Pack 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
Problem fixed in DB2 Version 9.7 Fix Pack 2
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67059 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.03.2010
08.04.2010
08.04.2010
Problem solved at the following versions (IBM BugInfos)
9.0.7,
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList