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

INCORRECT QUERY RESULTS WHEN USING OFFSET-CLAUSE AND/OR
FETCH-FIRST-CLAUSE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 
  ORDER BY ID
  OFFSET ? ROWS
  FETCH NEXT ? ROWS ONLY

In some circumstances  may be applied after the
offset-clause and fetch-first-clause are processed, which
results in fewer rows than expected.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description, use Local fix or upgrade to the       *
* release and fixpak that has this fix.                        *
****************************************************************
* RECOMMENDATION:                                              *
* See Error Description, use Local fix or upgrade to the       *
* release and fixpak that has this fix.                        *
****************************************************************
Local Fix:
Move the predicate into a nested subselect, e.g.:

  SELECT ID, NAME
  FROM (SELECT ID, NAME FROM TABLE1 WHERE )
  ORDER BY ID
  OFFSET ? ROWS
  FETCH NEXT ? ROWS ONLY
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT16918 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.10.2016
30.05.2017
30.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)