E1: UPG: How To - Double Byte Database With Unicode-CodeBase And Database Kept As Non-Unicode

(Doc ID 656897.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.

Goal

When a customer uses double byte database (For example, for Chinese, Japanese, Korean, Arabic languages) with a Unicode code base (EnterpriseOne application release 8.9 onwards as EnterpriseOne 9.0) and the database is kept as non-Unicode, garbage may appear in tables.

For E1 8.9+ application releases, Runtime cannot stop user from entering more data than the field can hold, since Runtime does not know if user is using a Unicode or Non-Unicode table. The database layer does NOT truncate data, but instead, throws a system exception that the insert or update operation cannot be completed. This is because the size of data being inserted or updated is larger than what the database allows.

Detail of ISSUES with Double Byte database String Data:

Solution

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