|
Problem IT02045
|
Status: Closed |
ACCESS PLANS CONTAINING INDEX ORING BETWEEN MDC AND NON MDC INDEX MAY NOT FETCH ALL ROWS FROM SECOND EXECUTION ONWARDS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The problem might occur for access plans containing index ORing
between two different indexes on the same MDC table, when one
index is a regular index and the other index is a block index.
The first open, fetch, and close operation on a statement with
such an access plan is working correctly and returns all
applying rows. All further open, fetch, and close operations on
the same statement may fail to return all applying rows.
An example of a vulnerable access plan:
FETCH
( 4)
37.6199
5.72592
/---+----\
386.443 1247
RIDSCN TABLE: DB2V977
( 5) T1
15.6706 Q1
2
+----------------++-----------------+
62.7736 415.667 1
SORT SORT SORT
( 6) ( 8) ( 10)
7.62301 7.97268 0.0758158
1 1 0
| | |
62.7736 415.667 1
IXSCAN IXSCAN IXSCAN
( 7) ( 9) ( 11)
7.61205 7.85609 0.0749869
1 1 0
| | |
1247 1247 1247
INDEX: DB2V977 INDEX: DB2V977 INDEX: SYSIBM
I1 I1 MDC / BLOCK INDEX
Q1 Q1 Q1 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7.0.10. *
**************************************************************** |
| Local Fix: |
|
| Solution |
The problem is first fixed in DB2 version 9.7.0.10. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.05.2014
06.11.2014
17.02.2015 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.10
|
 |
