When Essbase Server migrates a non-Unicode-mode application to Unicode mode, the character encoding in the application files is converted to UTF-8 encoding.
Before migrating application files to Unicode mode, perform the following tasks:
Back up all application and database files in the application.
See the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide.
If needed, apply the outline change files and then remove them.
If present, outline change files reside in each database directory, with the database name as the file name and a .chg extension; for example, /sample/basic/basic.chg.
To avoid mixing Unicode encoding and non-Unicode encoding in log files, back up log files and then clear or remove them.
Log files end with any of the following extensions: .log, .xcp, and .olg.
Grant Essbase Server permission to migrate applications to Unicode mode. See Setting Essbase Server to Unicode Mode.
Text files, such as calculation scripts, report scripts, and data sources, are not converted to UTF-8 encoding. For Unicode-mode applications, text files can be encoded in UTF-8 or in non-Unicode locales. You can use Essbase Unicode File Utility to convert non-Unicode-encoded files to UTF-8. See Essbase Unicode File Utility.
If you choose to work with non-Unicode text files in your Unicode-mode application, ensure that you understand how Essbase determines the locales of non-Unicode text files. See Managing File Encoding. |