D.1 Installing and Using Oracle Components in Different Languages

D.1.1 Configuring Oracle Components to Run in Different Languages

You can specify the language and the territory, or locale, in which you want to use Oracle components. The locale setting of a component determines the language of the user interface of the component and the globalization behavior, such as date and number formatting. Depending on the Oracle component, the locale of the component is either inherited from the operating system session that started the component, or is defined by the NLS_LANG environment variable.

The operating system locale usually influences Oracle components that are based on Java technology. The NLS_LANG environment variable usually influences Oracle components that use Oracle Client libraries such as OCI.

Note:

The user interface of an Oracle component will be displayed in a selected language only if the appropriate translation is available and has been installed. Otherwise, the user interface will be displayed in English.

D.1.1.1 Determining the Operating System Locale

The locale setting of your operating system session determines the language of the user interface and the globalization behavior for components such as Oracle Universal Installer, Oracle Net Configuration Assistant, and Oracle Database Configuration Assistant. It also determines the globalization behavior of Oracle Database sessions created by a user application through Oracle JDBC driver, unless overridden by the application.

Open the Control Panel from the Start menu to modify the operating system locale settings. On Windows 2000, click Regional Options. On Windows XP and Windows 2003, click Regional and Language Options.

To set locale for the current operating system user on Windows 2000, select the desired locale from the pop-up list in "Settings for the current user" area on the General tab. On Windows XP and Windows 2003, select the desired locale from the pop-up list in "Standards and formats" area on the Regional Options tab.

Some of the locales may be unavailable until you install required operating system support files. On Windows 2000, make sure that the relevant language group is selected in "Language settings for the system" area on the General tab. On Windows XP and Windows 2003, make sure the relevant check boxes are checked in "Supplemental language support" area on Languages tab.

Some Oracle components, such as SQL*Plus, require that also the Windows System Locale is set to the language in which the components are to be run. System Locale is called "Language for non-Unicode programs" on Windows XP and Windows 2003. To set the System Locale on Windows 2000, click the "Set default..." button on the General tab and select the locale from the displayed pop-up list. On Windows XP and Windows 2003, select the locale from the pop-up list in the "Language for non-Unicode programs" area on the Advanced tab.

Note:

The operating system must be restarted after the System Locale is changed.

Note:

See the operating system documentation for further information about Windows locale settings.

D.1.1.2 Configuring Locale and Character Sets with the NLS_LANG Environment Variable

The NLS_LANG environment variable determines the language of the user interface and the globalization behavior for components such as SQL*Plus, exp, and imp. It sets the language and territory used by the client application and the database. It also declares the character set for entering and displaying data by the client application.

characterset specifies the encoding of the database client, which is the character set for data entered or displayed by a client program

In most cases, this is the Oracle character set that corresponds to the Windows ANSI Code Page as determined by the System Locale.

The NLS_LANG parameter on Windows can be set

in Registry under the subkey corresponding to a given Oracle home,

as an environment variable.

When you install Oracle Database components and the NLS_LANG parameter is not yet set in the Registry subkey of the target Oracle home, Oracle Universal Installer sets the NLS_LANG parameter to a default value derived from the operating system locale for the current user. See the following table.

Caution:

AL32UTF8 is the Oracle Database character set that is appropriate for XMLType data. It is equivalent to the IANA registered standard UTF-8 encoding, which supports all valid XML characters.

Do not confuse Oracle Database database character set UTF8 (no hyphen) with database character set AL32UTF8 or with character encoding UTF-8. Database character set UTF8 has been superseded by AL32UTF8. Do not use UTF8 for XML data. UTF8 supports only Unicode version 3.0 and earlier; it does not support all valid XML characters. AL32UTF8 has no such limitation.

Using database character set UTF8 for XML data could cause a fatal error or affect security negatively. If a character that is not supported by the database character set appears in an input-document element name, a replacement character (usually a question mark) is substituted for it. This will terminate parsing and raise an exception.

D.1.1.3 NLS_LANG Settings in Console Mode and Batch Mode

Before you can use Oracle utilities such as SQL*Plus, SQL Loader, Import, and Export from the Command Prompt window, you may have to set the character set field of the NLS_LANG parameter to a value different than the one set in Registry.

This is required because programs running in console mode use, with a few exceptions, a different code page (character set) from programs running in GUI mode. The default Oracle home NLS_LANG parameter in the Registry is always set to the appropriate GUI code page. If you do not set the NLS_LANG parameter for the console mode session correctly, incorrect character conversion can corrupt error messages and data.

For Japanese, Korean, Simplified Chinese, Traditional Chinese, Thai, and Vietnamese, the console (OEM) code page is identical to the GUI (ANSI) code page. In this case, you do not need to set the NLS_LANG parameter. For other languages, set the correct character set value of NLS_LANG by issuing a SET NLS_LANG command in the same Command Prompt window in which you want to start the affected utility.

Similarly, in batch mode, set the correct character set value of NLS_LANG by inserting a SET NLS_LANG command at the start of the batch procedure, according to the character set of the files to be processed in the procedure.

To find the current console code page, issue the CHCP command in the Command Prompt window. Use the reported code page number to look up the corresponding Oracle character set name in Table D-2.

Table D-2 lists the Oracle character sets that correspond to the console mode code pages.

Table D-2 Oracle Character Sets for Console Mode (OEM) Code Pages

OEM Code Page

Oracle Character Set for Console Mode

437 (US)

US8PC437

737 (Greek)

EL8PC737

775 (Baltic)

BLT8PC775

850 (Multilingual Latin I)

WE8PC850

852 (Latin II)

EE8PC852

855 (Cyrillic)

RU8PC855

857 (Turkish)

TR8PC857

858 (Multilingual Latin I + Euro)

WE8PC858

866 (Russian)

RU8PC866

874 (Thai)

TH8TISASCII

932 (Japanese Shift-JIS)

JA16SJISTILDE

936 (Simplified Chinese GBK)

ZHS16GBK

949 (Korean)

KO16MSWIN949

950 (Traditional Chinese Big5)

ZHT16MSWIN950

1258 (Vietnam)

VN8MSWIN1258

D.1.2 Installing Translation Resources

To view the user interface of Oracle components in different languages, you must install the appropriate language translations along with the component. To select the translation resources that you want to install:

Note:

Part of Oracle Database Vault user interface text is stored in database tables in the DVSYS schema. By default, only the English language is loaded into these tables. You can use Oracle Database Vault Configuration Assistant to add more languages to Oracle Database Vault. For the necessary steps, see Appendix C in Oracle Database Vault Administrator's Guide

On the Language Selection screen, select the language in which you want to use Oracle components from the Available Languages field.

Note:

The Available Languages field lists all languages supported by Oracle globalization libraries. The set of languages for which a translation is actually available is usually smaller and depends on a particular component. The scope of translation for a given component may differ between languages. For example, some translations may include all user interface text, while others may include only error messages and no help files.

Use the > arrow to move the selected language to the Selected Languages field, and then click OK.

Note:

Oracle Universal Installer will ignore languages in the Selected Languages field for which no translation is available.

Select the produc ts you want, and then click Next.

Note:

To install additional languages for a component, you will have to reinstall this component.

D.2 Running Oracle Universal Installer in Different Languages

The operating system locale determines the language in which Oracle Universal Installer runs. Oracle Universal Installer may run in one of the following languages: