home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80535 Status: Geschlossen

QUERY RETURNS INCORRECT RESULTS FOR A CORRELATED SUBQUERY AGAINST A DATA
PARTITIONED TABLE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
If the access plan for a correlated subquery contains a nested 
loop join with a partitioned table on the inner side of the 
join, and if the join predicate AND the correlated predicate are 
pushed down into the scan of the partitioned table, then it's 
possible that wrong results may occur. 
 
The defect is a logic problem during query runtime where data 
partitions are incorrectly eliminated from the scan, resulting 
in the scan failing to qualify records that should have 
otherwise been found.
Problem-Zusammenfassung:
QUERY RETURNS INCORRECT RESULTS FOR A CORRELATED SUBQUERY 
AGAINST A DATA PARTITIONED TABLE.
Local-Fix:
Since the problem is dependent upon the above mentioned access 
plan, it may be possible to get an alternate access plan that 
avoids the problematic codepath in runtime.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
If the access plan for a correlated subquery contains a nested 
loop join with a partitioned table on the inner side of the 
join, and if the join predicate AND the correlated predicate are 
pushed down into the scan of the partitioned table, then it's 
possible that wrong results may occur. 
 
The defect is a logic problem during query runtime where data 
partitions are incorrectly eliminated from the scan, resulting 
in the scan failing to qualify records that should have 
otherwise been found.
Workaround
Since the problem is dependent upon the above mentioned access 
plan, it may be possible to get an alternate access plan that 
avoids the problematic codepath in runtime.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC80536 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.12.2011
08.03.2012
08.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.5.0.9 FixList