|
Problem IC98807
|
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 / A50 - 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 Version 10.5 Fix Pack 4 *
**************************************************************** |
| 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. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to DB2 Version 10.5 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.01.2014
27.10.2014
27.10.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
