DB2 - Problembeschreibung
Problem IC84440 | Status: Geschlossen |
RUNSTATS "FOR INDEXES" CLAUSE RESETS EXISTING RANGE PARTITION TABLE STATISTICS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
If runstats is executed on a range partitioned table using the "FOR INDEXES" clause, existing partition statistics in syscat.datapartitions will be reset to 0. For example, executing runstats for only 1 index can be done as follows : runstats on table db2inst1.tab1 for detailed index db2inst1.idx1 and the data partition statistics can be retrieved as follows : select substr(tabname,1,20) as tabname,card,npages,fpages,stats_time from syscat.datapartitions where tabname = 'TAB1' With this apar, the statistics will show 0 for columns card, npages and fpages. More examples of runstats executions that will have this problem : runstats on table db2inst1.tab1 for index db2inst1.idx1; runstats on table db2inst1.tab1 for detailed indexes all; ... | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade the DB2 server to DB2 v10 Fix Pack 1 * **************************************************************** | |
Local-Fix: | |
Use the "AND INDEXES" clause, which will collect table statistics as well as index statistics. e.g. to correct example 1 : runstats on table db2inst1.tab1 AND detailed index db2inst1.idx1; Note this this will slow down runstats execution as table statistics are also gathered. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
This problem has first been fixed in DB2 V10 Fix Pack 1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.06.2012 29.11.2012 29.11.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |