DB2 FOR LUW / DB2FORLUW / A50 - DB2

When using ADMIN_MOVE_TABLE procedure or db2convert utility to 
convert the row-organized table which has cluster index into 
column-organized table, SQL2105N (reason code 10) is returned. 
For example, 
 
create table tab2( c1 char(8) not null, c2 int, c3 char(8) not 
null, c4 int, c5  int) organize by row; 
create unique index c2_indx on tab2(c1 ASC, c3 ASC) PCTFREE 20 
CLUSTER COMPRESS NO ALLOW REVERSE SCANS; 
 
db2convert -d testdb -z db2inst1 -t tab2 -force -opt 
'FORCE,NEW_STATS,REVAL_ALL_OBJECTS' -trace 
 
[SNIPPED] 
 
Table                                   RowsNum         RowsComm 
Status          Progress (%) 
--------------------------------------- --------------- 
--------------- --------------- --------------- 
"DB2INST1"."TAB2"                       0               0 
COPY            Failed 
 
**************************************************************** 
************************************************* 
 Errors: 
**************************************************************** 
************************************************* 
 
---ADMIN_MOVE_TABLE failed for table "DB2INST1"."TAB2" with 
error message below--- 
 CALL 
SYSPROC.ADMIN_MOVE_TABLE('DB2INST1','TAB2','','','','ORGANIZE BY 
COLUMN','','-','','FORCE,NEW_STATS,REVAL_ALL_OBJECTS,NOT_ENFORCE 
D','COPY,TRACE') 
 SQL2105N  The ADMIN_MOVE_TABLE procedure could not be completed 
because a prerequisite for running the procedure was not 
satisfied.  Reason code: "10".  SQLSTATE=5UA0 
 
 
SQL2448N  The db2convert command failed to convert any 
row-organized tables to column-organized tables.

**************************************************************** 
* USERS AFFECTED:                                              * 
* users who use ADMIN_MOVE_TABLE procedure or db2convert       * 
* utility to convert the row-organized table into              * 
* column-organized table.                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V105FP3.                                      * 
****************************************************************

Drop the cluster index and recreate the unique index as 
non-clustered. And cancel the failed move by calling 
ADMIN_MOVE_TABLE and then rerun db2convert command.

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fix in V105FP3.

not known / see Local fix

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

23.09.2013
26.11.2014
26.11.2014