| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC88623 | Status: Closed |
THE INDEX RECREATED WITH SYSPROC.ADMIN_MOVE_TABLE PROCEDURE MIGHT HAVE WRONG DEFINITION. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
If table for which index was created with 'GENERATE KEY USING
XMLPATTERN ... AS ... REJECT INVALID VALUES' clause was moved
with SYSPROC.ADMIN_MOVE_TABLE procedure, then recreated index
will have wrong definition.
REJECT INVALID VALUES clause will be changed to IGNORE INVALID
VALUES clause.
The issue can be observed with db2look utility:
db2look -d sample -z db2inst1 -t tab1 -e
CREATE INDEX "DB2INST1"."IND1" ON "DB2INST1"."TAB1"
("C_XML" ASC)
GENERATE KEY USING XMLPATTERN '/row/c1'
AS SQL DOUBLE REJECT INVALID VALUES
<<<<<
COMPRESS NO ALLOW REVERSE SCANS;
db2 "CALL
SYSPROC.ADMIN_MOVE_TABLE('DB2INST1','TAB1','','','','','','','',
'','MOVE')"
db2look -d sample -z db2inst1 -t tab1 -e
CREATE INDEX "DB2INST1"."IND1" ON "DB2INST1"."TAB1"
("C_XML" ASC)
GENERATE KEY USING XMLPATTERN '/row/c3'
AS SQL DOUBLE IGNORE INVALID VALUES
<<<<<
COMPRESS NO ALLOW REVERSE SCANS; | |
| Problem Summary: | |
| Local Fix: | |
No local fix. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Comment | |
This APAR is a duplicate of IC87910 | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.11.2012 17.01.2013 17.01.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.2 |
|
| 10.5.0.2 |
|