X

The Latest Technology Stack News Directly from EBS Development

Migrating EBS Environments to Unicode

Steven Chan
Senior Director

It is possible to migrate an E-Business Suite database to a new character set. You might need to do this when you expand your EBS deployment to additional countries, or when preparing for an upgrade to an EBS release that will be used globally.

You will generally migrate your EBS character set to Unicode (AL32UTF8).  You must use the Database Migration Utility for Unicode (DMU) to scan for data conversion issues.

Instructions for using the DMU tool with EBS character set conversions are published here:

Join the discussion

Comments ( 9 )
  • Johan Almqvist Friday, October 31, 2014

    Be very careful when doing this. Understand the limitations due to all standard E-Business VARCHAR2 columns being defined as BYTE (not char) so this can break all sorts of existing solutions when suddenly VARCHAR(30) no longer can hold 30-character values due to mulitbyte characters.


  • Maher Al-Nubani Friday, October 31, 2014

    While it's true that E-Business Suite schema is defined as BYTE semantics (as opposed to CHAR or code point semantics), however a lot of E-Business Suite customers had successfully migrated to Unicode because they had to operate globally in multiple languages. Most of the columns in E-Business Suite have enough room to accommodate the character expansion caused by multibyte encoding of characters above the ASCII range.

    The expansion ratio is two for the vast majority of languages with the exception of Thai having a 3 expansion ratio.

    Thai customers are cautioned not to consider Unicode unless they have to. Though I know at least one Thai customer who has successfully migrated and is operating with AL32UTF8 character set.


  • Riovas Monday, December 5, 2016

    Hi,

    Is this note also valid for eBS 11i?

    I have eBS 11i with DB 9.2.0.6 and i want to migrate from CL8MSWIN1251 -> AL32UTF8

    Regards

    Savo


  • Maher Alnubani Tuesday, December 6, 2016

    First, please note that this document had been updated and merged into the Globalization Guide Note 393861.1 (Appendix A).

    Second, yes, it's applicable to R11i as well, but you have to pay close attention to the differences between R11i and R12 releases detailed in the document. One major difference is that R11i supports UTF8 character set only, whereas R12 supports both UTF8 and AL32UTF8.

    Therefore, for R11i, you want to CL8MSWIN1251 -> UTF8.


  • Jame Wednesday, February 14, 2018
    We use dmu to upgrade our 12.1.0.2 database from UTF8 to AL32UTF8. But our apps node can no longer connect to rdbms. We got "Segmentation fault"

    sqlplus apps/password

    SQL*Plus: Release 8.0.6.0.0 - Production on Wed Feb 14 14:37:16 2018

    (c) Copyright 1999 Oracle Corporation. All rights reserved.

    Segmentation fault

    Q is does AL32UTF8 ever certified with 11i?
  • Maher Alnubani Thursday, February 15, 2018
    EBS 11i is NOT certified with AL32UTF8 character set. 11i uses Forms/Reports 6i, which use an older version of database required support files (RSF) that don't support AL32UTF8.
    UTF8 character set is sufficient and can support ALL EBS supported languages.
    For more details, please review:
    Oracle Applications 11i Internationalization Guide (Doc ID 333785.1)
    Internationalization Update Notes for Oracle E-Business Suite 11i (Doc ID 222663.1)
  • althaf Friday, September 14, 2018
    Have 12.1.3 E-Business want to upgrade to R12.2

    First want to convert our database character set version from US7ASCII to AL32UTF8 only at DB side Ignoring the Apps side conversion as per document(1272374.1))

    Since while laying down file system for R12.2 we will give DB tier information only.

    Can the above method will be valid
  • Miguel A. Martínez Friday, February 8, 2019
    Migrating an E-Business Suite Installation to a New Character Set (Doc ID 124721.1)

    This content has been migrated to the Globalization Guide for Oracle Applications Release 12 (Doc ID 393861.1) Appendix C.

    The proble is that in doc ID 393861.1 doesn't exist Appendix C.

    Can you help me?
  • Maher Alnubani Thursday, February 21, 2019
    Doc 124721.1 has been rewritten completely under

    Appendix A. Migrating to Unicode

    of

    Globalization Guide for Oracle Applications Release 12 (Doc ID 393861.1)
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.

Recent Content