IT18203: WRONG RESULT IS POSSIBLE IN ORACLE COMPATIBILITY MODE UNICODE DBWHEN COMPARING A CHAR COLUMN WITH A GRAPHIC CONSTANT

DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error 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.
  

Local fix

• rewrite sql to avoid this comparison
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 10.1 Fix Pack 6                               *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 10.1 Fix Pack 6
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  IT18204 IT18205 IT18206

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RA10 PSN UP

     FIX