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 IC79409 Status: Closed

OPTIMIZER CARDINALITY ESTIMATION ERRORS FOR INDEX SCAN OPERATIONS

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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 the APAR text                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP6                                       * 
****************************************************************
Local Fix:
None available.
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
A fix was provided in DB2 9.7 FP6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84346 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.10.2011
05.06.2012
05.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