DB2 - Problem description
Problem IC92524 | Status: Closed |
COLLECTING INDEX-ONLY STATISTICS CAN INCORRECTLY UPDATE SYSCAT.COLUMNS.NQUANTILES AND SYSCAT.COLUMNS.NMOSTFREQ TO -1. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If a column has distribution statistics and it is the leading column in an index, collecting index-only statistics for the index will incorrectly update SYSCAT.COLUMNS.NQUANTILES and SYSCAT.COLUMNS.NMOSTFREQ to -1, suggesting the column does not have distribution statistics. However, the column's distribution statistics are not affected in the SYSCAT.SYSCOLDIST catalog. Also not affected are the distribution statistics in the table's packed descriptor which is used by the query optimizer. The problem therefore affects applications that query SYSCAT.COLUMNS.NQUANTILES and SYSCAT.COLUMNS.NMOSTFREQ, instead of SYSCAT.SYSCOLDIST, to determine if a column has distribution statistics. The db2look tool is affected by this problem. When the problem has occurred, db2look mimic output will not contain distribution statistics information for the affected columns. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 FP9 * **************************************************************** | |
Local Fix: | |
Perform a table and indexes statistics collection on the affected tables. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 V9.7 FP9 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC95347 IC98550 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.05.2013 17.12.2013 17.12.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |