DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 6.                            * 
****************************************************************

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 9.7 FixPack 6.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC80667 IC80668 IC80669 IC84209 IC84216 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.12.2011
06.06.2012
06.06.2012

9.7.FP6