DB2 FOR LUW / DB2FORLUW / 970 - DB2

The ADMIN_MOVE_TABLE procedure may fail with a duplicate values 
error (SQL0803N or SQL0603N) during the copy phase. 
 
 
The procedure will not ignore duplicate errors if the copy index 
is unique, we are clustering over the index, and a table scan is 
chosen to access the source data. 
 
If a table scan is used to access the data from the source 
table, insert/update/delete activity could result in the key 
values being copied from a location early in the source table, 
then removed, and reinserted into a location further down in the 
source table.  When the table scan finds the same key value 
again, it could see the duplicate values and fail with the 
SQL0803N error. 
 
If the COPY_WITH_INDEXES option is used, the indexes are created 
at the start of the COPY phase. 
 
If the COPY_WITH_INDEXES option is not used, the index creation 
is deferred to the end of the COPY phase and the duplicates 
prevent the index creation from succeeding. 
 
 
The triggers placed upon the source table to track 
insert/update/delete operations while the copy is taking place 
will account for the updates and so the duplicate error can be 
ignored during the copy phase and the source and target 
synchronized during the replay phase. 
 
This will primarily impact the moving of large tables that have 
lots of insert/update/delete operations where the unique key may 
be deleted or updated and then reinserted back into the table.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of ADMIN_MOVE_TABLE                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP6                                      * 
****************************************************************

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 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 V9.7 FP6

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC84329 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

01.09.2011
20.06.2012
20.06.2012

9.7.FP6