suche 36x36
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 IT22968 Status: Closed

RUNSTATS with index sampling can produce INCORRECT NLEAF OF PARTITIONED
INDEX FOR LARGE RANGE PARTITIONED TABLE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When executing Runstats on a range partitioned table with one or 
more partitioned indexes, the index stats can be incorrect when 
the index sampling option is used. 
This issue mostly occurs for large number of rows in a 
partitioned table. 
 
As a result, Runstats might calculate an incorrect table Card.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* NA                                                           * 
****************************************************************
Local Fix:
Don't use the INDEXSAMPLE option or use an index sampling rate 
less than the table sampling rate. The latter will only ensure 
the cardinality statistic is calculated correctly.
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
NA
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.10.2017
15.03.2018
15.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)