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.
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
Microsoft SQL Server
SET LANGUAGE
clause (for session only)
For more information about database environment variables, see the documentation for your database.