DB2 - Problem description
Problem IC63059 | Status: Closed |
AN ALTER INDEX STATEMENT FAILS TO CHANGE THE COMPRESSION ATTRIBUTE FOR PHYSICAL XML INDEX | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When an XML index is initially created by default or with the "compress no" clause, and if an alter index statement is run to update a XML index with clause "compress yes", this alter command completes, but it does not actually change the compression attribute to "yes" for physical XML index. For example, CREATE TABLE T2 ( ID INTEGER, XMLDOC XML); create index xix_d1_t2 on T2 (XMLDOC) GENERATE KEY USING XMLPATTERN '/a/b' as SQL DOUBLE; By default, XML index xix_d1_t2 has compression NO when checking SYSCAT.INDEXES table. SELECT INDNAME, COMPRESSION, PCTPAGESSAVED FROM SYSCAT.INDEXESWHERE TABNAME = 'T2' ORDER BY INDNAME; After ALTER statement "alter index xix_d1_t2 compress yes;" completes, the compression attribute of XML logic index shows "Y", but its physical index's compression attribute still shows"N". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who uses ALTER INDEX to change XML index's compression * * attribute. * **************************************************************** * PROBLEM DESCRIPTION: * * "ALTER INDEX" compress yes/no doesn't work on XML type * * index. * **************************************************************** * RECOMMENDATION: * * Upgrade to V97FP1. * **************************************************************** | |
Local Fix: | |
create table with XML columns using "compress yes" or create XML index using "compress yes". | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Support "ALTER INDEX" for XML type index to update compress attribute. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.09.2009 25.01.2010 25.01.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |