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

STATISTICAL VIEW IS NOT USED BY THE OPTIMIZER IF THE QUERY CONTAINS A
NODENUMBER PREDICATE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
If a query contains a join for which a statistical view is also 
defined,  the optimizer will not use the statview's statistics 
to adjust cardinality estimates if the query contains a 
NODENUMBER predicate on one of the tables involved in the 
statistical view,  i.e. 
 
CREATE VIEW SV AS (SELECT T1.*, T2.* FROM T1, T2 WHERE 
T1.C1=T2-C1) 
 
Query: SELECT * FROM T1, T2, T3 WHERE T1.C1=T2.C1 AND 
T2.C2=T3.C2 AND NODENUMBER(T1.C3)=1 
 
  With this scenario,  an explain output may show the following 
message which indicates a failure to apply the statview in the 
extended diagnostics output: 
 
Diagnostic Details:     EXP0073W  The following MQT or 
statistical view was 
                        not eligible because one or more data 
filtering 
                        predicates from the query could not be 
matched with 
                        the MQT: "MRT     "."SV".
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any using statviews in DPF with a nodenumber predicate       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fixpack 1 or later               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 Version 10.1 Fixpack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
05.11.2012
05.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList