|
Problem IC83737
|
Status: Closed |
OPTIMIZER RE-I/O COST ESTIMATION CAN BE INACCURATE FOR IXSCAN-FETCH |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
The Re-I/O Cost estimation can be inaccurate for the FETCH
operator in IXSCAN-FETCH when sequential prefetch is present in
the FETCH operator, and the index is not 100% clustered, and the
index is not fully qualified. Consequently, the Re-Total Cost,
which includes Re-I/O Cost, can be inaccurate too.
This problem was introduced in DB2 v9.5 Fixpack 9. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.5 Fixpack 10 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 v9.5 Fixpack 10 or higher |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.05.2012
22.08.2012
22.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.10
|
 |
