Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Databases Set to a Non-English Locale

Databases Set to a Non-English Locale

If the Hub Store database environment is set to a non-English locale, ensure that the database environment uses a Unicode character set before you run the upgrade script. You set the character set using a database environment variable.
This task is not required for Microsoft SQL Server environments.
The upgrade script translates metadata to English and associates a translation key with the metadata. After the upgrade is successful, each MDM Hub Console user can select any supported locale for the user interface and databases. The locale selection for each user is stored in the Master Database with all user data.
For example, consider an MDM Hub Store that resides in an Oracle database environment in a Korean locale. Before you upgrade, you ensure that the database environment variable
NLS_LANG
is set to
KOREAN_KOREA.AL32UTF8
(Korean Unicode). After the upgrade, you can set your locale to Korean, while someone else can choose a different supported locale.
The following table lists database environment variables that you can use to set the character set:
Database
Environment Variable Name
Oracle
NLS_LANG
IBM DB2
DB2CODEPAGE
For more information about database environment variables, see the documentation for your database.

0 COMMENTS

We’d like to hear from you!