DB2 - Problembeschreibung
Problem IT05185 | Status: Geschlossen |
SQL STATEMENT WITH REPARTITIONED JOINS MIGHT RETURN INCORRECT RESULTS IN A DPF SYSTEM | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
A complex SQL statement, requiring repartitioned joins in a DPF system, might produce wrong results if the following conditions are met: - The SQL statement includes two or more joins that are not collocated - At least one of the joins chosen by the optimizer is a repartitioned join, identifiable by the presence of a TQ operator somewhere below both inputs to the join - The join columns are of short-string type (CHAR, VARCHAR) with differing lengths. Note that the presence of these conditions does not always lead to incorrect results. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Database partitioning feature * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5.0.5. * **************************************************************** | |
Local-Fix: | |
You can attempt to avoid the repartition join by creating one or more materialized query tables (MQT) on each table referenced in the join, where the MQT is defined with a hash distribution key on the join columns. | |
Lösung | |
The problem was first fixed in DB2 version 10.5.0.5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.10.2014 15.12.2014 09.04.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |