|
Problem IT18203
|
Status: Closed |
WRONG RESULT IS POSSIBLE IN ORACLE COMPATIBILITY MODE UNICODE DBWHEN COMPARING A CHAR COLUMN WITH A GRAPHIC CONSTANT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If Oracle compatibility mode is set, we could return wrong
results in Unicode database when comparing a char column and a
graphic constant.
example:
db2set DB2_COMPATIBILITY_VECTOR=ORA
create db testdb
connect to testdb
create table test(c1 char(3))
insert into test values('a ')
select * from test where c1 = graphic('a')
Expected:
C1
---
a
1 record(s) selected.
Actual:
C1
---
0 record(s) selected. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fix Pack 6 *
**************************************************************** |
| Local Fix: |
rewrite sql to avoid this comparison |
| Solution |
First fixed in DB2 10.1 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.12.2016
02.03.2017
02.03.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
