DB2 FOR LUW / DB2FORLUW / 970 - DB2

In a rare timing scenario SQL doing a range table scan on a MDC
table in SMP mode only could loose rows from the result set.

There are optimizations in DB2 to determine the best next range
for each subagent to scan based on the usage of the system.
However, the calculation in the optimization does not ensure
each scan range is within the MDC block boundary and end up with
a range covering more than a single block.  On the other hand,
block predicate evaluation on a MDC table scan is done only once
per range since it does not expect the scan range to cross a
block boundary, it can incorrectly skip pages that would have
been qualified for the scan predicate.  And this is timing
related.

****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description, use Local fix or upgrade to release   *
* and fixpak that has this fix.                                *
****************************************************************
* RECOMMENDATION:                                              *
* See Error Description, use Local fix or upgrade to release   *
* and fixpak that has this fix.                                *
****************************************************************

Disable SMP mode.
Or don't specify a range predicate on the MDC columns.

not known / see Local fix

forerunner  : IT17395 
follow-up : 

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

13.10.2016
30.05.2017
30.05.2017