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

EXECUTION OF A QUERY USING DB2 TEXT SEARCH MIGHT BE SLOW

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The execution of a query using DB2 Text Search, 
as in the following example, might be slow: 
 
   SELECT C1, C2 
   FROM T1 
   WHERE CONTAINS ( C3, 'XYZ' ) = 1 
 
You can use the EXPLAIN statement to check the access plan 
generated by the optimizer.  The access plan of this example 
query can be formatted by using db2exfmt and it might look as 
follows if you encounter this problem: 
 
Access Plan: 
----------- 
        Total Cost:             227.412 
        Query Degree:           1 
 
                Rows 
               RETURN 
               (   1) 
                Cost 
                 I/O 
                 | 
                 40 
               ^HSJOIN 
               (   2) 
               226.682 
                 112 
         /-------+--------\ 
      1000                  40 
     TBSCAN               TBSCAN 
     (   3)               (   4) 
     196.917              19.0036 
       112                   0 
       |                    | 
      1000                 1000 
 TABLE: SCHEMA   TABFNC: SYSIBMINTERNAL 
      T1          SYSTS_TEXTSEARCH 
       Q2                   Q1 
 
where the details of TBSCAN(4) will include a residual 
predicate: 
 
                Predicates: 
                ---------- 
                3) Residual Predicate, 
                        Comparison Operator:            Equal 
(=) 
                        Subquery Input Required:        No 
                        Filter Factor:                  0.04 
 
                        Predicate Text: 
                        -------------- 
                        (Q1.$C1 = 1)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 3                       * 
****************************************************************
Local Fix:
available fix packs:
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
The issue was first fixed in DB2 version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96605 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.06.2013
03.10.2013
03.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList