DB2 FOR LUW / DB2FORLUW / B10 - 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:                                              * 
* MDC Tables                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please, apply this fix.                                      * 
****************************************************************

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

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
 

Please, apply this fix.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

13.10.2016
10.10.2017
10.10.2017