Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC81602 Status: Closed

RUNSTATS "FOR INDEXES" CLAUSE RESETS EXISTING RANGE PARTITION
TABLE STATISTICS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 server to V9.7 Fix Pack 6                    * 
****************************************************************
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.
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in V9.7 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84440 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.02.2012
22.06.2012
22.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 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.