Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC80667 Status: Closed

LIKE CLAUSE MAY RETURN INCORRECT RESULTS FOR VARCHAR COLUMN IN UNICODE
DATABASE

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
If you have example data below: 
 
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')" 
 
* The above '__' represents one multi-byte underscore charactor 
in UTF-8. 
* The above '_' represents one single-byte undersocre charactor 
in UTF-8. 
 
And run below 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 
 
You will have below different results for char and varchar. 
 
type    : #1 : #2 : #3 : 
------------------------ 
varchar :  5 :  1 :  1 :  <<-- incorrect 
char    :  6 :  1 :  4 :  <<-- correct 
 
You will have correct results if the column is defined as char. 
But you will have incorrect results if the column is defined as 
varchar.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.1.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.1 FixPack 12.                           * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 UDB Version 9.1 FixPack 12.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.01.2012
17.07.2012
17.07.2012
Problem solved at the following versions (IBM BugInfos)
9.1.FP12
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.12 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.