UTF-8 Encoding of Diacritical Characters not Properly Maintained When Inserting Data from JSON Files Into Oracle Database In ODI 12c
(Doc ID 2200952.1)
Last updated on FEBRUARY 11, 2019
Applies to:Oracle Data Integrator - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When processing a JSON file encoded in UTF-8, and inserting the data into an Oracle database with AL32UTF8 character set, the Oracle Data Integrator (ODI) 12c application does not maintain the proper encoding.
For example, the diacritical É character with rawtotext value of C38, is inserted into the database as two characters with the code EFBFBD, repeated twice: EFBFBDEFBFBD.
The following sequence of chars in the JSON file:
shows in the database as:
Note that correct accented / UTF-8 characters are shown:
- When editing the JSON file with a text editor such as Notepad...
- When viewing the contents of JSON file from a Datastore on File technology: ODI Studio > Designer > Models > myFileModel > myFileDatastore > right-click "View Data"
When viewing the contents of JSON file from a Datastore on Complex File technology: ODI Studio > Designer > Models > myComplexFileModel > myComplexFileDatastore > right-click "View Data", ODI does not show the accented / diacritical character correctly.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document