Software: Apache. PHP/5.5.15 uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586 SYSTEM Safe-mode: OFF (not secure) C:\Users\Administrator\Documents\win64_11gR2_client\client\doc\install.112\e10844\ drwxrwxrwx |
Viewing file: Select action/file-type:
C Configuring Oracle Database Globalization SupportThis appendix describes the following Globalization Support topics: C.1 Installing and Using Oracle Components in Different LanguagesThis section describes the following procedures: C.1.1 Configuring Oracle Components to Run in Different LanguagesYou 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 The operating system locale usually influences Oracle components that are based on Java technology. The 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.C.1.1.1 Determining the Operating System LocaleThe 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 XP, Windows 2003, Windows Server 2003 R2, and in the classic view of the Control Panel on Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, click Regional and Language Options. In the default view of the Control Panel on Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, click Change keyboards or other input methods. To set locale for the current operating system user on Windows XP, Windows 2003, and Windows Server 2003 R2, select the desired locale from the pop-up list in Standards and formats area on the Regional Options tab. On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, select the desired locale from the Current format pop-up list on the Formats tab. Some of the locales may be unavailable until you install required operating system support files. On Windows XP, Windows 2003, and Windows Server 2003 R2, 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 the Windows System Locale is also set to the language in which the components are to be run. System Locale is called Language for non-Unicode programs on Windows XP, Windows 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. 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. On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, click the Change system locale... button on the Administrative tab, accept the use of administrative privileges, if User Account Control is active, and select the locale from the pop-up list in the opened dialog box. Note: The operating system must be restarted after the System Locale is changed. See the operating system documentation for further information about Windows locale settings.C.1.1.2 Configuring Locale and Character Sets with the NLS_LANG Environment VariableThe The NLS_LANG=language_territory.characterset In this format:
The
When you install Oracle Database components and the 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 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 will terminate parsing and raise an exception. See Also:
For example:
C.1.1.2.1 NLS_LANG Settings in Console Mode and Batch ModeBefore 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 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 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 Similarly, in batch mode, set the correct character set value of To find the current console code page, issue the Table C-1 lists the Oracle character sets that correspond to the console mode code pages. Table C-1 Oracle Character Sets for Console Mode (OEM) Code Pages
C.1.2 Installing Translation ResourcesTo 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.
C.2 Running Oracle Universal Installer in Different LanguagesThe operating system locale determines the language in which Oracle Universal Installer runs. Oracle Universal Installer may run in one of the following languages:
To run Oracle Universal Installer in a desired language:
If the selected language is not from the languages listed earlier, then Oracle Universal Installer runs in English. |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0312 ]-- |