DB2 - Problembeschreibung
| Problem IC96605 | Status: Geschlossen |
EXECUTION OF A QUERY USING DB2 TEXT SEARCH MIGHT BE SLOW | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5 Fix Pack 3 * **************************************************************** | |
| Local-Fix: | |
| verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Lösung | |
The issue was first fixed in DB2 version 10.5 Fix Pack 3. | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.10.2013 27.02.2014 27.02.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.5.0.3 |
|
| 10.5.0.3 |
|