Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC97793 Status: Geschlossen

INCORRECT RESULT IN UNICODE DB WITH LIKE PREDICATE AND FULLWIDTH UNDERSCORE
WILD CHARACTER ON A CLOB COLUMN

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
In a unicode database, running a query might return incorrect 
results if it contains a like predicate against a clob column, 
and the pattern to match contains a fullwidth underscore wild 
character (X'EFBCBF'). 
 
For example: 
create table tbl1 ( id int, cclob20oct clob(20)) 
insert into tbl1 values (1, X'F094AE8041') 
select id from tbl1 where cclob20oct like X'F094AE80EFBCBF' 
ID 
----------- 
 
  0 record(s) selected. 
 
<-- incorrect result returns : the matching row is not returned. 
 
Recall that the fullwidth underscore is a wildcard character. 
See the Information Center for details.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.4.                             * 
****************************************************************
Local-Fix:
Use halfwidth underscore character (X'5F') instead of a 
fullwidth underscore character (X'EFBCBF').
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
The problem is first fixed in DB2 version 10.1.0.4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.11.2013
08.05.2014
26.05.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList