|
Problem IC79727
|
Status: Closed |
QUERIES WITH LIKE OPERATORS MIGHT RETURN INCORRECT RESULTS DUE TO AN INVALID HIGHEST PADDING CHARACTER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
SQL statements with LIKE operators might not return the correct
rows that are expected to be returned. This problem arises when
all the following conditions are met:
a) Unicode database using language aware collation is involved.
b) The SQL statement includes a LIKE predicate or a substring
function involved in a basic predicate.
c) The LIKE predicate compares UTF-8 strings that contains
characters encoded between 0xEE8080 to 0xEFBFBF.
d) The EXPLAIN statement shows the predicate filter rows by
start or stop key predicate.
Affected platforms: AIX 64-bit, Linux 64-bit System z
(linux390), Linux 32-bit, linux 64 bit PPC
After applying a fix pack or an APAR, perform the following
steps:
1. Rebind all packages using the db2rbind all command.
2. Refresh the MQTs using the REFRESH TABLE command. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who use Unicode databases on AIX 64-bit, Linux 64-bit *
* System z (linux390), Linux 32-bit, linux 64 bit PPC *
* platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* SQL statements with LIKE operators might not return the *
* correct rows that are expected to be returned. This problem *
* arises when all the following conditions are met: *
* *
* a) Unicode database using language aware collation is *
* involved. *
* b) The SQL statement includes a LIKE predicate or a *
* substring function involved in a basic predicate. *
* c) The LIKE predicate compares UTF-8 strings that contains *
* characters encoded between 0xEE8080 to 0xEFBFBF. *
* d) The EXPLAIN statement shows the predicate filter rows by *
* start or stop key predicate. *
* *
* After applying a fix pack or an APAR, perform the following *
* steps: *
* *
* 1. Rebind all packages using the db2rbind all command. *
* 2. Refresh the MQTs using the REFRESH TABLE command. *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V9.7 FixPack 6 or later, then rebind *
* all packages and refresh MQTs. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This problem was first fixed in DB2 V9.7 FixPack 6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC81495 IC81496
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.11.2011
05.06.2012
06.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
