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 IC63226 Status: Geschlossen

DB2 QUERY REWRITE MAY NOT COMPLETELY OPTIMIZE A QUERY CONTAINING NODENUMBER
LOCAL PREDICATE

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
DB2 Query ReWrite (QRW) may not completely optimize a query 
containing a nodenumber local predicate on a base table. This 
optimization is only valid if the following conditions are 
satisfied: 
1. There is a pair of Base Tables. 
2. The two Base Tables have the same partitioning map id 
3. The tables have equality join predicate on all the columns of 
the 
partitioning keys of the tables. 
4. Each column of the partitioning key of the first table must 
join to the column of the same order of the partitioning keys of 
the other table 
5. There is a local predicate of the form, 
NODENUMBER(<table>.<col>)=<x> where <x> can be a constant, host 
 
variable, parameter marker or a special register. 
 
Sample Query: 
 
create table T1(c11 int,c12 int,c13 int,c14 int) distribute by 
(c12,c13); 
create table T2(c21 int,c22 int,c23 int,c24 int) distribute by 
(c22,c23); 
 
before fix: 
select * from t1,t2 where nodenumber(t1.c11) = 0 and  t1.c12 = 
t2.c22 and  t1.c13 = t2.c23; 
 
after fix: 
select * from t1,t2 where nodenumber(t1.c11) = 0 and  t1.c12 = 
t2.c22 and  t1.c13 = t2.c23 and nodenumber(t2.<any col>) = 0;
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using DB2 in MPP environment                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please see Problem Description above.                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.1 Fix Pack 10                       * 
****************************************************************
Local-Fix:
Manually rewrite query with additional local predicate 
nodenumber(<table>.<col>)=<x> on other table.
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Lösung
First fixed in DB2 Version 9.1 Fix Pack 10
Workaround
keiner bekannt / siehe Local-Fix
Kommentar
Fix is available in DB2 V9.1 fix pack 10
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC63227 IC63229 IC70344 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.09.2009
20.06.2011
20.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP10
Problem behoben lt. FixList in der Version
9.1.0.10 FixList