|
Problem IC66294
|
Status: Closed |
COMPRESSION STATISTIC PCTPAGESSAVED MAY BE INACCURATE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
PCTPAGESSAVED is set to 0 when RUNSTATS is executed on just the
indexes of the table via the FOR INDEXES clause, for example:
RUNSTATS ON TABLE s.t FOR INDEXES ALL
Under rare situations, incorrect intermediate calculations can
lead to an inaccurate PCTPAGESSAVED value, including 0 and
negative values. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* PCTPAGESSAVED is set to 0 when RUNSTATS is executed on just *
* the indexes of the table via the FOR INDEXES clause, for *
* example: *
* *
* RUNSTATS ON TABLE s.t FOR INDEXES ALL *
* *
* Under rare situations, incorrect intermediate calculations *
* can lead to an inaccurate PCTPAGESSAVED value, including 0 *
* and negative values. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 Fix Pack 10 *
**************************************************************** |
| Local Fix: |
Determine compression benefit from other compression statistics
PCTROWSCOMPRESSED and AVGROWCOMPRESSIONRATIO.
If PCTPAGESSAVED is 0 after an index-only RUNSTATS operation,
collect statistics again, ensuring to collect statistics for the
table as well as its indexes, for example:
RUNSTATS ON TABLE s.t AND INDEXES ALL |
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
First Fixed In DB2 Version 9.1 Fix Pack 10 |
| Workaround |
N/A |
| Comment |
N/A |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66295 IC66296 IC67187
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.02.2010
16.06.2011
16.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
