DB2 - Problem description
Problem IC61935 | Status: Closed |
RUNSTATS TO COLLECT INDEX ONLY STATSTISTICS ON XML INDEXES MAY RESULT INCORRECT NPAGES OF TABLE STATISTICS. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
For table with XML column and XML index, having RUNSTATS with "FOR INDEXES ALL" option, which only collect index statistics, may result incorrect NPAGES of the table. The incorrect NPAGES may lead optimizer to choose lower performance access plan. The issue exists since v9.1GA, v9.5GA, v9.7GA, fixed in v9.5FP5 and v9.7FP1 and later release. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all uses * **************************************************************** * PROBLEM DESCRIPTION: * * see error description in APAR * **************************************************************** * RECOMMENDATION: * * upgrade to V97 fixpack 1 * **************************************************************** | |
Local Fix: | |
You may collect table and indexes statistics with the RUNSTATS "AND INDEXES ALL" options to work around this issue: RUNSTATS ON <SCHEMA>.<TABLE NAME> AND INDEXES ALL; | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
this problem is fixed in V97 fixpack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.07.2009 16.02.2010 16.02.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 |