DB2 FOR LUW / DB2FORLUW / 970 - DB2

A query that used to work fine in V9.1 returns incorrect result 
in V9.7. For example: 
 
SELECT * FROM myschema.tbl1 
WHERE C1 = 'X' 
  AND C2 = 'Y' 
  AND C3 IN ('A', 'B', 'C', 'D', 'E', 'F', 'G', 'H' ) 
  AND C4 = 'V' 
  AND '2010-01-01' BETWEEN C5 AND C6 
  AND C7 = 'Z' 
  AND C8 = '0' 
FETCH FIRST 1 ROWS ONLY 
 
The query fails to return any rows even though two rows satisfy 
the predicate criteria. If the "fetch first" option is removed, 
or "fetch first 2 rows only" is used, the query returns two rows 
as expected. 
 
The problem occurs when the following conditions are true: 
 
- Intra-partition parallelism is on 
- Query degree is greater than 1 
- Index scan is used 
- Runstats has been performed against the table and indexes

APAR fix was provided in Fixpack 4.

Disable intra-partition parallelism (may affect performance of 
other queries)

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 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
 

The fix ensures correct result set is returned for the case in 
question.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC75107 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

11.08.2010
09.05.2011
09.05.2011