| Oracle® Database Client Installation Guide 10g Release 2 (10.2) for Microsoft Windows Itanium (64-Bit) Part Number B14313-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Database Client Installation Guide 10g Release 2 (10.2) for Microsoft Windows Itanium (64-Bit) Part Number B14313-03 |
|
|
PDF · Mobi · ePub |
This appendix describes the following Globalization Support topics:
Installing and Using Oracle Components in Different Languages
Configuring Locale and Character Sets with the NLS_LANG Parameter
This section describes the following features:
Oracle Universal Installer runs by default in the selected language of your operating system. You can also run Oracle Universal Installer in the following languages:
Brazilian Portuguese
German
Japanese
Simplified Chinese
Traditional Chinese
French
Italian
Korean
Spanish
To run Oracle Universal Installer in a different language:
Change the language in which your operating system is running: From the Start menu, select Settings, then Control Panel. In the Control Panel, select Regional and Language Options.
Run Oracle Universal Installer by following the instructions in "Installing the Oracle Database Client Software".
Note:
The selected language is assigned to the
NLS_LANG registry parameter.You can select other languages in which to use Oracle components such as Oracle Net Configuration Assistant. However, this does not change the language in which you run Oracle Universal Installer. For the Oracle component to run in the selected language, it must be the same as the language set for your operating system. You can change your operating system language in the Regional Settings window from the Control Panel.
To use Oracle components in different languages:
Follow the instructions in "Procedure for Installing Oracle Database Client" to start Oracle Universal Installer.
From the Select a Product to Install window, select Product Languages.
The Language Selection window appears.
In the Language Selection window, select a language in which to use Oracle components from the Available Languages field.
Use the arrow (>) to move the language to the Selected Languages field and click OK.
Select the appropriate products for your installation and click Next.
After the installation completes, the dialog box wording, messages, and online help for the installed components display in the language you selected.
This section covers the following topics:
Oracle provides Globalization Support that enables users to interact with a database in their preferred locale and character set settings, as defined by the NLS_LANG parameter. When you install Oracle Database Client components, Oracle Universal Installer sets the NLS_LANG parameter in the registry.
The locale setting of your operating system determines the value of the NLS_LANG parameter at installation. Table B-1 lists the operating system locale and NLS_LANG value mappings.
The NLS_LANG parameter is stored in the registry under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID\NLS_LANG subkey, where ID is the unique number identifying the Oracle home.
The NLS_LANG parameter uses the following format:
NLS_LANG = LANGUAGE_TERRITORY.CHARACTER_SET
where:
| Parameter | Description |
|---|---|
LANGUAGE |
Specifies the language and conventions for displaying messages, day name, and month name. |
TERRITORY |
Specifies the territory and conventions for calculating week and day numbers. |
CHARACTER_SET |
Controls the character set used for displaying messages. |
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.1 and earlier; it does not support all valid XML characters. AL32UTF8 has no such limitation.
Using database character set UTF8 for XML data could potentially cause an irrecoverable 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 terminates parsing and raises an exception.
See Also:
Oracle Database Platform Guide for Microsoft Windows (32-Bit) for more information about the subkey locations for multiple Oracle homes
Oracle Database Globalization Support Guide for information about the NLS_LANG parameter and Globalization Support initialization parameters
Table B-1 lists the default NLS_LANG values for various Windows locales:
Table B-1 NLS_LANG Parameter Values
| Operating System Locale | NLS_LANG Value |
|---|---|
|
Arabic (U.A.E.) |
|
|
Bulgarian |
|
|
Catalan |
|
|
Chinese (PRC) |
|
|
Chinese (Taiwan) |
|
|
Croatian |
|
|
Czech |
|
|
Danish |
|
|
Dutch (Netherlands) |
|
|
English (United Kingdom) |
|
|
English (United States) |
|
|
Estonian |
|
|
Finnish |
|
|
French (Canada) |
|
|
French (France) |
|
|
German (Germany) |
|
|
Greek |
|
|
Hebrew |
|
|
Hungarian |
|
|
Icelandic |
|
|
Indonesian |
|
|
Italian (Italy) |
|
|
Japanese |
|
|
Korean |
|
|
Latvian |
|
|
Lithuanian |
|
|
Norwegian |
|
|
Polish |
|
|
Portuguese (Brazil) |
|
|
Portuguese (Portugal) |
|
|
Romanian |
|
|
Russian |
|
|
Slovak |
|
|
Spanish (Spain) |
|
|
Swedish |
|
|
Thai |
|
|
Spanish (Mexico) |
|
|
Spanish (Venezuela) |
|
|
Turkish |
|
|
Ukrainian |
|
|
Vietnamese |
|
Before you can use Oracle utilities such as SQL*Plus, SQL Loader, Import, and Export in MS-DOS mode, ensure that you have set the character set field of the NLS_LANG parameter for the session to the correct value.
This is required because MS-DOS mode uses, with a few exceptions, a different character set (or code-page) from Windows (ANSI code-page), and the default Oracle home NLS_LANG parameter in the registry is always set to the appropriate Windows code-page. If you do not set the NLS_LANG parameter for the MS-DOS mode session correctly, incorrect character conversion can corrupt error messages and data.
For Japanese, Korean, Simplified Chinese, and Traditional Chinese, the MS-DOS code-page is identical to the ANSI code-page. In this case, you do not need to set the NLS_LANG parameter in MS-DOS mode.
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.
Table B-2 lists the Oracle character sets that correspond to the MS-DOS mode for various operating system locales:
Table B-2 Oracle Character Sets for Operating System Locales
| Operating System Locale | Character Set |
|---|---|
|
Arabic |
|
|
Catalan |
|
|
Chinese (PRC) |
|
|
Chinese (Taiwan) |
|
|
Czech |
|
|
Danish |
|
|
Dutch |
|
|
English (United Kingdom) |
|
|
English (United States) |
|
|
Finnish |
|
|
French |
|
|
German |
|
|
Greek |
|
|
Hungarian |
|
|
Italian |
|
|
Japanese |
|
|
Korean |
|
|
Norwegian |
|
|
Polish |
|
|
Portuguese |
|
|
Romanian |
|
|
Russian |
|
|
Slovak |
|
|
Slovenian |
|
|
Spanish |
|
|
Swedish |
|
|
Turkish |
|
See Also:
" Globalization Support in the Directory" in Oracle Internet Directory Administrator's Guide for Oracle Internet Directory Globalization Support issues and requiredNLS_LANG environment variables for the various components and tools in an Oracle Internet Directory environment
|
 Copyright © 1996, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|