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 IC87888 Status: Closed

IMPROVE ACCURACY OF FILTER FACTOR ESTIMATE FOR NON-CORRELATED EXISTS CLAUSE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The filter factor of a non-correlated EXISTS clause, such as: 
 
... 
where 
     exists ( select 1 from table1 A, table2 B where A.key = 
b.key and A.col2 = 'XYZ') 
... 
 
May be more or less filtering depending on the results of the 
subselect in the exists.  This APAR will improve the accuracy of 
the resulting filter factor of the EXISTS clause. 
 
 
For example, you may see the exists subselect show up in the 
explain plan as a FILTER with an estimated cardinality of 0.5 
instead of a more accurate estimate for the probability a row 
will be returned from the subselect: 
 
                    /---------+ 
                  0.5 
                FILTER 
                  | 
          /-------+--------\ 
         1                   40 
      TBSCAN               ^NLJOIN 
        |                    | 
         1             /-----+------\ 
 TABFNC: SYSIBM     40                1 
      GENROW       TBSCAN           IXSCAN 
        Q4           |                | 
                    1000             1000 
               TABLE: DB2INST1  INDEX: DB2INST1 
                   TABLE1          TABLE2_PK 
                     Q2               Q1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 2                       * 
****************************************************************
Local Fix:
Use SELECTIVITY CLAUSE or Optimizer Profile to change the 
overall access plan.
available fix packs:
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

Solution
First fixed in DB2 version 10.1 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
17.12.2012
17.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList