DB2 - Problem description
Problem IC80008 | Status: Closed |
ON RARE OCCASIONS, DB2 MAY DETERMINE A NEGATIVE STATISTICAL VALUE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
On rare occasions, DB2 may determine a negative statistical value. This problem is dependent on the data values used to determine the statistics. When the problem occurs, it is likely to occur for a table that has a large number of rows, statistically in the order of 2^32. Negative statistical values may lead the query compiler to determine a poor access plan. The following column and column group statistics can observe the problem: syscat.columns.colcard syscat.colgroups.colgroupcard For parititioned indexes, the following index statistics can observe the problem: syscat.indexes.firstkeycard syscat.indexes.first2keycard syscat.indexes.first3keycard syscat.indexes.first4keycard syscat.indexes.fullkeycard | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL USERS on DB2 v97 FP5 and earlier * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * UPgrade to DB2 v97 FP6 * **************************************************************** | |
Local Fix: | |
There is no workaround for the index statistics. For the column and column group statistics, it is possible that a slight change in the data set might avoid the problem. If not using the TABLESAMPLE option for RUNSTATS command, try the TABLESAMPLE option. If using the TABLESAMPLE option for RUNSTATS command, try a different sample size, sampling method, or repeatable seed. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 V97 FP6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.11.2011 14.06.2012 14.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |