E1: UPG: Is It Recommended to Use the Unicode Conversion Field For Converting Data in Non Unicode Database From One Vendor Format to Another Vendor Format (e.g. DB2 to Oracle Database)?
(Doc ID 2766716.1)
Last updated on APRIL 09, 2021
Applies to:JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.
A third party tool is used to convert the data in database used by a Non-Unicode JD Edwards EnterpriseOne version (e.g. Xe) from one vendor format to another vendor format (e.g. convert the AS400 DB2 data to Oracle database). This is done for lift and shift installation and later to upgrade the JD Edwards EnterpriseOne application release to 9.2 which is a Unicode capable version.
The third party tool has a feature which will convert the source database data to from non-unicode to unicode format (e.g. convert the AS400 DB2 Non Unicode data to Unicode format NCHAR in Oracle database).
Is it recommended to use this feature, so that during the upgrade the Unicode Conversion will not be required?
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