DB2 FOR LUW / DB2FORLUW / A10 - DB2

When the source table does not have index, ADMIN_MOVE_TABLE 
creates generated index on the source table, the staging table 
and the target table in order to improve replay performance. 
First, ADMIN_MOVE_TABLE selects columns of the source table as 
many as possible until the column length exceeds the max key 
length limit of the index table space. And then it creates the 
generated index on those columns on the staging table, and also 
on the source table and the target table. 
 
In some cases(e.g. the source table has (var)graphic columns), 
ADMIN_MOVE_TABLE computes the column length incorrectly, as a 
result it creates the generated index on those columns which 
exceeds the max key length limit of the index table space, in 
turn ADMIN_MOVE_TABLE fails with SQL0614N error.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fixpack 5 or higher.                    * 
****************************************************************

Create an index for the source table before running 
SYSPROC.ADMIN_MOVE_TABLE.

Firstly fixed in DB2 V10.1 Fixpack 5.

not known / see Local fix

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

19.01.2015
14.07.2015
14.07.2015