DB2 FOR LUW / DB2FORLUW / B10 - DB2

A query that specifies a fetch-first-clause may return wrong 
results if there is a predicate in the same subselect.  For 
example: 
 
  SELECT ID, NAME 
  FROM TABLE1 
  WHERE <predicate> 
  ORDER BY ID 
  OFFSET ? ROWS 
  FETCH NEXT ? ROWS ONLY 
 
In some circumstances <predicate> may be applied after the 
offset-clause and fetch-first-clause are processed, which 
results in fewer rows than expected.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 11.1 fix pack 1                       * 
****************************************************************

Move the predicate into a nested subselect, e.g.: 
 
  SELECT ID, NAME 
  FROM (SELECT ID, NAME FROM TABLE1 WHERE <predicate>) 
  ORDER BY ID 
  OFFSET ? ROWS 
  FETCH NEXT ? ROWS ONLY

DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
 DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
 

First fixed in DB2 version 11.1 fix pack 1

not known / see Local fix

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

26.08.2016
05.05.2017
05.05.2017