ODI Does Not Properly Load Arabic Characters Into DB2/400

(Doc ID 1983222.1)

Last updated on JUNE 28, 2016

Applies to:

Oracle Data Integrator - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Symptoms

While running Oracle Data Integrator (ODI) Interfaces / Mappings for loading Arabic characters from Oracle to iSeries DB2/400, the Arabic characters are replaced by question marks (?), independently from which knowledge modules are used.

Below a screen copy showing the Arabic data:

 

... and another screen copy showing the data loaded by ODI:

 

For handling Arabic characters, iSeries requires a specific encoding (CCSID) to be used:

     https://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/rzaha/fileenc.htm
     http://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/rzahh/javadoc/ccsidList.html
     http://www.mcpressonline.com/forum/forum/programming/rpg/12799-how-to-set-job-ccsid
    
CCSID 420 (IBM EBCDIC Arabic) being the generally used value.

Though:
  • When using the Weblogic Datadirect JDBC driver, question marks are inserted regarless to the CCSID having been used for creating the DB2/400 table...
  • When using the IBM Toolbox / JTOpen JDBC driver, correct Arabic characters are inserted if CCSID 420 has been used for creating the DB2/400 table...

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms