DB2 - Problembeschreibung
Problem IC80456 | Status: Geschlossen |
LIKE CLAUSES MIGHT RETURN INCORRECT RESULTS FOR COLUMNS WITH VARCHAR DATA TYPE IN UNICODE DATABASES | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
In Unicode databases when clients with double-byte codepage are used, LIKE clauses might return incorrect results for columns defined as varchar data type. For example, you create a table t1 and then issue INSERT statements with values similar to the following statements: db2 "create table t1 (NAME varchar(10))" db2 "insert into t1 values ('a_abc')" db2 "insert into t1 values ('a_bc')" db2 "insert into t1 values ('a__c')" db2 "insert into t1 values ('a2bc')" db2 "insert into t1 values ('aabc')" db2 "insert into t1 values ('abc')" Then you run the following queries: db2 "select * from t1 where NAME LIKE '%a__'" <<-- SQL #1 db2 "select * from t1 where NAME LIKE '%a__a%'" <<-- SQL #2 db2 "select * from t1 where NAME LIKE '%a__b%'" <<-- SQL #3 The number of rows that you receive from the above queries is: 5 : 1 : 1, which is incorrect. The correct number of rows is: 6 : 1 : 4 and is returned by the above queries when the column NAME is defined as char data type. Note: In the above statements and queries, '__' represents one double-byte underscore character and '_' represents one single-byte underscore character. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 6. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC80667 IC80668 IC80669 IC84209 IC84216 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.12.2011 06.06.2012 06.06.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |