DB2 - Problembeschreibung
Problem IC81495 | Status: Geschlossen |
QUERIES WITH LIKE OPERATORS MIGHT RETURN INCORRECT RESULTS DUE TO AN INVALID HIGHEST PADDING CHARACTER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
Upgrade to DB2 9.5 FP9 or newer. | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
Problem Fixed in DB2 Version 9.5 Fix Pack 9 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.02.2012 15.03.2012 19.03.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP9 | |
Problem behoben lt. FixList in der Version | |
9.5.0.9 |