Click OK. Step 4: Handling Duplicate Exported Text Strings

Localizing Oracle Business Intelligence 15-15

15.4.2 Understanding How the Error Message Language Is Determined

For Oracle BI Presentation Services, the error message language is set based on the NQ_SESSION.WEBLANGUAGE session variable. Presentation Services provides a default value for this variable upon installation. The value is updated when a user selects a language on the Oracle BI EE sign-in page. For other clients, including third-party clients, the error message language is determined by the following precedence model: ■ The error message language is set based on the WEBLANGUAGE session variable. ■ If the WEBLANGUAGE session variable is not set, then the error message language is based on the error language that is specified in the ODBC Data Source Name DSN that is used to access the Oracle BI Server. See Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition for information about setting the error message language in the ODBC DSN. ■ If an error message language has not been set in the ODBC DSN, then the language that is specified in the ORACLE_BI_LANG environment variable is used for error messages. To change the value of ORACLE_BI_LANG, update the character code for this variable in opmn.xml. You can view the character codes for supported languages in the ORACLE_HOMEbifoundationserverlocale directory for example, en for English, or pt-BR for PortugueseBrazilian. ■ If the ORACLE_BI_LANG environment variable is not set, then error messages are displayed in English. Note that clients for the Administration Tool and Job Manager do not set the WEBLANGUAGE session variable. Therefore, these clients follow the precedence model starting with the ODBC DSN error message setting.

15.4.3 Troubleshooting the Current Locale in the Oracle BI Server

This section provides the following information about troubleshooting the current locale in the Oracle BI Server: ■ Section 15.4.3.1, Handling the NLS Locale Not Supported Error Message ■ Section 15.4.3.2, Setting the Japanese Locale on AIX Systems Romanian ro_RO.UTF-8 RO_RO.UTF-8 ro_RO.utf8 Russian ru_RU.UTF-8 RU_RU.UTF-8 ru_RU.utf8 Slovak sk_SK.UTF-8 SK_SK.UTF-8 sk_SK.utf8 Spanish es_ES.UTF-8 ES_ES.UTF-8 es_ES.utf8 Swedish sv_SE.UTF-8 SV_SE.UTF-8 sv_SE.utf8 Thai th_TH.UTF-8 TH_TH.UTF-8 th_TH.utf8 Turkish tr_TR.UTF-8 TR_TR.UTF-8 tr_TR.utf8 Table 15–2 Cont. LOCALE Settings for UNIX Platforms Locale Platform-Independent Name Name on Solaris Name on AIX Name on HP-UXLinux 15-16 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

15.4.3.1 Handling the NLS Locale Not Supported Error Message

If you do not have the appropriate locale installed, then the Oracle BI Server does not start, and the NQSServer.log file contains the following error: [47013] NLS locale xxx is not supported by the operating system. where xxx is the locale that is specified in the NQSConfig.INI file for the SORT_ ORDER_LOCALE parameter. Take the following actions to resolve this error: ■ UNIX . Install the locale that is indicated in Table 15–2 for the requested language. ■ Windows . Add the corresponding language pack using the Regional Settings dialog.

15.4.3.2 Setting the Japanese Locale on AIX Systems

When using a Japanese localization on an AIX platform, you might discover that the Oracle BI Server does not start. If you encounter this issue, then use the following procedure. To set the Japanese locale on an AIX system: 1. Ensure that the JA_JP.UTF-8 locale is installed. If it is not, then install it. 2. Open the NQSConfig.INI file for editing, as described in Section 3.4, Using a Text Editor to Update Configuration Settings. 3. In the General section, set the following parameters, being aware that the settings are case-sensitive: – LOCALE = Japanese; – SORT_ORDER_LOCALE = Japanese; 4. Save and close the NQSConfig.INI file.

15.5 Localizing Metadata Names in the Repository

You can use the Externalize Strings utility in the Administration Tool to localize the names of subject areas, tables, hierarchies, columns, and their descriptions in the Presentation layer. You can save these text strings to an external file with ANSI, Unicode, and UTF-8 encoding options. To externalize strings for localization: 1. Open the repository in the Administration Tool. 2. Right-click any Presentation layer object, such as a subject area, presentation table, or presentation column, and select either Externalize Display Names then Generate Custom Names , or Externalize Descriptions then Generate Custom Descriptions to externalize strings. Selecting one of these right-click externalization options automatically selects the Custom display name or Custom description options in the Properties dialog for the selected object and all of its child objects. For example, if you right-click a subject area and select one of the externalization options, then the externalization flag is set on all presentation tables, columns, hierarchies, and levels within that subject area.

3. Select Tools, then select Utilities.

4. Select Externalize Strings and click Execute.

5. In the Externalize Strings dialog, select a subject area in the left pane.