DB2 - Problembeschreibung
Problem IT17489 | Status: Geschlossen |
SELECT AGAINST AN MDC TABLE WITH A RANGE PREDICATE IN SMP MIGHT RETURN A WRONG RESULT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
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. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * MDC Tables * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please, apply this fix. * **************************************************************** | |
Local-Fix: | |
Disable SMP mode. Or don't specify a range predicate on the MDC columns. | |
verfügbare FixPacks: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Lösung | |
Please, apply this fix. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.10.2016 10.10.2017 10.10.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
11.1.1.1 |