|
Problem IC84547
|
Status: Closed |
ADMIN_MOVE_TABLE FAILS WITH ERROR SQL2103N WHEN THERE ARE TWO INDEXES ON THE SAME COLUMN. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
ADMIN_MOVE_TABLE fails with following error, when there are two
indexes on the same column:
SQL2103N The ADMIN_MOVE_TABLE procedure could not be completed
because some aspect of either the source table or target table
is not supported by the ADMIN_MOVE_TABLE procedure. Reason
code: "17". SQLSTATE=5UA0M
The problem is re creatable as follows:
CREATE TABLE "ihubv97 "."tab1" ("NUM" VARCHAR(12) NOT NULL )
CREATE INDEX "ihubv97 "."abc" ON "ihubv97"."tab1" ("NUM" ASC);
CREATE UNIQUE INDEX "ihubv97 "."xyz" ON "ihubv97 "."tab1"
("NUM" ASC);
CALL SYSPROC.ADMIN_MOVE_TABLE('ihubv97 ', 'tab1', 'USERSPACE1',
'USERSPACE1', 'USERSPACE1', '', '', '', '', '', 'MOVE')
The above command fails with error: SQL2103N |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Customer using ADMIN_MOVE_TABLE and having two indexes on *
* the same column *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest DB2 level *
**************************************************************** |
| Local Fix: |
To create the "UNIQUE" index first and then the other index. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
06.11.2012
06.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
