home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC84346 Status: Closed

OPTIMIZER CARDINALITY ESTIMATION ERRORS FOR INDEX SCAN OPERATIONS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The cardinality estimate for index scan operations requiring a 
FETCH (IXSCAN, IOA and IXA) might be inaccurate. The situations 
when this inaccuracy can occur will vary depending on many 
factors. It is more likely to occur if the index's table has 
many other indexes, column group statistics, statistical views 
or the table is range partitioned. The cardinality of the FETCH 
operator corresponding to the index scan operation might also be 
inaccurate.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP1 or subsequent fix pack               * 
****************************************************************
Local Fix:
None available.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
13.11.2012
13.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList