DB2 - Problem description
Problem IC80309 | Status: Closed |
"REORG INDEXES ALL" WITH "CLEANUP ONLY" AND "ON DATA PARTITION" OPTIONS RETURNS SUCCESS BUT WITHOUT CLEANING UP THE INDEXES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The REORG INDEXES ALL command with CLEANUP ONLY and ON DATA PARTITION options may return success without actually cleaning up any indexes. To hit this problem all of the following must be true: - The table is created as a partitioned table - The table contains a combination of PARTITIONED and NOT PARTITIONED indexes - The number of PARTITIONED indexes defined on the table is less than or equal to the number of NOT PARTITIONED indexes created on the table before the first PARTITIONED index is created. For example: CREATE INDEX NOT PARTITIONED CREATE INDEX PARTITIONED Hits the problem CREATE INDEX NOT PARTITIONED CREATE INDEX PARTITIONED CREATE INDEX PARTITIONED Does not hit the problem CREATE INDEX NOT PARTITIONED CREATE INDEX NOT PARTITIONED CREATE INDEX PARTITIONED CREATE INDEX PARTITIONED Hits the problem CREATE INDEX NOT PARTITIONED CREATE INDEX PARTITIONED CREATE INDEX NOT PARTITIONED CREATE INDEX PARTITIONED Does not hit the problem | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7.0.6. * **************************************************************** | |
Local Fix: | |
Drop and then recreate the NOT PARTITIONED INDEXES. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 version 9.7.0.6. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.12.2011 05.06.2012 05.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.0.6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |