|
Problem IC81495
|
Status: Closed |
QUERIES WITH LIKE OPERATORS MIGHT RETURN INCORRECT RESULTS DUE TO AN INVALID HIGHEST PADDING CHARACTER |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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: |
Upgrade to DB2 9.5 FP9 or newer. |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed in DB2 Version 9.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.02.2012
15.03.2012
19.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
