DB2 - Problembeschreibung
Problem IC66294 | Status: Geschlossen |
COMPRESSION STATISTIC PCTPAGESSAVED MAY BE INACCURATE. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Lösung | |
First Fixed In DB2 Version 9.1 Fix Pack 10 | |
Workaround | |
N/A | |
Kommentar | |
N/A | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC66295 IC66296 IC67187 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 12.02.2010 16.06.2011 16.06.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1.FP10 | |
Problem behoben lt. FixList in der Version | |
9.1.0.10 |