home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97297 Status: Closed

OPTIMIZER COMPUTES INCORRECT CARDINALITY ESTIMATE IN PRESENCE OF
STATISTICAL VIEW WITH A PREDICATE THAT HAS AN EXPRESSION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The optimizer might compute an incorrect cardinality estimate in 
an access plan for a SQL statement on which a statistical view 
is eligible, if the following conditions are true: 
1) There is a statview ( sv1 ), whose SELECT list contains 
expression column. 
2) There is another statview ( sv2 ), which contains a predicate 
involving the same expression. 
 
For example, consider the following statistical views: 
create view sv1(x) as (select c1+5 from t1); 
create view sv2(y) as (select c1 from t1 where c2+1 < 2 and c1+5 
= 5); 
 
Please note the expression 'c1+5'. It is the output column of 
sv1 and it is also used in predicate for sv2. In this case, the 
optimizer might compute an incorrect cardinality estimate for 
the following SQL statement: 
select * from t1 where c1+5=5 and c2+1<2; 
 
The explain plan ( i.e. db2exfmt output ) of above SQL may show 
the following diagnostic messages: 
Diagnostic Details:     EXP0233I  The predicate "Q4.C1 + 5 = 5" 
contains 
                        an expression matching the statistical 
view column 
                        "SCHEMA1.SV1" 
 
Diagnostic Details:     EXP0147W  The following statistical view 
was used 
                        by the optimizer to estimate 
cardinalities: 
                        "SCHEMA1"."SV2".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to DB2 Version 10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.10.2013
01.09.2014
01.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList