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

QUERY MAY PERFORM BAD WHEN CONTAINS OR SCORE FUNCTIONS ARE USED WITH
VARIABLES IN THE SEARCH STRING AND REOPT ONCE IS SPECIFIED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Queries that are bound using REOPT ONCE and that use the 
CONTAINS or SCORE function may perform poorly when the search 
string is a host variable, local variable, global variable, 
parameter marker, special register or when statement 
concentrator is active. In such a situation REOPT ONCE may not 
be effective in enhancing the access plan used for the query. 
 
Applicable to both DB2 text-search and Net Search Extender text 
indexes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP 10                                     * 
****************************************************************
Local Fix:
Use REOPT ALWAYS or use literal values for the search-argument 
of the text search or net search extender function. 
 
In the case of statement concentrator, disable concentration for 
the affected statements using the corresponding bind option, CLI 
attribute or JDBC property.
Solution
Upgrade to DB2 9.7 FP 10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC98806 IC98807 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.11.2013
06.02.2015
06.02.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList