suche 36x36
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 IT18204 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 / B10 - 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 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************
Local Fix:
rewrite sql to avoid this comparison
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in DB2 11.1 Mod 2 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.12.2016
27.06.2017
27.06.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)