PK AAoa,mimetypeapplication/epub+zipPKAAiTunesMetadata.plistc artistName Oracle Corporation book-info cover-image-hash 6229209 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 343586398 publisher-unique-id E24187-05 unique-id 625975548 genre Oracle Documentation itemName Oracle® Database Client Installation Guide for Microsoft Windows, 11g Release 2 (11.2) releaseDate 2012-05-02T18:10:13Z year 2012 PKxKhcPKAAMETA-INF/container.xml PKYuPKAAOEBPS/advance.htmCW Installing Oracle Database Client Using Response Files

B Installing Oracle Database Client Using Response Files

This appendix describes how to use response files to perform a silent or noninteractive installation of Oracle Database Client. It covers the following topics:

B.1 How Response Files Work?

You can automate the installation and configuration of Oracle software, either fully or partially, by specifying a response file when you start Oracle Universal Installer. Oracle Universal Installer uses the values in the response file to provide answers to some or all of the Oracle Universal Installer prompts.

Typically, Oracle Universal Installer runs in interactive mode, which means that it prompts you to provide information in graphical user interface (GUI) screens. When you use response files to provide this information, you run Oracle Universal Installer at a command prompt using either of the following modes:

You define the settings for a silent or noninteractive installation by entering values for the variables listed in the response file. For instance, to specify the Oracle home, you would supply the appropriate value for the ORACLE_HOME variable, as in the following example:

ORACLE_HOME="C:\app\product"

Another way of specifying the response file variable settings is to pass them as command line arguments when you run Oracle Universal Installer. For example:

DRIVE_LETTER:\setup.exe_location> setup -silent "ORACLE_HOME=C:\app\product" ...

Ensure that you enclose the variable and its setting in quotes.


See Also:

Oracle Universal Installer and OPatch User's Guide for more information about response file formats.

B.1.1 Reasons for Using Silent Mode or Noninteractive Mode

Table B-1describes several reasons why you might want to run Oracle Universal Installer in silent mode or noninteractive mode.

Table B-1 Reasons for Using Silent Mode or Noninteractive Mode

ModeUses

Silent

Use silent mode to:

  • Complete an unattended installation

  • Complete several similar installations on multiple systems without user interaction

Oracle Universal Installer displays progress information in the window that you used to start it, but it does not display the Oracle Universal Installer screens.

Noninteractive

Use noninteractive mode if you want to complete similar Oracle software installations on multiple systems, providing default answers to some, but not all, of Oracle Universal Installer prompts.

If you do not specify information required for a particular Installer screen in the response file, Oracle Universal Installer displays that screen. It suppresses screens for which you have provided all of the required information.


B.1.2 General Procedure for Using Response Files

You follow these general steps to install Oracle Database Client using response files:

  1. Customize or create a response file for the installation settings that you need.

    You can create the response file by using either of the following methods:

    • Modify one of the sample response files that is provided with the installation.

    • Save response file option during run time.

    "Preparing a Response File" explains how to customize or create the response file.

  2. Run Oracle Universal Installer from a command prompt, specifying the response file, using either silent or noninteractive mode.


    Note:

    Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 require Administrator privileges at the command prompt.

    "Running Oracle Universal Installer Using the Response File" explains how to run Oracle Universal Installer with a response file.

B.2 Preparing a Response File

This section describes the methods that you can use to prepare a response file for use during silent-mode or noninteractive-mode installations:

B.2.1 Editing a Response File Template

Oracle provides response file templates for the database client and the configuration tool. These files are located in the client\response directory on the Oracle Database installation media.

Table B-2 lists the available Oracle Database Client sample response files:

Table B-2 Response Files

Response File NamePurpose

client_install.rsp

Oracle Database Client installation

netca.rsp

Oracle Net Configuration Assistant to perform the configuration with the client installation types.


To copy and modify a response file:

  1. Copy the appropriate response files from the client\response directory on the Oracle Database media to your hard drive.

  2. Modify the response files with a text file editor.

    Remember that you can specify the response file variables at the command line rather than within the response file. "How Response Files Work?" explains this method.


    See Also:

    Oracle Universal Installer and OPatch User's Guide for detailed information about creating response files. In an installed Oracle Database, select Start, then Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer Concepts Guide. It appears in HTML format.

  3. Run the response file by following the instructions in the "Running Oracle Universal Installer Using the Response File" section.

B.2.2 Saving a Response File

You can use the Oracle Universal Installer in interactive mode to save a response file, which you can edit and then use to complete silent mode or response file mode installations.

Starting with Oracle Database 11g Release 2 (11.2), you can save all the installation steps into a response file during installation by clicking Save Response File on the Summary page. You can use the generated response file for a silent installation later.

When you save the response file, you can either complete the installation, or you can exit from the installer on the Summary page, before it starts to copy the software to the system.

If you save a response file during a silent installation, then Oracle Universal Installer saves the variable values that were specified in the original source response file into the new response file.


Note:

Oracle Universal Installer does not save passwords in the response file.

To save a response file:

  1. Ensure that the computer on which you are creating the response file has met the requirements described in Chapter 2.

    When you run Oracle Universal Installer to save a response file, it checks the system to verify that it meets the requirements to install the software. For this reason, Oracle recommends that you complete all of the required preinstallation tasks and save the response file while completing an installation.

  2. At the command prompt, use the cd command to change to the directory that contains the Oracle Universal Installer setup.exe executable.


    Note:

    Windows Vista, Windows Server 2008, Windows Server 2008 R2, and Windows 7 require Administrator privileges at the command prompt.

    On the installation DVD, setup.exe is located in the database directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.

  3. Run setup.exe.

  4. After Oracle Universal Installer starts, enter the installation settings, to save the response file.

  5. When the installer displays the Summary screen, perform the following:

    • Click Save Response File and specify a file name and location for the response file. Then, click Save to save the values to the file.

    • Click Finish to create the response file and continue with the installation.

      Click Cancel if you only want to create the response file but not continue with the installation. The installation will stop, but the settings you have entered will be saved in the response file.

  6. Before you use the saved response file on another system, edit the file and make any required changes.

    Use the instructions in the file as a guide when editing it.

B.3 Running Oracle Universal Installer Using the Response File

At this stage, you are ready to run Oracle Universal Installer at the command line, specifying the response file you created, to perform the installation. On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, you must open the command prompt with Administrator privileges. The Oracle Universal Installer executable, setup.exe, provides several options. For help information about the full set of these options, run setup.exe with the -help option, for example:

DRIVE_LETTER:\setup.exe_location setup -help

A new command window appears, with the "Preparing to launch..." message. In a moment, the help information appears in that window.

To run Oracle Universal Installer and specify a response file:

  1. Place the response file on the computer where you want to install Oracle Database Client.

  2. At a command prompt, run Oracle Universal Installer with the appropriate response file. On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, you must open the command prompt with Administrator privileges.

    To start Oracle Universal Installer in silent or response file mode, enter a command similar to the following: 

    DRIVE_LETTER:\setup.exe_location [-silent] "variable=setting" [-nowelcome] [-nowait] [-noconfig]  -responseFile filename

    Note:

    Do not specify a relative path to the response file. If you specify a relative path, then Oracle Universal Installer fails.

    In this example:

    • DRIVE_LETTER: Path of the database directory on the DVD.

    • setup.exe_location: Indicates the location of setup.exe.

    • -silent: Indicates that you want to run Oracle Universal Installer in silent mode.

    • "variable=setting" refers to a variable within the response file that you may prefer to run at the command line rather than set in the response file. Enclose the variable and its setting in quotes.

    • -nowelcome: Suppresses the Welcome window that appears during installation.

    • -nowait: Closes the console window when the silent installation completes.

    • -noconfig: Suppresses running the configuration assistants during installation, performing a software-only installation instead.

    • filename: The full path and file name of the installation response file that you configured.

B.4 Performing an In-place Oracle Database Client Upgrade Using the Response File

Starting with Oracle Database 11g Release 2 (11.2.0.2), you can perform an in-place Oracle Database Client upgrade using the response file:

  1. Edit the oracle.install.client.upgrading entry in the client_install.rsp file and set it to true. By default, the oracle.install.client.upgrading entry is set to false.

  2. Run Oracle Universal Installer in silent mode as described in "Running Oracle Universal Installer Using the Response File".


See Also:

"Performing an In-place Oracle Database Client Upgrade"

PK(}HWCWPKAAOEBPS/cover.htmO Cover

Oracle Corporation

PK[pTOPKAAOEBPS/gblsupp.htm[ Configuring Oracle Database Globalization Support

C Configuring Oracle Database Globalization Support

This appendix describes the following Globalization Support topics:

C.1 Installing and Using Oracle Components in Different Languages

This section describes the following procedures:

C.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.

C.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 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 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 user session. It also declares the character set for entering and displaying data by the client application.

The NLS_LANG environment variable uses the following format:

NLS_LANG=language_territory.characterset

In this format:

  • language specifies the language used for displaying user interface, error messages, sorting, day names, and month names

  • territory specifies the conventions for default date, monetary and numeric formats

  • 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.


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:

  • Arabic (U.A.E.) - ARABIC_UNITED ARAB EMIRATES.AR8MSWIN1256

  • Chinese (PRC) - SIMPLIFIED CHINESE_CHINA.ZHS16GBK

  • Chinese (Taiwan) - TRADITIONAL CHINESE_TAIWAN.ZHT16MSWIN950

  • English (United Kingdom) - ENGLISH_UNITED KINGDOM.WE8MSWIN1252

  • English (United States) - AMERICAN_AMERICA.WE8MSWIN1252

  • French (Canada) - CANADIAN FRENCH_CANADA.WE8MSWIN1252

  • French (France) - FRENCH_FRANCE.WE8MSWIN1252

  • German (Germany) - GERMAN_GERMANY.WE8MSWIN1252

  • Hebrew - HEBREW_ISRAEL.IW8MSWIN1255

  • Japanese - JAPANESE_JAPAN.JA16SJISTILDE

  • Russian - RUSSIAN_RUSSIA.CL8MSWIN1251

  • Spanish (Spain) - SPANISH_SPAIN.WE8MSWIN1252

  • Spanish (Mexico) - MEXICAN SPANISH_MEXICO.WE8MSWIN1252

  • Spanish (Venezuela) - LATIN AMERICAN SPANISH_VENEZUELA.WE8MSWIN1252

C.1.1.2.1 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 C-1.

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

OEM Code PageOracle 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


C.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.

  1. Start Oracle Universal Installer.

  2. On the Select Installation Option screen, select the installation option and click Next.

  3. On the System Class screen, select the type of system for installing the database, and click Next.

  4. On the Grid Installation Options screen, select the type of database installation you want to perform, and click Next.

  5. On the Select Install type screen, select the type of installation, and click Next.

  6. On the Select Product Languages screen, select the language in which you want to run the product 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.

  7. 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.

C.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:

To run Oracle Universal Installer in a desired language:

  1. Change the locale for the operating system user and the System Locale as described in "Determining the Operating System Locale" section.

  2. Run Oracle Universal Installer by following the instructions in the "Installing the Oracle Database Client Software" section.

If the selected language is not from the languages listed earlier, then Oracle Universal Installer runs in English.

PK~u?[[PKAAOEBPS/overview.htm7h Oracle Database Client Installation Overview

1 Oracle Database Client Installation Overview

This chapter describes the different types of Oracle Database Client installations that you can perform, and issues to consider before you install the software:

1.1 Installation Overview

The Oracle Database Client installation process consists of five steps:

  1. Read the release notes: Read the Oracle Database Release Notes before you begin the installation. The release notes are available with the platform-specific documentation. The latest version of the release notes is available on Oracle Technology Network at

    http://www.oracle.com/technetwork/indexes/documentation/index.html

  2. Plan your installation: This overview chapter describes the installation types that you can use to install Oracle Database Client and issues to consider before you begin.

    You may also want to refer to Appendix A, "Frequently Asked Questions about Installation," in Oracle Database Installation Guide. This appendix advises on the best way to install Oracle products depending on your site's requirements.

  3. Complete preinstallation tasks: Chapter 2 describes preinstallation tasks that you must complete before installing Oracle Database Client.

  4. Install the software: Use the following sections to install Oracle Database Client:

  5. Complete postinstallation tasks: Use the following sections to complete the postinstallation tasks:

    • Chapter 4 describes recommended and required postinstallation tasks.

    • Appendix C provides information about globalization support.

1.2 Oracle Database Client and Oracle Database Interoperability

For information about interoperability between different versions of Oracle Database Client and Oracle Database releases, see Note 207303.1 on the My Oracle Support (formerly OracleMetaLink) Web site at

https://support.oracle.com/

1.3 Recommended File System

Oracle strongly recommends that you install the Oracle database home (Oracle database binaries, trace files, and so on) on Oracle ACFS or NTFS; the database files themselves must be placed on Oracle ASM if using Oracle ACFS; otherwise they cannot be placed on NTFS. Usage of Oracle ACFS and Oracle ASM or NTFS instead of FAT32 is recommended to ensure security of these files.


See Also:

"File Permissions" in Oracle Database Platform Guide for Microsoft Windows for information about the default permissions when using Oracle Universal Installer and Database Configuration Assistant to install the Oracle Database software

1.4 Managing User Accounts with User Account Control

To ensure that only trusted applications run on your computer, Windows Vista, Windows Server 2008, Windows Server 2008 R2, and Windows 7 provide User Account Control. If you have enabled this security feature, then, depending on how you have configured it, Oracle Universal Installer prompts you for either your consent or your credentials when installing Oracle Database. Provide either the consent or your Windows Administrator credentials as appropriate.

You must have Administrator privileges to run some Oracle tools, such as Database Configuration Assistant, Net Configuration Assistant, and OPatch, or to run any tool or application that writes to any directory within the Oracle home. If User Account Control is enabled, and you are logged in as the local Administrator, then you can successfully run each of these commands in the usual way. However, if you are logged in as "a member of the Administrator group," then you must explicitly invoke these tasks with Windows Administrator privileges. All the Oracle shortcuts that require Administrator privileges will be invoked as "Administrator" automatically when you click the shortcuts. However, if you run the above tools from a Windows command prompt, you must run them from an Administrator command prompt. OPatch does not have a shortcut and has to be run from an Administrator command prompt.


See Also:

"Running Tools with Windows User Account Control" in Oracle Database Platform Guide for Microsoft Windows for more information

To start a command prompt window with Windows Administrator privileges:

  1. On your desktop, create a shortcut for the command prompt window. An icon for that shortcut appears on the desktop.

  2. Right click the icon for the newly created shortcut, and specify "Run as administrator."

When you open this window, the title bar reads Administrator: Command Prompt. Commands run from within this window are run with Administrator privileges.

1.5 Oracle Database Client Installation Types

You can choose one of the following installation types when installing Oracle Database Client:

1.6 Simplified Patching of Timestamp with Time Zone Data Type

Starting with Oracle Database 11g Release 2 (11.2), the patching process of TIMESTAMP WITH TIME ZONE data type values is simplified.


See Also:

"Oracle Database 11g Release 2 (11.2) New Features in Globalization" and "Clients and Servers Operating with Different Versions of Time Zone Files" in Oracle Database Globalization Support Guide for more information about the simplified patching process and how certain clients work with server with different time zone files

1.7 Software Updates Option

Use the Software Updates feature to dynamically download and apply the latest updates released by Oracle; such as, interim patch updates, critical patch updates, Oracle Universal Installer updates, and the latest patch set updates. This functionality is available starting with Oracle Database 11g Release 2 (11.2.0.2).

You can choose to download the latest updates by providing My Oracle Support credentials or you can apply previously downloaded updates. You can also download the updates separately using the -downloadUpdates option and later apply them during the installation by providing the location where the updates are present.


See Also:

"Procedure for Installing Oracle Database Client" for more information about the -downloadUpdates option, and dynamically applying software updates during the installation

PK O77PKAAOEBPS/title.htmQ Oracle Database Client Installation Guide 11g Release 2 (11.2) for Microsoft Windows

Oracle® Database

Client Installation Guide

11g Release 2 (11.2) for Microsoft Windows

E24187-05

May 2012

Oracle Database Client Installation Guide 11g Release 2 (11.2) for Microsoft Windows

E24187-05

Copyright © 1996, 2012, Oracle and/or its affiliates. All rights reserved.

Primary Author: Reema Khosla

Contributing Authors: Janet Stern, Prakash Jashnani

Contributors: Eric Belden, Sudip Datta, David Friedman, Alex Keh, Peter LaQuerre, Rich Long, Matt McKerley, Sham Rao Pavan, Hanlin Qian, Janelle Simmons, Helen Slattery, Sujatha Tolstoy, Michael Verheij, Madhu Velukur, Sergiusz Wolicki, Sue Mavris, Mohammed Shahnawaz Quadri, Rahul S Joshi, Vishal Saxena, Krishna Itikarlapall

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

PKrPKAAOEBPS/jbridge.htm( Installing Java Access Bridge

A Installing Java Access Bridge

This appendix describes how to install Java Access Bridge, which enables use of a screen reader with Oracle components:


Note:

Java Access Bridge is not supported on Windows x64 for 64-bit database installations.

A.1 Overview of Java Access Bridge

Java Access Bridge enables assistive technologies to read Java applications running on the Windows platform. Assistive technologies can read Java-based interfaces, such as Oracle Universal Installer and Oracle Enterprise Manager Database Control.

Your Oracle Database, Oracle Database Client, and Oracle Database Examples media contain the Java Runtime Environment (JRE) 1.5, which Oracle Universal Installer uses during installation. The JRE enables use of Java Access Bridge during installation. See "Setup for Oracle Installed Components" for information about installing and configuring Java Access Bridge after you install Oracle components.

A.2 Setup for JRE 1.5

To set up Java Access Bridge with JRE 1.5, stop your assistive technology, then from the installation media root, go to install directory and double-click access_setup.bat file before the installation.

After the batch file has run, restart your assistive technology program.

A.3 Setup for Oracle Installed Components

This section describes how to install and configure Java Access Bridge for Windows after installing Oracle components. It contains the following topics:

A.3.1 Installing Java Access Bridge

To install Java Access Bridge, follow these steps:

  1. Go to the Sun Microsystem's Web site and download Java Access Bridge:

    http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html

  2. Select the accessbridge-2_0_1-manual_install.zip file and extract its files to the system where you plan to install Java Access Bridge. For example:

    DRIVE_LETTER:\AccessBridge-2_0_1

  3. Copy the Java Access Bridge files listed in Table A-1 into the JRE 1.5 directory used by Oracle components. If the files exist, overwrite them. By default, the JRE used by Oracle components is installed in:

    ORACLE_HOME\jdk\jre

    Table A-1 lists the files that you must copy from the Java Access Bridge location on your hard drive to the JRE directory used by Oracle components:

    Table A-1 Copy Files to JRE Directory

    CopyTo

    DRIVE_LETTER:\AccessBridge-2_0_1\installerFiles\jaccess-1_4.jar

    ORACLE_HOME\jdk\jre\lib\ext

    DRIVE_LETTER:\AccessBridge-2_0_1\installerFiles\access-bridge.jar

    ORACLE_HOME\jdk\jre\lib\ext

    DRIVE_LETTER:\AccessBridge-2_0_1\installerFiles\JavaAccessBridge.dll

    windows_directory\system32

    DRIVE_LETTER:\AccessBridge-2_0_1\installerFiles\WindowsAccessBridge.dll

    windows_directory\system32

    DRIVE_LETTER:\AccessBridge-2_0_1\installerFiles\JAWTAccessBridge.dll

    windows_directory\system32

    DRIVE_LETTER:\AccessBridge-2_0_1\installerFiles\accessibility.properties

    ORACLE_HOME\jdk\jre\lib


  4. You can access Java Access Bridge documentation located at

    DRIVE_LETTER:\AccessBridge-2_0_1\doc

A.3.2 Configuring Oracle Components to Use Java Access Bridge

You can configure Oracle components to use Access Bridge after you complete the installation. To do so, you must set the system variable ORACLE_OEM_CLASSPATH to point to the installed Java Access Bridge files.

Follow these steps:

  1. Display System in the Control Panel.

  2. Select the Advanced tab.

  3. Click the Environment Variables button.

  4. Click the New button under the System Variable list. The New System Variable dialog appears.

  5. In the Variable Name field, enter ORACLE_OEM_CLASSPATH.

  6. In the Variable Value field, enter the full path to jaccess.jar and access-bridge.jar.

    Use a semicolon to separate the two paths. Do not use quotes or character spaces. For example, if JRE 1.5 is installed in the default location, the setting would be:

    ORACLE_HOME\jdk\jre\lib\ext\jaccess.jar;ORACLE_HOME\jdk\jre\lib\ext\access-bridge.jar

  7. Click OK.

PK.((PKAAOEBPS/glossary.htmH Glossary

Glossary

connect descriptor

A specially formatted description of the destination for a network connection. A connect descriptor contains destination service and network route information.

The destination service is indicated by using its service name for the Oracle Database or its Oracle system identifier (SID) for Oracle release 8.0, or version 7 databases. The network route provides, at a minimum, the location of the listener through use of a network address.

default domain

The network domain within which most client requests take place. It can be the domain where the client resides, or a domain from which the client often requests network services. The default domain is also the client configuration parameter that determines what domain to append to unqualified network name requests. A name request is unqualified if it does not have a "." character within it.

easy connect naming

A Naming method that allows clients to connect to a database server without any configuration. Clients use a simple TCP/IP address, which consists of a host name and optional port number, service name, and instance name:

SQL>CONNECT user_name@host[:port][/service_name][/instance_name]
Enter password: password

installation type

An installation type is a predefined component set that automatically selects which components to install. See "Oracle Database Client Installation Types" for a list of installation types available with each top-level component.

Interprocess Communication (IPC)

A protocol used by client applications that resides on the same node as the listener to communicate with the database. IPC can provide a faster local connection than TCP/IP.

ldap.ora file

A file created by the Oracle Net Configuration Assistant that contains the following directory access information:

The ldap.ora file resides in ORACLE_HOME\network\admin.

listener

A process that resides on the server and whose responsibility is to listen for incoming client connection requests and manage the traffic to the server.

When a client requests a network session with a database server, a listener receives the actual request. If the client information matches the listener information, then the listener grants a connection to the database server.

listener.ora file

A configuration file for the listener that identifies the:

The listener.ora file resides in ORACLE_HOME\network\admin.

An Oracle Database 11g Release 2 (11.2) does not require identification of the database service because of service registration. However, static service configuration is required for an Oracle Database 11g Release 2 (11.2) if you plan to use Oracle Enterprise Manager.

local naming

A Naming method that resolves a net service name into a connect descriptor. This name is configured and stored in the tnsnames.ora file on each individual client.

Naming method

A resolution method used by a client application to resolve a connect identifier to a network address when attempting to connect to a database service. Oracle Net Services supports the following naming methods:

net service name

A simple name for a service that resolves to a connect descriptor. Users initiate a connect request by passing a username and password along with a net service name in a connect string for the service to which they want to connect:

SQL> CONNECT username@net_service_identifier
Enter password: password

Depending on your needs, net service names can be stored in a variety of places, including:

operating system authenticated connections

Windows login credentials can be used to authenticate users connecting to an Oracle Database. The benefits of Windows native authentication include:

OPS$

The initialization file parameter OS_AUTHENT_PREFIX enables users to specify a prefix that Oracle uses to authenticate users attempting to connect to the database. Oracle concatenates the value of this parameter to the beginning of the user's operating system account name and password. When a connection request is attempted, Oracle compares the prefixed username with Oracle usernames in the database.

The default value of this parameter is "" (a null string), thereby eliminating the addition of any prefix to operating system account names. In earlier releases, OPS$ (short for operating system specific) was the default setting.

Oracle Context

The root of a directory subtree with a relative distinguished name of cn=OracleContext, under which all Oracle software information is kept. There may be one (or multiple) Oracle Context in a directory. An Oracle Context can be associated with a directory naming context.

The Oracle Context can contain the following Oracle entries:

Oracle home

The directory path to install Oracle components (for example, c:\app\username\product\11.2.0\dbhome_n where n is the number of the Oracle home). You are prompted to enter an Oracle home in the Path field of the Oracle Universal Installer File Locations window.

Oracle schema

A set of rules that determine what can be stored in an LDAP-compliant directory server. Oracle has its own schema that is applied to many types of Oracle entries, including Oracle Net Services entries. The Oracle schema for Oracle Net Services entries includes the attributes the entries may contain.

Oracle Net foundation layer

A networking communication layer that is responsible for establishing and maintaining the connection between the client application and server, and exchanging messages between them.

protocol address

An address that identifies the network address of a network object.

When a connection is made, the client and the receiver of the request, such as the listener, or Oracle Connection Manager, are configured with identical protocol addresses. The client uses this address to send the connection request to a particular network object location, and the recipient "listens" for requests on this address. It is important to install the same protocols for the client and the connection recipient, as well as configure the same addresses.

repository

A set of tables located in any Oracle database accessible to the Oracle Management Server. Oracle Management Server uses a repository to store all system data and application data, information about the state of managed nodes distributed throughout the environment, as well as information about the separately licensable management packs.

service registration

A feature by which the PMON process (an instance background process) automatically registers information with a listener. Because this information is registered with the listener, the listener.ora file does not need to be configured with this static information.

Service registration provides the listener with the following information:

This information allows the listener to determine how best to service a client connection request.

SID

The Oracle system identifier that distinguishes the database from all other databases on your computer. The SID automatically defaults to the database name portion of the global database name (sales in the example sales.us.example.com) until you reach eight characters or enter a period. You can accept or change the default value.

sqlnet.ora file

A configuration file for the client or server that specifies the:

The sqlnet.ora file resides in ORACLE_HOME\network\admin.

system identifier

See SID.

Terminal Server

Microsoft Windows Terminal Server is a Windows thin-client terminal server, a product that adds support for multiple, simultaneous client sessions on the Windows Server. Windows Terminal Server provides an operating system graphical user interface (GUI) to users of Oracle databases.

tnsnames.ora file

A configuration file that contains net service names mapped to connect descriptors. This file is used for the local naming method. The tnsnames.ora file resides in ORACLE_HOME\network\admin.

UNC

See Universal Naming Convention (UNC)

typical configuration

Oracle Universal Installer option that performs a default configuration of a connection between Oracle Database Client and Oracle Database. It configures the following:

When Oracle Database Client attempts to connect, it tries local naming first, followed by easy connect naming.

unqualified name

A net service name that does not contain a network domain.

Universal Naming Convention (UNC)

The Universal Naming Convention provides a means to access files on a network without mapping the network drive to a drive letter. UNC names are constructed in the following manner:

\\computer name\share name\filename

PKHHPKAAOEBPS/post_install.htm Oracle Database Client Postinstallation Tasks

4 Oracle Database Client Postinstallation Tasks

This chapter describes the following postinstallation tasks:


Note:

This chapter describes basic configuration only. See Oracle Database Platform Guide for Microsoft Windows and product-specific administration and tuning guides for more sophisticated configuration and tuning information.

4.1 Required Postinstallation Tasks

This section covers the following topics:

4.1.1 Downloading and Installing Patches

To download required patches, check the My Oracle Support (formerly OracleMetaLink) Web site for required patches for your installation. Doing so ensures that you have the latest update of Oracle Database Client.


Note:

You cannot update Instant Client by downloading a patch. Use the procedure under "Updating Instant Client" to update Instant Client.


Note:

Browsers require an Adobe Flash plug-in, version 9.0.115 or higher to use My Oracle Support. Check your browser for the correct version of Flash plug-in by going to the Adobe Flash checker page, and installing the latest version of Adobe Flash.

If you do not have Flash installed, then download the latest version of the Flash Player from the Adobe Web site:

http://www.adobe.com/go/getflashplayer


To find and download patches:

  1. Use a Web browser to view the My Oracle Support (OracleMetaLink) Web site:

    https://support.oracle.com/

  2. Log in to My Oracle Support (formerly OracleMetaLink).


    Note:

    If you are not a My Oracle Support (formerly OracleMetaLink) registered user, then click Register here and follow the registration instructions.

  3. On the main page of My Oracle Support (formerly OracleMetaLink), click Patches & Updates.

  4. Select Advanced Search.

  5. Specify the following information, then click Go:

    • On the Advanced Search page, click the search icon next to the Product or Product Family field.

    • In the Product Family field, select Database and Tools in the search list field, then specify RDBMS Server in the text field.

    • In the Release field, specify the current release number.

    • In the Platform or Language field, select your platform.

    • Any available patch updates are displayed under the Results heading.

  6. Open the patch ReadMe file, which you can access by clicking the View README icon, and follow the installation instructions.

    Some patches install with Oracle Universal Installer; others require special procedures. Oracle recommends that you always read the README before proceeding.

  7. Return to the Patch Set page, click Download, and save the file on the system.

  8. Use an unzip utility to uncompress the Oracle patches that you downloaded from My Oracle Support (formerly OracleMetaLink). The unzip utility is located in the $ORACLE_HOME/bin directory.

4.1.2 Updating Instant Client

To update Instant Client:

  1. Download Instant Client from Oracle Technology Network http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html.

  2. Place the new files directly on top of the previous files.

    If you place the files into a different directory (and remove the previous files), be sure to update your PATH environment variable setting to reflect the new location.

4.2 Recommended Postinstallation Tasks

Oracle recommends that you perform the tasks in the following sections after completing an installation:

4.2.1 Configuring Instant Client Light

To configure Instant Client Light, you must make it the default instead of Instant Client.

To configure Instant Client Light:

  1. In the ORACLE_BASE\ORACLE_CLIENT_HOME directory, either rename or delete the oraociei11.dll file.

    The oraociei11.dll file is the main binary for Instant Client.

  2. From the ORACLE_BASE\ORACLE_CLIENT_HOME\install\instantclient\light directory, copy the oraociicus11.dll file to the ORACLE_BASE\ORACLE_CLIENT_HOME directory.

    The oraociicus11.dll file is the binary for Instant Client Light.

  3. Ensure that the PATH environment variable points to the ORACLE_BASE\ORACLE_CLIENT_HOME directory.


Note:

If the Instant Client PATH is not set, applications will try to load the regular Instant Client libraries first. If the applications cannot find these, they will attempt to load the Instant Client Light library next.

4.2.2 Connecting Oracle Database Client to an Oracle Database

After you run Oracle Universal Installer to install Oracle Database Client, you must use Net Configuration Assistant (NetCA) to configure Oracle Database Client to connect to an Oracle database. At the end of installation, Oracle Universal Installer prompts you to configure the database connection. If you bypassed that option, or if you need to change the database connection later on, use the following procedure if you installed the Administrator, Runtime, or Custom installation types.


See Also:

"Connecting Instant Client or Instant Client Light to an Oracle Database" if you had installed the Instant Client installation type

To connect Oracle Database Client to an Oracle Database:

  1. From the Start menu, choose Oracle - HOME_NAME, then Configuration and Migration Tools, then Net Configuration Assistant.

  2. In the Welcome window, select Local Net Service Name configuration and click Next.

  3. In the Net Service Name Configuration window, select Add and click Next.

  4. In the Service Name window, enter the name of the Oracle database to which you want to connect and click Next.

  5. In the Select Protocols window, select the protocol you want and click Next.

  6. In the Protocol window, depending on the protocol you selected, enter the appropriate information and click Next.

  7. In the Net Test window, select whether you want to test the connection, and click Next.

  8. In the Net Service Name window, enter a name for the net service and click Next.

  9. Answer the remaining prompts, which allow you to configure another net service name, and then click Finish to complete the configuration.

    Net Configuration Assistant creates the tnsnames.ora file in the following location:

    ORACLE_HOME\network\admin\tnsnames.ora

See Also:

Oracle Database Net Services Administrator's Guide for more information about Oracle Net Configuration Assistant

4.2.3 Connecting Instant Client or Instant Client Light to an Oracle Database

Before you can connect Instant Client or Instant Client Light to an Oracle database, ensure that the PATH environment variable specifies the directory that contains the Instant Client libraries. (By default, Oracle Universal Installer updates the PATH variable for you during the installation process, but another user may have inadvertently reset it since then.) This directory is the Oracle home directory that you specified during installation.

For example, for regular Instant Client, it is in:

C:\app\username\product\11.2.0\client_1

For Instant Client Light, it is in:

C:\app\username\product\11.2.0\client_1\light

After you have checked the PATH environment variable, you can use any of the following methods to specify Oracle Database connection information for client applications:

4.2.3.1 Specifying a Connection by Using the Easy Connect Naming Method

You can specify a connection address to an Oracle Database directly from a client application, without having to configure a tnsnames setting for the Instant Client. This method is convenient in that you do not have to create and manage a tnsnames.ora file. However, your application users must specify the host name and port number when they want to log in to your application.

For example, suppose you are running SQL*Plus on the client computer and want to connect to the sales_us database, which is located on a server whose host name is shobeen and port number is 1521. If you launch SQL*Plus from the command line, you could log in as follows:

sqlplus system/admin@//shobeen:1521/sales_us

Similarly, in your application code, you can use Oracle Call Interface net naming methods to create the Instant Client-to-Oracle Database connection. For example, the following formats in the OCIServerAttach() call specify the connection information:

  • Specify a SQL connect URL string using the following format:

    //host[:port][/service_name]

    For example:

    //shobeen:1521/sales_us

  • Alternatively, you can specify the SQL connect information as an Oracle Net keyword-value pair. For example:

    "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=shobeen) (PORT=1521))(CONNECT_DATA=(SERVICE_NAME=sales_us)))"

    See Also:

    Oracle Call Interface Programmer's Guide for more information about using Oracle Call Interface Instant Client

4.2.3.2 Specifying a Connection by Configuring a tnsnames.ora File

By default, when you install Instant Client, Oracle Universal Installer does not include a sample tnsnames.ora file nor the Oracle Net Configuration Assistant utility normally used to create it. However, if you want to shield users from having to specify actual host names and port numbers, you may want to consider using a tnsnames.ora file to set the Instant Client-to-Oracle Database connection.

You can create the tnsnames.ora file manually by copying and modifying a version of this file from another Oracle installation, or you can use Oracle Net Configuration Assistant to create and manage it for you.

To install Oracle Net Configuration Assistant:

  1. Run Oracle Universal Installer.

  2. Select the Custom installation type.

  3. In the Available Product Components list, select Oracle Network Utilities and click Next.

  4. In the Summary window, click Install, then click Exit and Yes to exit Oracle Universal Installer.

After you have installed Oracle Net Configuration Assistant, follow the procedure in "Connecting Oracle Database Client to an Oracle Database" for each client computer.

Then, on each client computer, configure either of the following settings:

  • Set the TNS_ADMIN environment variable to specify the location of the tnsnames.ora file and specify a service name from that file.

  • Place the tnsnames.ora file in the ORACLE_HOME\network\admin directory, and ensure that the ORACLE_HOME environment has been set to this Oracle home.


    See Also:

    Oracle Call Interface Programmer's Guide for more information about Oracle Call Interface Instant Client connection strings

4.2.3.3 Specifying a Connection by Using an Empty Connect String and the LOCAL Variable

You can set the connect string to an empty connect string (""), and then set the LOCAL environment variable to one of the following values:

  • A direct address, as described under "Specifying a Connection by Using the Easy Connect Naming Method"

  • Oracle Net keyword-value pair

  • A tnsnames.ora entry and TNS_ADMIN is set to the location of tnsnames.ora

  • A tnsnames.ora entry and the following:

    • tnsnames.ora file located in ORACLE_HOME/network/admin

    • The ORACLE_HOME environment variable set to this Oracle home

This method allows your applications to specify internally a connection string if the application code itself uses an empty connection string. The benefit of an empty connect string is that the application itself does not need to specify the tnsnames.ora entry. Instead, when a user invokes the application, the location of the database is determined by a script or the environment, depending on where you have set the LOCAL environment variable. The disadvantage of using empty strings is that you must configure this additional information in order for your application to connect to the database.

4.2.4 Setting Up User Accounts

For information about setting up additional user accounts, see Oracle Database Platform Guide for Microsoft Windows.

4.2.5 Using Oracle9i Language and Definition Files with Oracle Database 11g Release 2

Changes have been made to the content of some of the language and territory definition files in Oracle Database 10g and later releases. These updates are necessary to correct the legacy definitions that no longer meet the local conventions in some of the languages and territories that Oracle Database supports.

Oracle Database 11g Release 2 customers should review their existing application code to ensure that the correct cultural conventions, which were introduced and defined in Oracle Database 10g, are being used. For customers who may not be able to make the necessary code changes to support their applications, Oracle Database offers Oracle9i locale definition files with this release of Oracle Database. If the Oracle Database server installation has been configured to use the Oracle9i files, then you must enable this functionality in each client installation as well.

To enable this functionality:

  1. Run the cr9idata.pl script, by default located in ORACLE_HOME\nls\data\old.

    If the client installation type you chose does not include this directory, you can find the cr9idata.pl script in the same directory path in a default Oracle Database installation.

  2. Set the ORA_NLS10 environment variable to point to the directory where you installed the new language and territory definition files, which by default are in ORACLE_HOME\nls\data.

  3. Restart Oracle Database.


See Also:


4.2.6 Configuring Oracle Counters for Windows Performance Monitor

Before you can use to view Oracle-specific counters, you must specify the system password using operfcfg.exe located in the ORACLE_HOME\bin directory.

To set the system password, enter the following:

DRIVE_LETTER:\> ORACLE_HOME\bin\operfcfg.exe
Enter user-name: system
Enter password: password
Enter tns-alias: orcl
operfcfg: New registry values have been successfully set.

See Also:

Oracle Database Platform Guide for Microsoft Windows for additional information about Oracle Counters for Windows Performance Monitor

4.3 Required Product-Specific Postinstallation Task – Configuring Oracle Net Services

You can configure Oracle Database Client to communicate with Oracle Net Services by adding the appropriate entries to the tnsnames.ora and listener.ora files. If you have a previous release or Oracle software, you can just copy information in the Oracle Net tnsnames.ora and listener.ora configuration files from the previous release to the corresponding files in the new release.


Note:

The default location for the tnsnames.ora and listener.ora files is the ORACLE_HOME\network\admin directory.

4.4 Postinstallation Tasks for SQL Developer

This section describes tasks that you must complete after you install the software:

4.4.1 Migrating User Settings from Release 1.0

The first time you start SQL Developer after installing it or after adding any extensions, you are asked if you want to migrate your user settings from a previous release. (This occurs regardless of whether there was a previous release on your system.)


Note:

Migration of user settings is supported only from SQL Developer Release 1.0 to Release 1.1. It is not supported for migration from a pre-release version of 1.1 to Release 1.1.

These settings refer to database connections, reports, and certain SQL Developer user preferences that you set in a previous version by clicking Tools and then Preferences. However, some user preferences are not saved, and you must re-specify these using the new release.

To migrate user settings from SQL Developer Release 1.0:

  1. Install Oracle SQL Developer.

  2. When you start SQL Developer Release 1.1, click Yes when asked if you want to migrate settings from a previous release.

  3. In the dialog box that is displayed, do not accept the default location for the settings. Instead, specify the location of your Release 1.0 settings, which might be a folder whose path ends with sqldeveloper\jdev\system.

See also Section 4.4.2, "Migrating Information from Previous Releases."

4.4.2 Migrating Information from Previous Releases

If you have used a previous release of SQL Developer or a pre-release version of the current release, you may want to preserve database connections that you have been using. To preserve database connections, save your existing database connections in an XML file. To save the connections, right-click the Connections node in the Connections Navigator and select Export Connections. After you complete the installation described in this guide, you can use those connections by right-clicking the Connections node in the Connections Navigator and selecting Import Connections.

If you want to use any user-defined reports or the SQL history from a previous version, see "Location of User-Related Information" for information about where these are located. If you want to use any user-defined reports or the SQL history from Release 1.0 with both Releases 1.0 and 1.1, you must save them before using Release 1.1, because Release 1.1 modifies the files to a format that is incompatible with Release 1.0.

SQL Developer preferences (specified by clicking Tools and then Preferences) from a pre-release version of the current release cannot currently be saved and reused; you must re-specify any desired preferences.

4.4.3 Location of User-Related Information

SQL Developer stores user-related information in several places, with the specific location depending on the operating system and certain environment specifications. User-related information includes user-defined reports, user-defined snippets, SQL Worksheet history, and SQL Developer user preferences.

SQL Developer user preferences are stored under the installation directory. To preserve preferences when upgrading to a more recent version of the same SQL Developer release, but not to upgrade from Release 1.0 to 1.1, use the Check for Updates feature (click Help, then Check for Updates) to upgrade your system.

This user-related information is stored in or under the HOME environment variable location, if defined; otherwise the SQLDEVELOPER_USER_DIR location, if defined; otherwise as indicated in the following table.

The table shows the typical default locations (under a directory or in a file) for specific types of resources on different operating systems. (Note the period in the name of any directory or folder named .sqldeveloper.)

Table 4-1 Default Locations for User-Related Information

Resource TypeWindows Systems

User-defined reports

C:\Documents and Settings\<user-name>\.sqldeveloper\UserReports.xml

User-defined snippets

C:\Documents and Settings\<user-name>\.sqldeveloper\UserReports.xml

SQL history

C:\Documents and Settings\<user-name>\.sqldeveloper\SqlHistory.xml

SQL Worksheet archive files

C:\Documents and Settings\<user-name>\.sqldeveloper\tmp\

SQL Developer user preferences

<sqldeveloper_install>\sqldeveloper\sqldeveloper\system\

~/.sqldeveloper/system/


SQL Worksheet archive files contain SQL statements that you have entered. These files begin with sqldev and then have a random number (for example, sqldev14356.sql). If you close SQL Developer with a SQL Worksheet open that contains statements, then you will be prompted to save these files.

To specify a nondefault SQLDEVELOPER_USER_DIR location, do either of the following:

  • Set the SQLDEVELOPER_USER_DIR environment variable to specify another directory path.

  • Edit the <sqldeveloper_install>\sqldeveloper\sqldeveloper\bin\sqldeveloper.conf file and substitute the desired directory path for SQLDEVELOPER_USER_DIR in the following line:

    SetUserHomeVariable SQLDEVELOPER_USER_DIR

If you want to prevent other users from accessing your user-specific SQL Developer information, you must ensure that the appropriate permissions are set on the directory where that information is stored or on a directory above it in the path hierarchy. For example, you may want to ensure that the sqldeveloper folder and the <user-name>\.sqldeveloper folder under Documents and Settings are not sharable.

PKSg]PKAAOEBPS/preface.htm'! Preface

Preface

This guide provides instructions about installing and configuring Oracle Database Client for both Microsoft Windows (32-Bit) and Microsoft Windows (x64). Only the features of Oracle Database for Microsoft Windows (32-bit) and Microsoft Windows (x64) software installed on Windows Server 2003, Windows Server 2003 R2, Windows XP Professional, Windows Vista, Windows Server 2008, Windows Server 2008 R2 (x64), and Windows 7 are discussed in this guide.

This preface contains these topics:

Audience

Oracle Database Client Installation Guide for Microsoft Windows is intended for anyone installing an Oracle Database Client.

To use this document, you need the following:


See Also:


Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documentation

For more information, see these Oracle resources:

Many of the examples in this book use the sample schemas, which are installed by default when you select the Basic Installation option with an Oracle Database installation. Refer to Oracle Database Sample Schemas for information about how these schemas were created and how you can use them yourself.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://www.oracle.com/technetwork/community/join/overview/index.html

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://www.oracle.com/technetwork/indexes/documentation/index.html

Conventions

The following text conventions are used in this document:

ConventionMeaning
boldfaceBoldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italicItalic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospaceMonospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

PKTeY,!'!PKAAOEBPS/index.htm Index

Index

A  B  C  D  E  F  G  H  I  J  L  M  N  O  P  Q  R  S  T  U  V  W 

A

accessibility software, Java Access Bridge, A
Administrator installation type
about, 1.5
connecting to database, 4.2.2
disk space requirements, 2.1.1, 2.1.1
AL32UTF8 character set
upgrade considerations, 2.2.3, C.1.1.2
aliases, multiple on computers, 2.3.3
applications, empty connection strings, 4.2.3.3

B

bind order of the adapters
about, 2.3.5

C

compilers
supported, 2.2.1, 2.2.2
components
unsupported
Windows Terminal Server, 2.4.1
computers with multiple aliases, 2.3.3
computers, non-networked, 2.3.4
configuration assistants
suppressing during silent or noninteractive installation, B.3
troubleshooting, D.5, D.5
connecting to database, 4.2.2
counters, Oracle Counters for Windows Performance Monitor, 4.2.6
Custom installation type
about, 1.5
connecting to database, 4.2.2

D

Database Configuration Assistant (DBCA)
suppressing during silent or noninteractive installation, B.3
databases
connecting to, 4.2.2
removing, 5
Deinstallation Tool
about, 5.1
DHCP computers, installing on, 2.3.1
disk space
checking, 2.1.2, 2.1.2
requirements, 2.1.1
DVD drive, installing from, 3.2.1
Dynamic Host Configuration Protocol. See DHCP

E

easy connect naming method for Instant Client-to-database connection, 4.2.3.1
empty connect strings, 4.2.3.3
environment variables
LOCAL, 4.2.3.3
NLS_LANG, C.1.1.2
ORA_NLS10, 4.2.5
ORACLE_HOSTNAME, 2.3.2
ORACLE_OEM_CLASSPATH, A.3.2
TNS_ADMIN, 4.2.3.2
errors
configuration assistants, D.5
fatal, D.5.2
installation, D.3
noninteractive installation, D.4
silent mode, D.4
existing Oracle installation, 3.1.5

F

fatal errors, D.5.2, D.5.2
files, Oracle Universal Installer log files, D.3

G

globalization support, C

H

hard disk space
checking, 2.1.2
requirements, 2.1.1
hardware requirements, 2.1
host name, setting before installation, 2.3.2
hosts file
editing for multihomed computers, 2.3.2
location, 2.3.2

I

In-place upgrade, 3.1.6, 3.3.2
performing, 3.3.3
using response file, B.4
installActions.log file, D.3
installation
accessing installation software, 3.2
computer aliases, multiple, 2.3.3
downloading software from Oracle Technology Network, 3.2.3
DVD drive, 3.2.1
errors, D.3
guidelines, 3.3.1, 3.3.1
laptops, 2.3.4
log file (interactive install), D.3
log file (noninteractive install), D.4
log files (interactive install), D.3
multiple, 3.1.2
noninteractive mode error handling, D.4
Oracle base directory, 3.1.3
Oracle homes, multiple, 3.1.4
overview, 1.1
preinstallation considerations, 3.1
procedure, 3.3.2
quick installation, Preface, Preface
remote installation with remote access software, 3.2.2
remote installation, DVD drive, 3.2.1.1
response files, D.4
silent mode error handling, D.4
suppressing screens, B.3
troubleshooting, D
with existing Oracle installations, 3.1.5
installation guidelines, 3.3.1
installation software, accessing, 3.2
installation types
about, 1.5
Administrator, 1.5
Custom, 1.5
Instant Client, 1.5
Runtime, 1.5
Instant Client
about, 1.5
connecting to database with Oracle Call Interface, 4.2.3.1
connecting to Oracle Database, 4.2.3
disk space requirements, 2.1.1, 2.1.1
easy connect naming method, 4.2.3.1
empty connect strings, 4.2.3.3
installation type, 1.5
Instant Client Light
about, 1.5
configuring, 4.2.1
connecting to database, 4.2.3
requirements for language and character sets, 2.2.3
updates, 4.1.2
LOCAL environment variable, connecting to database, 4.2.3.3
TNS_ADMIN environment variable, connecting to database, 4.2.3.2
tnsnames.ora file connection method, 4.2.3.2
updates, 4.1.2
Instant Client Light
about, 1.5
configuring, 4.2.1
connecting to database, 4.2.3
disk space requirements, 2.1.1
requirements for language and character sets, 2.2.3
updates, 4.1.2
IP addresses, multiple, 2.3.2

J

Java Access Bridge
about, A.1
configuring, A.3.2
installing, A.3.1
JRE 1.5, A.2
Java Runtime Environment (JRE)
guideline for modifying, 3.3.1
requirements, 2.1.1
JRE. See Java Runtime Environment (JRE)

L

languages
installing Oracle components in different languages, C.2
Oracle9isupport postinstallation step, 4.2.5
using Oracle components in different languages, C.1.2
laptops, installing Oracle Database on, 2.3.4
listener.ora file
Oracle Net Services configuration, 4.3
LOCAL environment variable, 4.2.3.3
log files
if encounter errors, D.2
interactive, D.3
noninteractive, D.4
reviewing installation session, D.3
loopback adapters
about, 2.3.5
checking if installed, 2.3.5.1
computers with multiple aliases, 2.3.3
installing, 2.3.5
installing on Windows 2003, 2.3.5.2, 2.3.5.2
installing on Windows Vista and Windows Server 2008, 2.3.5.3, 2.3.5.4
installing on Windows Vista or Windows Server 2008, 2.3.5.3, 2.3.5.4
installing on Windows XP, 2.3.5.2
non-networked computers, 2.3.4
removing, 2.3.5.5, 2.3.5.5
See also network adapters, primary network adapters

M

memory
checking, 2.1.2
requirements, 2.1
multihomed computers, installing on, 2.3.2
multiple aliases, computers with, 2.3.3
multiple Oracle homes
setting, 2.3.2
My Oracle Support (formerly OracleMetaLink) Web site, 2.4

N

Net Configuration Assistant (NetCA)
suppressing during silent or noninteractive installation, B.3
NetCA. See Oracle Net Configuration Assistant (NetCA)
netca.rsp response file, B.2.1
network adapters
computers with multiple aliases, 2.3.3
how primary adapter is determined, 2.3.5
non-networked computers, 2.3.4
primary, on computers with multiple aliases, 2.3.3
See also loopback adapters, primary network adapters
network cards, multiple, 2.3.2
network topics
about, 2.3
computers with multiple aliases, 2.3.3
DHCP computers, 2.3.1
laptops, 2.3.4
listed, 2.3
loopback adapters, 2.3.5
multiple network cards, 2.3.2
non-networked computers, 2.3.4
NLS_LANG environment variable, C.1.1.2
noninteractive installation
errors, D.4
noninteractive mode
about, B.1
error handling, D.4
reasons for using, B.1.1
See also response files, silent mode, B.1
non-networked computers, 2.3.4
NTFS systems, hard disk space requirements, 2.1.1

O

Operfcfg.exe utility, 4.2.6
ORA_NLS10 environment variable, 4.2.5
Oracle Administration Assistant for Windows, 3.1.4
Oracle Automatic Storage Management (Oracle ASM)
silent or noninteractive mode installations, B.1.2
Oracle base directory, creation of, 3.1.3
Oracle Call Interface
Instant Client connection method, 4.2.3.1
See also Instant Client
Oracle components
using in different languages, C.1.2
Oracle Counters for Windows Performance Monitor, 3.1.4, 4.2.6
Oracle Database
connect Oracle Database Client to, 4.2.2
connecting to Instant Client, 4.2.3
Oracle Database Client
guidelines for installing, 3.3.1
installation procedure, 3.3.2
preinstallation requirements, 2
Oracle home directory
multiple homes, network considerations, 2.3.2
Oracle homes, multiple, 3.1.4
Oracle host name, setting before installation, 2.3.2
Oracle Net Configuration Assistant (NetCA)
about, 4.2.2
connecting client to database, 4.2.2
installing, 4.2.3.2
noninteractive installation, B.2.1
response file, B.2.1
tnsnames.ora configuration, 4.2.2
troubleshooting, D.5
Oracle Net Services
configuring, 4.3
Oracle Objects for OLE, 3.1.4
Oracle Provider for OLE DB, 3.1.4
Oracle Technology Network (OTN)
accessing, 3.2.3
downloading software from, 3.2.3
Oracle Univeral Installer
location of executable, B.3
Oracle Universal Installer
log files, D.3
running in different languages, C.2
version to use, 3.3.1
Oracle Universal Installer (OUI)
running at command line, B.3
ORACLE_HOSTNAME environment variable
about, 2.3.2
computers with multiple aliases, 2.3.3
multihomed computers, 2.3.2
setting before installation, 2.3.2
ORACLE_OEM_CLASSPATH environment variable, A.3.2
Oracle9i language and territory support, 4.2.5
OTN. See Oracle Technology Network
OUI. See Oracle Universal Installer

P

paging file size
checking, 2.1.2
requirements, 2.1
patches
downloading and installing, 4.1.1
postinstallation task, 4.1.1
physical RAM
checking, 2.1.2
requirements, 2.1
postinstallation tasks
configuring Oracle Net Services, 4.3
downloading and installing patches, 4.1.1, 4.1.1
Instant Client-to-database connection, 4.2.3
Oracle Database Client-to-database connection, 4.2.2
Oracle9i language and territory support, 4.2.5
recommended, 4.2
required, 4.1.1
user accounts, 4.2.4
preinstallation considerations, 3.1
primary network adapters
how determined, 2.3.5
See also loopback adapters, network adapters
product postinstallation task, configuring Oracle Net Services, 4.3

Q

quick installation, Preface, Preface

R

RAM
checking, 2.1.2
requirements, 2.1
reinstalling Oracle software, 3.3.1
remote access software, 3.2.2
remote installations
about, 3.2.2
DVD drive, 3.2.1.1
removing
Oracle Database Client, overall procedure, 5
requirements
hard disk space, 2.1.1
hardware, 2.1
Java Runtime Environment, 2.1.1
software, 2.2
Web browser support, 2.4.5
requirements, Oracle Database Client, 2
response files
about, B.1
creating
with response file mode, B.2.2
with template, B.2.1
error handling, D.4
general procedure, B.1.2
Oracle Automatic Storage Management (Oracle ASM), B.1.2
passing values at command line, B.1
specifying with Oracle Universal Installer, B.3
See also silent mode, noninteractive mode, B.1
Runtime installation type
about, 1.5
connecting to database, 4.2.2
disk space requirements, 2.1.1, 2.1.1

S

setup.exe. See Oracle Universal Installer (OUI)
silent mode
about, B.1
error handling, D.4
reasons for using, B.1.1
See also noninteractive mode, response files, B.1
software
requirements, 2.2
software updates option, 1.7
software, removing, 5
suppressed mode. See noninteractive mode
swap space
checking, 2.1.2
requirements, 2.1
Symantec pcAnywhere remote access software, 3.2.2

T

temporary directory, 2.1.2
temporary disk space
checking, 2.1.2, 2.1.2
freeing, 2.1.2
requirements, 2.1
tmp directory
checking space in, 2.1.2
freeing space in, 2.1.2
TNS_ADMIN environment variable, 4.2.3.2
tnsnames.ora file
Instant Client-to-database connection,_ 4.2.3.2
Oracle Net Services configuration, 4.3
troubleshooting, D
Inventory log files, D.3

U

unsupported components
on Windows Terminal Server, 2.4.1
updating Instant Client, 4.1.2
upgrading
AL32UTF8 character set, 2.2.3, C.1.1.2
upgrading. See patches
user accounts, 4.2.4

V

VNC remote access software, 3.2.2

W

Web browser support, 2.4.5
Windows
compilers, supported, 2.2.1, 2.2.2
Windows Terminal Services, unsupported components, 2.4.1
PK(PKAAOEBPS/install.htm Installing Oracle Database Client

3 Installing Oracle Database Client

You can use 32-Bit media for installing Oracle Database Client on all supported operating systems. You can use 64-Bit media for installing Oracle Database Client on all supported 64-bit x64 operating systems. This guide is for both Windows 32-Bit and Windows x64. This chapter covers the following topics:

3.1 Preinstallation Considerations Before Installing Oracle Database Client

The Oracle Database Client software is available on the Oracle Technology Network (OTN) Web site. In most cases, you use the graphical user interface (GUI) provided by Oracle Universal Installer to install the software. However, you can also use Oracle Universal Installer to complete silent or noninteractive installations using response files, without using the GUI.

Review the information in Chapter 1, "Oracle Database Client Installation Overview" and complete the tasks listed in Chapter 2, "Oracle Database Client Preinstallation Requirements" before beginning the installation.

Next, consider the following issues:

3.1.1 Installation Consideration on Windows Vista and Later

On Windows Vista, Windows Server 2008, Windows Server 2008 R2, and Windows 7, command prompts should be opened with Administrator privileges.


See Also:

"Managing User Accounts with User Account Control"

3.1.2 Installing Oracle Database Client Installations in Silent or Noninteractive Mode

If you need to perform multiple installations of Oracle Database Client, you may want to use silent or noninteractive mode, with response files. In these modes, at each computer, you run Oracle Universal Installer from the command line using a response file. The response file is a text file containing the settings you normally enter in the Oracle Universal Installer GUI dialog boxes. This method lets you quickly perform multiple installations using similar settings for each computer.


See Also:

Appendix B, "Installing Oracle Database Client Using Response Files" for instructions on performing silent and noninteractive installations

3.1.3 Creating the Oracle Base Directory

If you install Oracle Database Client on a computer with no other Oracle software installed, Oracle Universal Installer creates an Oracle base directory for you. If Oracle software is already installed, one or more Oracle base directories already exist. In the latter case, Oracle Universal Installer offers you a choice of Oracle base directories into which you can install Oracle Database Client.

You are not required to create an Oracle base directory before installation, but you can do so if you want.


Note:

You can choose to create a new Oracle base directory, even if other Oracle base directories exist on the system.

3.1.4 Installing Oracle Database Client into Multiple Oracle Homes

You can install all Oracle components in multiple Oracle homes on the same computer. However, some components can only support one active instance at a time. This means that the current (latest) installation renders the previous one inactive. These components are:

  • Oracle Administration Assistant for Windows

  • Oracle Counters for Windows Performance Monitor

  • Oracle Objects for OLE on Windows 32-bit

  • Oracle Provider for OLE DB


Note:

Oracle Objects for OLE is not supported on Windows x64.

3.1.5 Installing Oracle Database Client on a System with an Existing Oracle Software

Oracle Database Client can be installed in the same Oracle Database home if both products are at the same release level. For example, you can install Oracle Database Client 10g Release 2 (10.2) into an existing Oracle Database 10g Release 2 (10.2) home. If you apply a patch set before installing the client, then you must apply the patch set again. Oracle Universal Installer will prompt you for an Oracle home directory, whether you have other Oracle software installed on the computer or not. You cannot install products from one release of Oracle Database Client into an Oracle home directory of a different release. For example, you cannot install Oracle Database 11g release 1 (11.1) software into an existing Oracle9i Oracle home directory.

You can install this release more than once on the same system as long as each installation is installed in a separate Oracle home directory.

3.1.6 Updating the Existing Software with the Current Version

Use the In-Place Upgrade feature to upgrade an existing client installation to the latest release by installing the new client software into an existing client home with the same installation type. For example, if release 11.2.0.1 is installed, then use Oracle Universal Installer to upgrade to release 11.2.0.2.

Consider the following before selecting this option:

  • This upgrade is only possible in a client home and not in any other Oracle home that contains non-client installations, such as Database installations.

  • This upgrade does not delete files in the client home that are commonly updated by other users. For example, configuration data files.

  • This upgrade cannot be performed if processes associated with the Oracle Database Client home are running.

This functionality is available starting with Oracle Database 11g Release 2 (11.2.0.2).


See Also:

"Performing an In-place Oracle Database Client Upgrade"

3.2 Accessing the Installation Software

The Oracle Database Client software is available on installation media or you can download it from the Oracle Technology Network (OTN) Web site, or Oracle Software Delivery Cloud Web site. To install the software from the hard disk, you must either download it and unpack it, or copy it from the installation media, if you have it.

You can access and install Oracle Database Client by using the following scenarios:

3.2.1 Installing from a Remote DVD Drive

If the computer where you want to install Oracle Database Client does not have a DVD drive, you can perform the installation from a remote DVD drive. You must complete the following steps:

3.2.1.1 Step 1: On the Remote Computer, Share the DVD Drive

The remote DVD drive that you want to use must allow shared access. To set this up, perform these steps on the remote computer that has the DVD drive:

  1. Log in to the remote computer as an Administrator user.

  2. Start Windows Explorer.

  3. Right-click the DVD drive letter and choose Sharing (or Sharing and Security).

  4. Click the Sharing tab and do the following:

    1. Select Share this folder.

    2. In Share name, give it a share name such as dvd. You will use this name when you map the DVD drive on the local computer in step d of the next section.

    3. Click Permissions. You need at least "read" permission for the user who will be accessing it to install Oracle Database.

    4. Click OK when you are finished.

  5. Insert the DVD labeled Oracle Database 11g Release 2 (11.2) into the DVD drive.

3.2.1.2 Step 2: On the Local Computer, Map the DVD Drive

Perform these steps on the local computer to map a remote DVD drive and to run Oracle Universal Installer from the mapped drive:

  1. Map the remote DVD drive.

    1. Start Windows Explorer on the local computer.

    2. From the Tools menu, select Map Network Drive to display the Map Network Drive dialog.

    3. Select a drive letter to use for the remote DVD drive.

    4. In Folder, enter the location of the remote DVD drive using the following format:

      \\remote_hostname\share_name

      where:

      • remote_hostname is the name of the remote computer with the DVD drive.

      • share_name is the share name that you entered in step 4 of the previous procedure. For example

        \\computer2\dvd

    5. If you need to connect to the remote computer as a different user, click different user name, and enter the username.

    6. Click Finish.

  2. Run Oracle Universal Installer from the mapped DVD drive.

  3. Go to the "Installing the Oracle Database Client Software" section.

3.2.2 Installing on Remote Computers Through Remote Access Software

If you want to install and run Oracle Database Client on a remote computer (that is, the remote computer has the hard drive and will run Oracle Database Client components), but you do not have physical access to the computer, you still can perform the installation on the remote computer if it is running remote access software such as VNC or Symantec pcAnywhere. You also need the remote access software running on your local computer.

You can install Oracle Database Client on the remote computer in one of two ways:

  • If you have copied the contents of the Oracle Database Client DVD to a hard drive, you can install from the hard drive.

  • You can insert the DVD into a drive on your local computer, and install from the DVD.

3.2.2.1 Installing on Remote Computers from a Hard Drive

If you have copied the contents of the Oracle Database Client DVD to a hard drive, you can install from the hard drive.

The steps that must complete are:

  1. Make sure that the remote access software is installed and running on the remote and local computers.

  2. Share the hard drive that contains the Oracle Database Client DVD.

  3. On the remote computer, map a drive letter to the shared hard drive. You would use the remote access software to do this on the remote computer.

  4. Through the remote access software, run Oracle Universal Installer on the remote computer. You access Oracle Universal Installer from the shared hard drive.

  5. Go to the "Installing the Oracle Database Client Software" section.

3.2.2.2 Installing on Remote Computers from a Remote DVD Drive

You can insert the DVD into a drive on your local computer, and install from the DVD.

The steps that you need to complete are:

  1. Make sure that the remote access software is installed and running on the remote and local computers.

  2. On the local computer, share the DVD drive.

    On the remote computer, map a drive letter to the shared DVD drive. You would use the remote access software to do this on the remote computer.

    These steps are described in the "Installing from a Remote DVD Drive" section.

  3. Through the remote access software, run Oracle Universal Installer on the remote computer. You access Oracle Universal Installer from the shared DVD drive.

  4. Go to Section 3.3, "Installing the Oracle Database Client Software."

3.2.3 Downloading Oracle Software

You can download the trial version of the installation files from the Oracle Technology Network (OTN) or Oracle Software Delivery Cloud Web site and extract them on your hard disk. Make sure that you completely review and understand the terms of the license. Most downloads include the Development License. This section contains the following topics:

3.2.3.1 Downloading the Installation Archive Files from OTN

To download the installation archive files from Oracle Technology Network:

  1. Use any browser to access the software download page from Oracle Technology Network:

    http://www.oracle.com/technetwork/indexes/downloads/index.html

  2. Navigate to the download page for the product that you want to install.

  3. On the download page, identify the required disk space by adding the file sizes for each required file.

    The file sizes are listed next to the filenames.

  4. Select a file system with enough free space to store and expand the archive files.

    In most cases, the available disk space must be at least twice the size of all the archive files.

  5. On the file system that you selected in step 4, create a parent directory for each product, for example OraDBClient11g, to hold the installation directories.

  6. Download all of the installation archive files to the directories that you created in step 5.

  7. Verify that the files you downloaded are the same size as the corresponding files on Oracle Technology Network.

  8. Extract the files in each directory that you just created.

  9. After you have extracted the required installation files, see the "Installing the Oracle Database Client Software" section.

3.2.3.2 Downloading the Software from Oracle Software Delivery Cloud

You can download the software from Oracle Software Delivery Cloud as Media Packs. A Media Pack is an electronic version of the software that is also available to Oracle customers on CD-ROM or DVD. To download the Media Pack:

  1. Use any browser to access the Oracle Software Delivery Cloud Web site:

    http://edelivery.oracle.com/

  2. Complete the Export Validation process by entering information (name, company, e-mail address, and country) in the online form.

  3. In the Media Pack Search page, specify the Product Pack and Platform to identify the Media Pack you want to download. If you do not know the name of the Product Pack, you can search for it using the License List.

  4. In the search results page, click Readme to download and review the Readme file for download instructions and product information.

  5. After you review the Readme, choose the appropriate Media Pack from the search results to download the individual zip files. Follow the Download Notes instructions in this page. Once you download and extract the contents of the required zip files, proceed with the installation of the software.


Note:

Print the page with the list of downloadable files. It contains a list of part numbers and their corresponding descriptions that you may need to refer during the installation process.


See Also:

Frequently Asked Questions section on the Oracle Software Delivery Cloud Web site for more information about Media Packs

3.2.3.3 Extracting the Installation Files

To extract the installation archive files, perform the following steps:

  1. If necessary, change to the directory that contains the downloaded installation archive files.

  2. Use GUI tool, like 7-Zip, to extract the installation files.

    When you have extracted all of the required installation files, see "Installing the Oracle Database Client Software" section .

3.2.4 Copying the Oracle Database Client Software to a Hard Disk

To copy the contents of the media to a hard disk:

  1. Create a directory for the installation files on your hard drive. For example:

    d:\install\client

  2. Copy the contents of the installation media to the directory that you just created.

When you have copied the required installation files, see the "Installing the Oracle Database Client Software" section.

3.3 Installing the Oracle Database Client Software

This section covers the following topics:

3.3.1 Guidelines for Installing Oracle Database Client

In most cases, you use the graphical user interface (GUI) provided by Oracle Universal Installer to install Oracle Database Client. However, you can also use Oracle Universal Installer to complete silent or noninteractive installations using a response file, without using the GUI. This method is particularly useful if you need to perform multiple installations of Oracle Database Client.

As you install Oracle Database Client, follow these guidelines:


See Also:

Appendix B, "Installing Oracle Database Client Using Response Files" for information about silent or noninteractive installations

  • Do not use Oracle Universal Installer from an earlier Oracle product release to install components from this release.

  • Use the same installation media to install Oracle Database Client on all supported Windows platforms.

  • If you reinstall Oracle software into an Oracle home directory where Oracle Database Client is already installed, you must reinstall any components that were installed before you began the reinstallation.

  • Do not modify the Java Runtime Environment (JRE) except by using a patch provided by Oracle Support Services. Oracle Universal Installer automatically installs the Oracle-supplied version of the JRE. This version is required to run Oracle Universal Installer and several Oracle assistants.

  • If you encounter errors during installation, click Help or see Appendix D, "Troubleshooting the Oracle Database Client Installation" for advice.

  • Products not installed by default, in case of Custom installation:

    • Oracle Connection Manager

    • Oracle Net Listener

    • Oracle Scheduler Agent

    • Oracle Services for Microsoft Transaction Server

    • Oracle Counters for Windows Performance Monitor

3.3.2 Procedure for Installing Oracle Database Client

Use Oracle Universal Installer to install the Oracle Database Client software.

To install Oracle Database Client perform the following steps:

  1. Log on as a member of the Administrators group to the computer to install Oracle components.

    If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.

  2. Insert the Oracle Database Client installation media and navigate to the client directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.

    Use the same installation media to install Oracle Database on all supported Windows platforms.

  3. Double-click setup.exe to start Oracle Universal Installer.

    Starting with Oracle Database 11g Release 2 (11.2.0.2), if you plan to run the installation in a secured data center, then you can download updates before starting the installation by starting Oracle Universal Installer on a system that has Internet access in update download mode. To start Oracle Universal Installer to download updates, enter the following command:

    ./setup.exe -downloadUpdates

    Provide the My Oracle Support user name and password, and provide proxy settings if needed on the Provide My Oracle Support credentials screen. Then, enter the Download location and click Download on the Download software updates screen. If updates are available, then they are downloaded in the location provided. The Finish Updates screen shows the successful download of the updates. Click Close.

    After you download updates, transfer the update file to a directory on the server where you plan to run the installation.


    See Also:


  4. If you have an existing Oracle Database Client 11g Release 2 (11.2) installed on your system, the Select Installation Mode screen is displayed. Select New Install to install Oracle Database Client software in to a new location.

    Starting with Oracle Database 11g Rel;Fease 2 (11.2.0.2), if you want to upgrade an earlier release of Oracle Database Client, then select Upgrade and follow the instructions in "Performing an In-place Oracle Database Client Upgrade"

  5. In the Select Installation Type screen, select the type of installation that you want: Instant Client, Administrator, Runtime, or Custom and click Next.

  6. Starting with Oracle Database 11g Release 2 (11.2.0.2), you can use the Software Updates feature to dynamically download and apply latest updates. In the Download Software Updates screen, select one of the following options, and click Next:

    • Use My Oracle Support credentials for download to download and apply the latest software updates.

      Click Proxy Settings to configure a proxy for Oracle Universal Installer to use to connect to the Internet. Provide the proxy server information for your site, along with a user account that has access to the local area network through which the server is connecting. Starting with Oracle Database 11g Release 2 (11.2.0.3), you can enter the Proxy Realm information. The proxy realm information is case-sensitive. If you do not have a proxy realm, then you do not need to provide an entry for the Proxy Username, Proxy Password, and Proxy Realm fields.

      Click Test Connection to ensure that your proxy settings are correctly entered, and the installer can download the updates.

    • Use pre-downloaded software updates to apply previously downloaded software updates.

    • Skip software updates if you do not want to apply any updates.

  7. The Apply Software Updates screen is displayed if you select to download the software updates or provide the pre-downloaded software downloads location. If you selected Use My Oracle Support credentials for download in the previous screen, then select Download and apply all updates, and click Next. If you selected Use pre-downloaded software updates, then select Apply all updates, and click Next.

  8. The Select Product Languages screen enables you to select the language in which you want to run the product.

    Select the product language from the Available Languages list, transfer it to the Selected Languages list. Click Next.

    This screen is not displayed if you select Instant Client as the type of installation in step 5.

  9. In the Specify Installation Location screen, enter the following details:

    Oracle Base: This path appears by default. You can change the path based on your requirement.

    The Oracle Base section is not displayed if you select Instant Client as the type of installation in step 5.

    In the Software Location section, accept the default value or enter the Oracle home directory path in which you want to install Oracle components. The directory path should not contain spaces. Click Next.

  10. If you selected Custom as the type of installation in step 5, then the Available Product Components screen is displayed. Select the products that you want to install and click Next.

  11. In step 10, if you select Oracle Scheduler Agent as one of the components that you want to install, then the Oracle Database Scheduler Agent screen is displayed. Enter the Scheduler Agent Host Name, and the Scheduler Agent Port Number. Click Next.

  12. The Perform Prerequisite Checks screen verifies if your computer meets the minimum system requirements to install the desired product. Click Next.


    Note:

    Oracle recommends that you use caution in checking the Ignore All option. If you check this option, then Oracle Universal Installer may not confirm that your system is able to install Oracle Database successfully.

  13. Review the information displayed in the Summary screen, and click Install.


    Note:

    Starting with Oracle Database 11g Release 2 (11.2), you can save all the installation steps into a response file by clicking Save Response File. Later, this file can be used for a silent installation.

  14. The Install Product screen shows the progress of a client installation. After Oracle Database Client is installed, click OK.

  15. If you are performing a Custom installation, and selected Oracle Net Listener from the list of components to install in step 10, then go to "Using Oracle Net Configuration Assistant" for instructions.

  16. In the Finish screen, click Close to exit Oracle Universal Installer.

Using Oracle Net Configuration Assistant

During a Custom Oracle Database Client installation, if you select Oracle Net Listener from the list of components to install in step 10, then Oracle Universal Installer automatically starts Oracle Net Configuration Assistant as part of the Oracle Database Client installation. Perform the following to configure the listener and naming methods using Oracle Net Configuration Assistant:

  1. In the Welcome screen, click Next.

  2. In the Listener Configuration screen, enter a Listener name or accept the default value. Click Next.

  3. In the Listener Configuration, Select Protocol screen, select one or more protocols from the Available Protocols list, and move it to the Selected Protocols list. Click Next.

  4. In the Listener Configuration, TCP/IP Protocol screen, select the standard port number, or enter a different port number. Click Next.

  5. Select No if you do not want to configure an additional listener, and click Next.

  6. The listener configuration is now complete, click Next to proceed.

  7. In the Naming Methods Configuration screen, select Yes to configure naming methods. Click Next.

  8. In the Naming Methods Configuration screen, select the naming method you want from the list of Available Naming Methods and then click Next.

    Typically, Local Naming is sufficient.

  9. In the Net Service Name Configuration screen, enter Service Name, and click Next.

  10. In the Net Service Name Configuration screen, select the protocol for the database you want to access, and click Next.

  11. In the Net Service Name Configuration screen, enter the Host name of the computer where the Oracle database is installed. Use the standard port number, or specify a different port number, and click Next.

  12. In the Net Service Name Configuration, Test screen, click Yes to test the database connection. Click Next.

    In most cases, the test fails only because the default user name and password Oracle Universal Installer supplies in the dialog box do not match the user name and password for the target database. Click Change Login, reenter the user name and password, and then click OK.

  13. In the Connecting screen, click Next.

  14. In the Net Service Name screen, enter the name of the Net Service Name, and click Next.

  15. Answer the remaining prompts to complete the configuration.

  16. In the Finish screen, click Close, to exit from Oracle Universal Installer.

You can also run Oracle Net Configuration Assistant after the installation in standalone mode to configure the listener, naming methods, net service names, and directory server usage.

To start Oracle Net Configuration Assistant in standalone mode, select Programs from the Start menu, and then select Oracle - HOME_NAME. Next, select Configuration and Migration Tools, and then Oracle Net Configuration Assistant.


See Also:

"Using Oracle Net Configuration Assistant to Configure Network Components" in Oracle Database Net Services Administrator's Guide

3.3.3 Performing an In-place Oracle Database Client Upgrade

Starting with Oracle Database 11g Release 2 (11.2.0.2) you can perform an in-place upgrade of Oracle Database Client 11g Release 2 (11.2) using the following instructions:


Note:

You can perform an in-place Oracle Database Client upgrade only if you have an existing Oracle Database Client 11g Release 2 (11.2.0.1) or later client home installed on your system.

  1. Perform Steps 1 through 3 listed in "Procedure for Installing Oracle Database Client".

  2. The Select Installation Mode screen is displayed only if you have an existing Oracle Database Client 11g Release 2 (11.2.0.1) or later installed on your system, . Select Upgrade to upgrade the existing Oracle Database Client software to the latest version.

  3. In the Specify Installation Location screen, accept the default Software Location value or enter the Oracle home directory path in which you want to install Oracle components. The directory path should not contain spaces. Click Next.

  4. In the Download Software Updates screen, select one of the following options, and click Next:

    • Use My Oracle Support credentials for download

    • Use pre-downloaded software updates

    • Skip software updates

    See Step 6 in "Procedure for Installing Oracle Database Client" for more information about the options in the Download Software Updates screen.

  5. The Apply Software Updates screen is displayed if you select to download the software updates or provide the pre-downloaded software updates location. Select either Download and apply all updates or Apply all updates, as applicable, and click Next.

    See Step 7 in "Procedure for Installing Oracle Database Client" for more information about the options in the Apply Software Updates screen.

  6. The Select Product Languages screen enables you to select the language in which you want to run the product.

    Select the product language from the Available Languages list, transfer it to the Selected Languages list. Click Next.

  7. The Perform Prerequisite Checks screen verifies if your computer meets the minimum system requirements to install the desired product. Click Next.

  8. Review the information displayed in the Summary screen, and click Install.

  9. The Install Product screen displays the progress of the client upgrade.

  10. Review the information in the Finish screen and click Close to exit Oracle Universal Installer.


See Also:


PK 9 ûPKAA OEBPS/ts.htm46 Troubleshooting the Oracle Database Client Installation

D Troubleshooting the Oracle Database Client Installation

This appendix contains the following information about troubleshooting:

D.1 Verifying Requirements

Before you try any of the troubleshooting steps in this appendix, do the following:

D.2 What to Do if an Installation Error Occurs?

If you encounter an error during installation:

D.3 Reviewing the Log of an Installation Session

When you run Oracle Universal Installer on a computer with no Oracle software installed, it creates a directory called:

DRIVE_LETTER:\Program Files\Oracle\Inventory\logs

During this first installation and all subsequent installations, Oracle Universal Installer saves all of the actions that it performs in a log file in this directory. If you encounter problems during the installation, review the log file for information about possible causes of the problem.

Log filenames for interactive installations take the form:

installActionsdate_time.log

oraInstalldate_time.err
oraInstalldate_time.out

For example, if an interactive installation occurred at 9:00:56 A.M. on February 14, 2005, the log file would be named:

installActions2005-02-14_09-00-56-am.log

Note:

Do not delete or manually alter the Inventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system.


See Also:

"Silent or Noninteractive Installation Response File Error Handling"

D.4 Silent or Noninteractive Installation Response File Error Handling

To determine whether a silent or nonintereactive installation succeeds or fails, check the silentInstallActionsdate_time.log file, located in the DRIVE_LETTER:\Program Files\Oracle\Inventory\logs directory.

A silent installation fails if:

Oracle Universal Installer or a configuration assistant validates the response file at run time. If the validation fails, the installation or configuration process ends.


See Also:

"Reviewing the Log of an Installation Session" for information about interactive installation log files

D.5 Troubleshooting Configuration Assistants

To troubleshoot an installation error that occurs when a configuration assistant is running:

D.5.1 Configuration Assistant Failure

Oracle configuration assistant failures are noted at the bottom of the installation window. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the installActionsdate_time.log file.

The execution status codes are listed in the following table:

StatusResult Code
Configuration assistant succeeded0
Configuration assistant failed1
Configuration assistant canceled-1

D.5.2 Irrecoverable Errors

If you receive an irrecoverable error while a configuration assistant is running:

  1. Remove the failed installation as described in Section D.7, "Cleaning Up After a Failed Installation."

  2. Correct the cause of the irreoverable error.

  3. Reinstall the Oracle software.

D.6 Troubleshooting Inventory Issues

If you face any of the following situations for Oracle home, then run the opatch lsinventory -detail command to list the contents of the inventory and see section "Recovering from inventory corruption" in the Oracle Universal Installer and OPatch User's Guide for information about fixing the issue.

D.7 Cleaning Up After a Failed Installation

If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory. Follow the instructions in Chapter 5, "Removing Oracle Database Client Software" to run the Deinstallation tool.

PK09646PKAA OEBPS/toc.ncx 4 Oracle® Database Client Installation Guide for Microsoft Windows, 11g Release 2 (11.2) Cover Table of Contents Oracle Database Client Installation Guide 11g Release 2 (11.2) for Microsoft Windows Preface Oracle Database Client Installation Overview Oracle Database Client Preinstallation Requirements Installing Oracle Database Client Oracle Database Client Postinstallation Tasks Removing Oracle Database Client Software Installing Java Access Bridge Installing Oracle Database Client Using Response Files Configuring Oracle Database Globalization Support Troubleshooting the Oracle Database Client Installation Glossary Index Copyright PK PKAAOEBPS/content.opfa Oracle® Database Client Installation Guide for Microsoft Windows, 11g Release 2 (11.2) en-US E24187-05 Oracle Corporation Oracle Corporation Oracle® Database Client Installation Guide for Microsoft Windows, 11g Release 2 (11.2) 2012-05-02T18:10:13Z Describes how to install and configure Oracle Database Client on Windows. PKz&V%ȣOΏ9??:a"\fSrğjAsKJ:nOzO=}E1-I)3(QEQEQEQEQEQEQE֝Hza<["2"pO#f8M[RL(,?g93QSZ uy"lx4h`O!LŏʨXZvq& c՚]+: ǵ@+J]tQ]~[[eϸ (]6A&>ܫ~+כzmZ^(<57KsHf妬Ϧmnẁ&F!:-`b\/(tF*Bֳ ~V{WxxfCnMvF=;5_,6%S>}cQQjsOO5=)Ot [W9 /{^tyNg#ЄGsֿ1-4ooTZ?K Gc+oyڙoNuh^iSo5{\ܹ3Yos}$.nQ-~n,-zr~-|K4R"8a{]^;I<ȤL5"EԤP7_j>OoK;*U.at*K[fym3ii^#wcC'IIkIp$󿉵|CtĈpW¹l{9>⪦׺*ͯj.LfGߍԁw] |WW18>w.ӯ! VӃ :#1~ +މ=;5c__b@W@ +^]ևՃ7 n&g2I8Lw7uҭ$"&"b eZ":8)D'%{}5{; w]iu;_dLʳ4R-,2H6>½HLKܹR ~foZKZ࿷1[oZ7׫Z7R¢?«'y?A}C_iG5s_~^ J5?œ tp]X/c'r%eܺA|4ծ-Ե+ْe1M38Ǯ `|Kյ OVڅu;"d56, X5kYR<̭CiطXԮ];Oy)OcWj֩}=܅s۸QZ*<~%뺃ȶp f~Bðzb\ݳzW*y{=[ C/Ak oXCkt_s}{'y?AmCjޓ{ WRV7r. g~Q"7&͹+c<=,dJ1V߁=T)TR՜*N4 ^Bڥ%B+=@fE5ka}ędܤFH^i1k\Sgdk> ֤aOM\_\T)8靠㡮3ģR: jj,pk/K!t,=ϯZ6(((((((49 xn_kLk&f9sK`zx{{y8H 8b4>ÇНE|7v(z/]k7IxM}8!ycZRQ pKVr(RPEr?^}'ðh{x+ՀLW154cK@Ng C)rr9+c:׹b Жf*s^ fKS7^} *{zq_@8# pF~ [VPe(nw0MW=3#kȵz晨cy PpG#W:%drMh]3HH<\]ԁ|_W HHҡb}P>k {ZErxMX@8C&qskLۙOnO^sCk7ql2XCw5VG.S~H8=(s1~cV5z %v|U2QF=NoW]ո?<`~׮}=ӬfԵ,=;"~Iy7K#g{ñJ?5$y` zz@-~m7mG宝Gٱ>G&K#]؃y1$$t>wqjstX.b̐{Wej)Dxfc:8)=$y|L`xV8ߙ~E)HkwW$J0uʟk>6Sgp~;4֌W+חc"=|ř9bc5> *rg {~cj1rnI#G|8v4wĿhFb><^ pJLm[Dl1;Vx5IZ:1*p)إ1ZbAK(1ׅ|S&5{^ KG^5r>;X׻K^? s fk^8O/"J)3K]N)iL?5!ƾq:G_=X- i,vi2N3 |03Qas ! 7}kZU781M,->e;@Qz T(GK(ah(((((((Y[×j2F}o־oYYq $+]%$ v^rϭ`nax,ZEuWSܽ,g%~"MrsrY~Ҿ"Fت;8{ѰxYEfP^;WPwqbB:c?zp<7;SBfZ)dϛ; 7s^>}⍱x?Bix^#hf,*P9S{w[]GF?1Z_nG~]kk)9Sc5Ո<<6J-ϛ}xUi>ux#ţc'{ᛲq?Oo?x&mѱ'#^t)ϲbb0 F«kIVmVsv@}kҡ!ˍUTtxO̧]ORb|2yԵk܊{sPIc_?ħ:Ig)=Z~' "\M2VSSMyLsl⺿U~"C7\hz_ Rs$~? TAi<lO*>U}+'f>7_K N s8g1^CeКÿE ;{+Y\ O5|Y{/o+ LVcO;7Zx-Ek&dpzbӱ+TaB0gNy׭ 3^c T\$⫫?F33?t._Q~Nln:U/Ceb1-im WʸQM+VpafR3d׫é|Aү-q*I P7:y&]hX^Fbtpܩ?|Wu󭏤ʫxJ3ߴm"(uqA}j.+?S wV ~ [B&<^U?rϜ_OH\'.;|.%pw/ZZG'1j(#0UT` Wzw}>_*9m>󑓀F?EL3"zpubzΕ$+0܉&3zڶ+jyr1QE ( ( ( ( ( ( ( (UIdC0EZm+]Y6^![ ԯsmܶ捆?+me+ZE29)B[;я*wGxsK7;5w)}gH~.Ɣx?X\ߚ}A@tQ(:ͧ|Iq(CT?v[sKG+*רqҍck <#Ljα5݈`8cXP6T5i.K!xX*p&ќZǓϘ7 *oƽ:wlຈ:Q5yIEA/2*2jAҐe}k%K$N9R2?7ýKMV!{W9\PA+c4w` Wx=Ze\X{}yXI Ү!aOÎ{]Qx)#D@9E:*NJ}b|Z>_k7:d$z >&Vv󃏽WlR:RqJfGإd9Tm(ҝEtO}1O[xxEYt8,3v bFF )ǙrPNE8=O#V*Cc𹾾&l&cmCh<.P{ʦ&ۣY+Gxs~k5$> ӥPquŽўZt~Tl>Q.g> %k#ú:Kn'&{[yWQGqF}AЅ׮/}<;VYZa$wQg!$;_ $NKS}“_{MY|w7G!"\JtRy+贾d|o/;5jz_6fHwk<ѰJ#]kAȎ J =YNu%dxRwwbEQEQEQEQEQEQEQEQEQE'fLQZ(1F)hQ@X1KEQE-Q@ 1KE3h=iPb(((1GjZ(-ʹRPbR@ 1KE7`bڒyS0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((?l:ϊw "{{-3j3%{sj~2= 7 ~MڅKrHb|P3 r=Ҁ +Ş/$iu7=q2dԂxn⸷9$l]H #WI񯄴;\[ݚD8C3p&0U9^AnK vI+!I8>5(zqj03Y.X ,@85ߛ8>pq8=} \xmm常8` $Q@$v7zwp]ɝA GX;y_]覮O&4 SPtY.X),@84U=7Vuv K4,$g{@<+uqtiGw3; I@ORմn5MBp%8'ƫ%u6uBJrHRN2@ϸ J(9i[[mɿ{=8lxmm常8` $Q@$v7zwp]ɝA GU[;jvzg+d!q`rx+G%!m˹@ݎP|YN;;iWwRgd0^#' N'((((((((((((((((((PTz k㯆 jlI#TQ-$sONC^8 5w(x&eyȹ_Cdv$w Yͨ#,䳞B(cY8 :~.jo|rYp&oD,"p,bCTsĸ&~ jzR"[YGl Q98n@;ĺ:]9ƽhOxgXHuVn7cxub;Qa9*?i>姙?ɜs|?~z, hɅaC12c;3g? h|Jdg5@C5|F_$|<7¾d]Iɔ$0GUp&];_u"iZ{27v:+4:[zޛ}:v%`$)' gPYsZyn#i1A@R,ɍ)ey>y⻿zMZN HR8XN 2 O\H9&|^E4(E(F@Pi~sQ`~xq zƧyצ-Q\|yBI=_] z[ln[np38%MBTxl,"#n$%n$o_*q$~xoULInTty d1 i0Fy OŞ5ƺ-k)-U,7y/|CO -I1$r@eTfo <!~$kz\w,qq| Ff8#$2ǃ`ğR"6+(YFv4Ԏ0'{Xi wB,b>#xmGKtQn,o\2[aP<@$/EXQ1h_mዘ!VWc|9,F {Q|o{oiKx NB 0AӠ MK[^$y?g1w7|o? 7QiyepȖe"7JKݎv`6cn.>'m]f/_[A('8l+.8An _KUQ}Q(ɐXob_ 8Ғ7и#y=zPkRM'ž$EZr2D[>cGVٺ`Ix;ʥ؆wrk(2xΝ?lnu_?;{15'yo %Β^W q#YqWw Z/.`е}wkx U~;rw?±k,x#CfӲ;Gr N@S7[~wmsnݳ}8q ryR7I 8#Ҹ? 4oB]7~Y8bYe Jp8._6ZirWHřXLKsQCI@O!{ᗒ MjsY;"hѾm`|6p#\M;?_?L߽qz%O?h&ͫq𶡬ϡZ"wsѳۍ򯙹bSz?|a}-9/rQEr3Ih>"x>Եؓ(wJrJmgºFpPH3bI85$DaIdLML(X*lrI#na?ßu~kq&n[ °?6⺏1񷁡VpGP`n ;£FP: *O꽂?t>T w5h&&psw&AV;Sٜ2OBQ_?²Yo;7o׵>Tlv]}zǨ_w##\NI&44Wu,),D' wcnty_2i_ ԆadH'XN?x?wWiz\sA-\3]:*Tc;z?'Gu\G.nog9]x$P**_>&k?Zyzਖ਼*h9b̛X"6|61@ExY!ku5DDn1mD*00b#3|u)[uZUյBrt|(>2,C%jȪpI;w˿^F#瑶q]x(*?mGZǏ-xwQ-Ʊ:QX`\|P6=qyVOW!/l|j8dIM c¨8lȱ8tj2  z{}|S+ZVպZ>Y:@/>+|Ug.[lb3Iiby]ǁ~hs}7ۼ3n=sڼSUMeޤt&F?n5ܓ\hLD m¬eiPQ^'|ovf}j<:F[] R  $/ut jޡ}Q<2KXDݴUMB"8l⅞z喇w%Ƙ ٧˞6!J#x+MFj>qe+l>T3GSW}g I2(]HXcps,{Y.)9#6 0 x珱|iyKƹ(G#^e_G6my:F./7c$(''+>O ß * 2 #08Gb]|խDWnF8;W|mfUK[= jU*򛊌gs׾(xoZhLxDK381g?ß}ʷUz"38?$  KKb)q ,'$ ZFaZ0 TUljEEG(*?mw V=m/Kh%kkV`Up6aoZ<77λYOw$.VgR۝P@̇=p~!nK?]]HյL$ƍ˴yFQOj/|xNݍBEHeЎ i~.5xZ8 p $D߂ :e=ܓWhYJnvaA2'<xN[=j&F)$,I PK6[ª;$HIaY?TU|V}lXoV0 Uwt*A9x+M6w455ӫ0bUF0|࿇~5? xU|CiwDʑCrh_,Ȅry}?L\m-c4\Xǁ@kßx{i$p8a׆'5鿳,n[jP*-Pu'<z'-{3󭦟HL+"@TP0%x|'`?^j Z[4?d1tb8UxZm4K=,-ͼQTXmx?x!(T)$r(eu#x 1@E|5iXID.ۀr 끑8"Ɨ?дc@7w R%7H[?jDnUXI!][o\ap+9p6s%ܟuK4;<|f@@ϧ^kWټg;=Fh"w)A)Jc:Ҋ~-;:w5^mFqR ;59ȏ৊ux6\]z¯$xAd ΀="Ė5mrW|=shZ}F,Fs{((((((x.x}MK恎jnȻKwuhRյ/[SPd:EfVCc'}Q^o:ς\/6ڦYyH~Ԅ{PQE|>0):h|*;S 9Es7PJHh}E xYwo/ϵG<*RG@:(:}7×~&Ҵ;[= &U2$\>OPx'}q7C̺5,p8$(((((((((((PTzbo|i<%,ǥHڎ %*(N@ϒ8OPTzA־Ѡ\j=+xKI4LFm!J +h>M/Dd%M$wԟC²訫s߅=.ƭpחFtY$#pg'dQP VԦ|O˨]L$mgϭh|P߆Bbk" 2COR !8R|Y`ZxRV%Z ˨ ʬ[$aWό{$? |}xS[Jheh?w8 8]_ufu(נ/-, o G]s;y_]覠&_MEpF1;>3r3]|Ky᝔jzJbf˗fu2nڨv1)և/$:Drg#O52 RV'2(=j-GYikKEo.#\ڸy=NO4ѵ4oqU@ǡP۰APxn⸷9$l]H #׍x!lHdTstB:h~'e1VdvBX\W1V^lom"]p \[i y?0⿅nH7r^XL,!F b\ҼA3?Y5ZvYU8 a@_>8 :T) VվElbKkc¯!ZϲOy{f7q_׉Ϗ<2KFPɕXH¯$'+(_7-Gx$iV_怯ˬ+FSyƕMz.qAZ,͝HozN7?1<2;E3RT ʷ!v8*LJ|Y`Z>2?X|_VE8|K!3&9`GМ+YjZ"[w0Zja-fu|P0=aLmbIaY?TTs4Ԭ7OxOMе2ʠq$0P VxB×E1%De9,PfT~;F<1w,qkVZ=`YT*FH#A8gc㾫ce8$JJG' u  Y W}%lBU8g@;44 ߋ價[+}1v;dV{1ln5ٖmc$]b7E#}Xk[ t)l?fd$nI"P8 3SGмQǬxoR}7*I_+oG/pWzEx]x|5xME,Rm( 0PE0 aX{QEC²訫+g'dQPWmCۿG^^InQtyZ襬^1i_uVOPHg-?3 [yZ襯??4W*~^^'( ~IW}kn .$,>͹ !Q¿RXx;}0lD#B<[+H׸A<7V\[J6 dGk_ۘLؓGʱO`8=FG4QEQEQEQEQEQEQEQEQEQEq0/%~!ƭ_;^F?獶p]P\Ï¿Ɠ:|#Qn773Š↭O3Bmcn߻]6lj1CHmYxxtt=ddA Q@7={NCkKl4v0["bqʠy!FNNkES;:>_3Wtw'ݎC[4:,gEv 9R (Jk}sMM]ܤcŽ~мg<4~F|̉F[ivP\Ï¿Ɠ:|#Qn773Š#$u[mK `!LYXl`t&~.arߋu-SXt[_]+:۠ul.K9||{%i؞4; Vnݻ ]qdכ|IW1ϏA">V?1oPGFauKSB3w+ +' }ьt^_Gw@'prFvS+b8w_Bn^K((¦8%{O>3񭞿=v"DvkF$:J (2+}IJCχw-#x|%֢:Q; lr@,(c;J+Νm@k:UEBB]0NO˞'9ᯎ^kZ=ǑxIgoH 8o7|C7zMc S^^?:*?ֺψ=_ivki%NTf[ /9b@Ҋs|xPΕe#otАLS2kk:tvZ֏q^,1Y(GyEyn>'j#)ZlƩxجʠ|!15xw#S{wRX#Gr Es)ew`n$!&US i,0z7O^(ӭ=wCҭoI؄ ?0rv= ?og?KL_ c~EuO~=_Uy_Vqܠm_q+]gZD?(@B#n9 8$NX"{ok S@+U' u3:&XAF~bb:WI^?;*/ѤP~`0sm0F>|gXO{.5kcڨ!qA;sW7x/_ھͲA9X&BX.v.~qPƺ<+ujZC]%IJCz߂/xڥޛ3 FzWy@WWww]焵zLJX >@>Rwe*X `$O7J]t;4"mɒ qr+VkfZ$Ϳuki^t;XdCmT9:. _*<.^q+p|sC+s>~QO=6{#njX1lǴ@ 8|!MCga6kH݄R]YK y鹱]ǃ|!}ọRV޹j<TD7H r{Nş AV// ˡ_O׀|nL`X _Q]J. g:}yecmОׁthfyWnr{U8^@ {z_Go:|Uw{Rf=Xǵgj;ZF"wXX.sM͎ < jڷCPt4hʢ&NѺG8@c?k6I4 CX%hC$ )auvn>$|?׼7SF4[ nn C>1?A_[J[JsÃ|]=XIu^j'ajRu,U%w!2HΕc|(дN;;%0G Fo&J wWݼ;mN s]Ğᕗ$!yh1MBqGw-/IՌ濋36y;G!Hs: O^3|K'.m 4D2$B0A+>i_&ѵ+? xMҒ1礻Te19PvQ׭=l^}_7,S]HB&( _3cP|* x:3rՉmqY\IǿƭONv%O 偹"# 7yiIukx;w$чjoU&־ ZY:gӭp`@ʤEG\ 'MFѬtv6QBp ~yxU^^W=v8?$ ž7Xӧ񽝭:B oݘ0̙#{ƩK\ƾ5Hћ(ySy$ +C~W<-oxr{O.pE:lW%OkX=R5vdfd|x8 P]Hcx2B;FGBEt|sC+Mj'_қnYqs=bLӮo$mby}EҼƽ8]k26i*QSY*( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ()N[X]bR$(8gU((((( zw]ɍ<RA6[0D#5 `*J(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((PKb1{ {PKAAOEBPS/dcommon/contbig.gif`GIF87a!!!111999BBBJJJRRRccckkksss{{{skk{{ZRRRJJƽ{sZRJRJB91)kcZB9)sskZRJ1޽ƽ{{ssskkkcƵZZRccZRRJJJB{BB9991ssckkZccR))!RRB!!JJ1))99!11ƌ)1R)k֔)s1RZJR{BJs9R1J!11J1J9k{csZk!1J!)cBR9J1B)91B!cRs{!)s!){1B!k!s!{ksksckckZc9B)1!)!)BJ9B1919έƌ!!)JJcZZ{!!!1RR{JJsBBkJJ{!!9BB{1!!J9)!!Z!!c1!!kR!!s9Z!BckJs)19!!c!!ZRZ,H rrxB(Kh" DժuICiи@S z$G3TTʖ&7!f b`D 0!A  k,>SO[!\ *_t  Exr%*_}!#U #4 & ֩3|b]L ]t b+Da&R_2lEٱZ`aC)/яmvUkS r(-iPE Vv_{z GLt\2s!F A#葡JY r|AA,hB}q|B`du }00(䡆<pb,G+oB C0p/x$…– ]7 @2HFc ) @AD \0 LHG',(A` `@SC)_" PH`}Y+_|1.K8pAKMA @?3҄$[JPA)+NH I ,@8G0/@R T,`pF8Ѓ)$^$ DDTDlA@ s;PKPKAAOEBPS/dcommon/darbbook.cssPKPKAA!OEBPS/dcommon/O_signature_clr.JPG"(JFIF``C    $.' ",#(7),01444'9=82<.342C  2!!22222222222222222222222222222222222222222222222222" }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz ?( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (?O '~MQ$Vz;OlJi8L%\]UFjޙ%ԯS;rA]5ފ<׈]j7Ouyq$z'TQuw7Ŀ KX߁M2=S'TQt?.5w'97;~pq=" ~k?`'9q6 E|yayM^Om'fkC&<5x' ?A?Zx'jß={=SßM gVC.5+Hd֪xc^)Җufz{Cީ|D Vkznq|+Xa+{50rx{|OG.OϞ~f/ xxX[2H )c+#jpUOZYX\=SG ߨC|K@;_߆'e?LT?]:?>w ڔ`D^So~xo[Ӡ3i7B:Q8 Vc-ďoi:FM292~y_*_闱YN\Fr=xZ3鳎OwW_QEzW~c]REeaSM}}Hӏ4&.E]u=gMѠ+mF`rNn$w9gMa꺢nTuhf2Xv>އ a(Û6߭?<=>z'TQuw7Ŀ KX߁M2=S'TQt?.5Kko\.8S$TOX߀Gw?Zx汴X)C7~.i6(Щ=+4{mGӭ¸-]&'t_kV*I<1)4thtIsqpQJ+> \m^[aJ5)ny:4o&QEnyAEPEEss 72,PDۢ׃K W{Wjr+wگ iM/;pd?~&?@;7E4gv8 $l'z'TQuw7Ŀ Gֱ=ɿ&G?. iR(5W*$|?w᫼gkmIbHe/_t>tg%y.l}N5[]+Mk0ĠeHdPrsst'UiC,y8`V%9ZIia|ܪvi מYG,o}+kk{YbyIeb*sAtի82zWoEK5z*o-eo;n(P u-I)4Š(HQEQEQEQEhz(X/Đ?}Bk˩ ݏrk0]4>8XzV? }6$}d^F>nU K ?Bտk_9׾x~w'ߞ  uDŽtL ؈5c-E/"|_Oo.IH쐍=i*Iw5(ںw?t5s.)+tQ2dUt5Vĺ.jZ"@IRrZƅY4ߡ_;}ų(KyQf1Aǵt?sZg+?F5_oQR&Dg߿]6FuRD u>ڿxl7?IT8'shj^=.=J1rj1Wl$얲cPx;E,p$֟ˏkw qg"45(ǛkV/=+ũ)bYl~K#˝J_כ5&\F'I#8/|wʾ_Xj Q:os^T1.M_|TO.;?_  jF?g N 8nA2F%i =qW,G=5OU u8]Rq?wr'˻S+۾.ܼ 87Q^elo/T*?L|ۚ<%<,/v_OKs B5f/29n0=zqQq(ª=VX@*J(э(f5qJN_EVǞQEOuoѕOuoa5}gO?:߂8Wא|cڽ~]N&O( (<]>͠@VQ=^~U ̴m&\խ5i:}|}r~9՝f}_>'vVֲ$~^f30^in{\_.O F8to}?${φ|#x^#^n~w=~k~?'KRtO.㌡h![3Zu*ٷճ(ԟ]z_/W1(ԟ]v~g|Yq<ז0 ; b8֮s,w9\?uEyStKaª@\,)) (!EPEPEPEPEPzѧts{v>C/"N6`d*J2gGӧWqBq_1ZuΓ\X]r?=Ey88Mp&pKtO-"wR2 K^-Z< \c>V0^@O7x2WFjs<׻kZ(<Т(OFw/6$1[:ޯԯ#q~4|,LVPem=@=YLUxӃV}AUbcUB.Ds5*kٸAeG>PJxt͝ b88?*$~@ׯD VkraiJs}Q.20x&mXξ,Z]“A-J#`+-E/"<]\a'tZGy.(|lދ~gMK OZdxDŽU9T6ϯ^<Ϡt5CZ]].t۫S=s`ڳ%8iVK:nqe+#<.T6U>zWoy3^I {F?J~=G}k)K$$;$de8*G Uӟ4Ocºw}|]4=ݣ\x$ʠms?q^ipw\"ȿPs^Z Q_0GڼU.t}ROM[G#]8wٞ ӫ87}Cgw vHȩBM55vof =A_٭`Ygx[6 P,5}>蚊(0(+?>+?> k|TuXq6_ +szk :u_ Z߶Ak_U}Jc2u/1[_»ݸG41-bሬ۴}}Eȹפ_c?5gi @cL\L<68hF_Ih>X4K7UТ sMj =J7CKo>Օ5s:߀t ~ηaٿ?|gdL8+gG%o?x`دOqȱwc¨&TW_V_aI=dpG!wu۞սZ1yL50$(l3(:~'ַo A}a3N*[0ǭ HKQV}G@֜$ 9of$ArNqUOgË05#m?D)^_h//5_/<?4}Jį+GkpG4"$ r| >S4Ђ"S 1%R:ȝ 8;PKPz PKAAOEBPS/dcommon/feedback.gif7GIF89a'%(hp|fdx?AN5:dfeDGHɾTdQc`g*6DC\?ؘ||{;=E6JUՄfeA= >@,4`H.|`a (Q 9:&[|ځ,4p Y&BDb,!2@, $wPA'ܠǃ@CO~/d.`I @8ArHx9H75j L 3B/` P#qD*s 3A:3,H70P,R@ p!(F oԥ D;"0 ,6QBRɄHhI@@VDLCk8@NBBL2&pClA?DAk%$`I2 #Q+l7 "=&dL&PRSLIP)PɼirqМ'N8[_}w;PK-PKAAOEBPS/dcommon/booklist.gifGIF89a1޵֥΄kZ{Jk1Rs!BZ)B),@I9Z͓Ca % Dz8Ȁ0FZЌ0P !x8!eL8aWȠFD(~@p+rMS|ӛR$ v "Z:]ZJJEc{*=AP  BiA ']j4$*   & 9q sMiO?jQ = , YFg4.778c&$c%9;PKː5PKAAOEBPS/dcommon/cpyr.htm1 Oracle Legal Notices

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2012, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in prerelease status:

This documentation is in prerelease status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Oracle Logo

PKN61PKAAOEBPS/dcommon/masterix.gif.GIF89a1ޜΌscJk1Rs!Bc1J),@IS@0"1 Ѿb$b08PbL,acr B@(fDn Jx11+\%1 p { display: none; } /* Class Selectors */ .ProductTitle { font-family: sans-serif; } .BookTitle { font-family: sans-serif; } .VersionNumber { font-family: sans-serif; } .PrintDate { font-family: sans-serif; font-size: small; } .PartNumber { font-family: sans-serif; font-size: small; } PKeӺ1,PKAAOEBPS/dcommon/larrow.gif#GIF87a絵ƌֵƽ{{ss֜ƔZZ{{{{ZZssZZccJJJJRRBBJJJJ991111))!!{,@pH,Ȥrl:ШtpHc`  өb[.64ꑈ53=Z]'yuLG*)g^!8C?-6(29K"Ĩ0Яl;U+K9^u2,@@ (\Ȱ Ë $P`lj 8x I$4H *(@͉0dа8tA  DсSP v"TUH PhP"Y1bxDǕ̧_=$I /& .)+ 60D)bB~=0#'& *D+l1MG CL1&+D`.1qVG ( "D2QL,p.;u. |r$p+5qBNl<TzB"\9e0u )@D,¹ 2@C~KU 'L6a9 /;<`P!D#Tal6XTYhn[p]݅ 7}B a&AƮe{EɲƮiEp#G}D#xTIzGFǂEc^q}) Y# (tۮNeGL*@/%UB:&k0{ &SdDnBQ^("@q #` @1B4i@ aNȅ@[\B >e007V[N(vpyFe Gb/&|aHZj@""~ӎ)t ? $ EQ.սJ$C,l]A `8A o B C?8cyA @Nz|`:`~7-G|yQ AqA6OzPbZ`>~#8=./edGA2nrBYR@ W h'j4p'!k 00 MT RNF6̙ m` (7%ꑀ;PKl-OJPKAAOEBPS/dcommon/index.gifGIF89a1޵ΥΥ{sc{BZs,@IM" AD B0 3.R~[D"0, ]ШpRNC  /& H&[%7TM/`vS+-+ q D go@" 4o'Uxcxcc&k/ qp zUm(UHDDJBGMԃ;PK(PKAAOEBPS/dcommon/bookbig.gif +GIF89a$!!!)))111999BBBJJJRRRZZZccckkksss{{{skkB991)))!!B11))1!JB9B9!!cZ9ƭƽssk{ZZRccZRRJJJBBB9c!!ν)1)k{s絽ƌkssֽZccJRRBJJ{9BB)11)99!!))11!!k!JZ!)RcJccBcs)1c)JZ!BR!)BZ)99J!Rk9!c11B)Z{)9Bkc1kB9BZ!Z{9Rs)Jkksk9kB1s1Jk9Rƥc{k9s)Z{1k91)s1Rk)Jc1J!))BZ!1k{csc{)19B!)Bcsc{ksc{kZs!RkJkJkքc{9Zks{ck9R)Bks9R9R1J!)Z1B!)c)9)99BR19kksBBJcc{ccBBZ))9kk!!199c11ZBB{9!!R!!Z!!c))!!kR!!s!!BcksRZ1c9B)R91c1)Z!R9B9k1)RcZ{)!1B9JB9B)!)J9B!& Imported from GIF image: bookbig.gif,$!!!)))111999BBBJJJRRRZZZccckkksss{{{skkB991)))!!B11))1!JB9B9!!cZ9ƭƽssk{ZZRccZRRJJJBBB9c!!ν)1)k{s絽ƌkssֽZccJRRBJJ{9BB)11)99!!))11!!k!JZ!)RcJccBcs)1c)JZ!BR!)BZ)99J!Rk9!c11B)Z{)9Bkc1kB9BZ!Z{9Rs)Jkksk9kB1s1Jk9Rƥc{k9s)Z{1k91)s1Rk)Jc1J!))BZ!1k{csc{)19B!)Bcsc{ksc{kZs!RkJkJkքc{9Zks{ck9R)Bks9R9R1J!)Z1B!)c)9)99BR19kksBBJcc{ccBBZ))9kk!!199c11ZBB{9!!R!!Z!!c))!!kR!!s!!BcksRZ1c9B)R91c1)Z!R9B9k1)RcZ{)!1B9JB9B)!)J9BH`\Ȑ:pظа"A6DBH,V@Dڹ'G"v Æ ܥ;n;!;>xAܽ[G.\rQC wr}BŊQ A9ᾑ#5Y0VȒj0l-GqF>ZpM rb ;=.ސW-WѻWo ha!}~ْ ; t 53 :\ 4PcD,0 4*_l0K3-`l.j!c Aa|2L4/1C`@@md;(H*80L0L(h*҇҆o#N84pC (xO@ A)J6rVlF r  fry†$r_pl5xhA+@A=F rGU a 1х4s&H Bdzt x#H%Rr (Ѐ7P`#Rщ'x" #0`@~i `HA'Tk?3!$`-A@1l"P LhʖRG&8A`0DcBH sq@AXB4@&yQhPAppxCQ(rBW00@DP1E?@lP1%T` 0 WB~nQ@;PKGC PKAAOEBPS/dcommon/rarrow.gif/GIF87a絵ƌֵƽ{{ss֜ƔZZ{{{{ZZssZZccJJJJRRBBJJJJ991111))!!{,@pH,Ȥrl:ШLlԸ NCqWEd)#34vwwpN|0yhX!'+-[F 'n5 H $/14w3% C .90" qF 7&E "D mnB|,c96) I @0BW{ᢦdN p!5"D`0 T 0-]ʜ$;PKJV^PKAAOEBPS/dcommon/mix.gifkGIF89aZZZBBBJJJkkk999sss!!!111cccֽ{{{RRR)))猌ƭ{s{sks!,@@pH,B$ 8 t:<8 *'ntPP DQ@rIBJLNPTVEMOQUWfj^!  hhG H  kCúk_a Ǥ^ h`B BeH mm  #F` I lpǎ,p B J\Y!T\(dǏ!Gdˆ R53ټ R;iʲ)G=@-xn.4Y BuU(*BL0PX v`[D! | >!/;xP` (Jj"M6 ;PK枰pkPKAAOEBPS/dcommon/doccd_epub.jsM /* Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2012.3.17 */ function addLoadEvent(func) { var oldOnload = window.onload; if (typeof(window.onload) != "function") window.onload = func; else window.onload = function() { oldOnload(); func(); } } function compactLists() { var lists = []; var ul = document.getElementsByTagName("ul"); for (var i = 0; i < ul.length; i++) lists.push(ul[i]); var ol = document.getElementsByTagName("ol"); for (var i = 0; i < ol.length; i++) lists.push(ol[i]); for (var i = 0; i < lists.length; i++) { var collapsible = true, c = []; var li = lists[i].getElementsByTagName("li"); for (var j = 0; j < li.length; j++) { var p = li[j].getElementsByTagName("p"); if (p.length > 1) collapsible = false; for (var k = 0; k < p.length; k++) { if ( getTextContent(p[k]).split(" ").length > 12 ) collapsible = false; c.push(p[k]); } } if (collapsible) { for (var j = 0; j < c.length; j++) { c[j].style.margin = "0"; } } } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(compactLists); function processIndex() { try { if (!/\/index.htm(?:|#.*)$/.test(window.location.href)) return false; } catch(e) {} var shortcut = []; lastPrefix = ""; var dd = document.getElementsByTagName("dd"); for (var i = 0; i < dd.length; i++) { if (dd[i].className != 'l1ix') continue; var prefix = getTextContent(dd[i]).substring(0, 2).toUpperCase(); if (!prefix.match(/^([A-Z0-9]{2})/)) continue; if (prefix == lastPrefix) continue; dd[i].id = prefix; var s = document.createElement("a"); s.href = "#" + prefix; s.appendChild(document.createTextNode(prefix)); shortcut.push(s); lastPrefix = prefix; } var h2 = document.getElementsByTagName("h2"); for (var i = 0; i < h2.length; i++) { var nav = document.createElement("div"); nav.style.position = "relative"; nav.style.top = "-1.5ex"; nav.style.left = "1.5em"; nav.style.width = "90%"; while (shortcut[0] && shortcut[0].toString().charAt(shortcut[0].toString().length - 2) == getTextContent(h2[i])) { nav.appendChild(shortcut.shift()); nav.appendChild(document.createTextNode("\u00A0 ")); } h2[i].parentNode.insertBefore(nav, h2[i].nextSibling); } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(processIndex); PKo"nR M PKAAOEBPS/dcommon/toc.gifGIF89a1ΥΥ{c{Z{JkJk1Rk,@IK% 0| eJB,K-1i']Bt9dz0&pZ1o'q(؟dQ=3S SZC8db f&3v2@VPsuk2Gsiw`"IzE%< C !.hC IQ 3o?39T ҍ;PKv I PKAAOEBPS/dcommon/topnav.gifGIF89a1ֽ筽ޭƔkZZk{Bc{,@ ) l)-'KR$&84 SI) XF P8te NRtHPp;Q%Q@'#rR4P fSQ o0MX[) v + `i9gda/&L9i*1$#"%+ ( E' n7Ȇ(,҅(L@(Q$\x 8=6 'נ9tJ&"[Epljt p#ѣHb :f F`A =l|;&9lDP2ncH R `qtp!dȐYH›+?$4mBA9 i@@ ]@ꃤFxAD*^Ŵ#,(ε  $H}F.xf,BD Z;PK1FAPKAAOEBPS/dcommon/bp_layout.css# @charset "utf-8"; /* bp_layout.css Copyright 2007, Oracle and/or its affiliates. All rights reserved. */ body { margin: 0ex; padding: 0ex; } h1 { display: none; } #FOOTER { border-top: #0d4988 solid 10px; background-color: inherit; color: #e4edf3; clear: both; } #FOOTER p { font-size: 80%; margin-top: 0em; margin-left: 1em; } #FOOTER a { background-color: inherit; color: gray; } #LEFTCOLUMN { float: left; width: 50%; } #RIGHTCOLUMN { float: right; width: 50%; clear: right; /* IE hack */ } #LEFTCOLUMN div.portlet { margin-left: 2ex; margin-right: 1ex; } #RIGHTCOLUMN div.portlet { margin-left: 1ex; margin-right: 2ex; } div.portlet { margin: 2ex 1ex; padding-left: 0.5em; padding-right: 0.5em; border: 1px #bcc solid; background-color: #f6f6ff; color: black; } div.portlet h2 { margin-top: 0.5ex; margin-bottom: 0ex; font-size: 110%; } div.portlet p { margin-top: 0ex; } div.portlet ul { list-style-type: none; padding-left: 0em; margin-left: 0em; /* IE Hack */ } div.portlet li { text-align: right; } div.portlet li cite { font-style: normal; float: left; } div.portlet li a { margin: 0px 0.2ex; padding: 0px 0.2ex; font-size: 95%; } #NAME { margin: 0em; padding: 0em; position: relative; top: 0.6ex; left: 10px; width: 80%; } #PRODUCT { font-size: 180%; } #LIBRARY { color: #0b3d73; background: inherit; font-size: 180%; font-family: serif; } #RELEASE { position: absolute; top: 28px; font-size: 80%; font-weight: bold; } #TOOLS { list-style-type: none; position: absolute; top: 1ex; right: 2em; margin: 0em; padding: 0em; background: inherit; color: black; } #TOOLS a { background: inherit; color: black; } #NAV { float: left; width: 96%; margin: 3ex 0em 0ex 0em; padding: 2ex 0em 0ex 4%; /* Avoiding horizontal scroll bars. */ list-style-type: none; background: transparent url(../gifs/nav_bg.gif) repeat-x bottom; } #NAV li { float: left; margin: 0ex 0.1em 0ex 0em; padding: 0ex 0em 0ex 0em; } #NAV li a { display: block; margin: 0em; padding: 3px 0.7em; border-top: 1px solid gray; border-right: 1px solid gray; border-bottom: none; border-left: 1px solid gray; background-color: #a6b3c8; color: #333; } #SUBNAV { float: right; width: 96%; margin: 0ex 0em 0ex 0em; padding: 0.1ex 4% 0.2ex 0em; /* Avoiding horizontal scroll bars. */ list-style-type: none; background-color: #0d4988; color: #e4edf3; } #SUBNAV li { float: right; } #SUBNAV li a { display: block; margin: 0em; padding: 0ex 0.5em; background-color: inherit; color: #e4edf3; } #SIMPLESEARCH { position: absolute; top: 5ex; right: 1em; } #CONTENT { clear: both; } #NAV a:hover, #PORTAL_1 #OVERVIEW a, #PORTAL_2 #OVERVIEW a, #PORTAL_3 #OVERVIEW a, #PORTAL_4 #ADMINISTRATION a, #PORTAL_5 #DEVELOPMENT a, #PORTAL_6 #DEVELOPMENT a, #PORTAL_7 #DEVELOPMENT a, #PORTAL_11 #INSTALLATION a, #PORTAL_15 #ADMINISTRATION a, #PORTAL_16 #ADMINISTRATION a { background-color: #0d4988; color: #e4edf3; padding-bottom: 4px; border-color: gray; } #SUBNAV a:hover, #PORTAL_2 #SEARCH a, #PORTAL_3 #BOOKS a, #PORTAL_6 #WAREHOUSING a, #PORTAL_7 #UNSTRUCTURED a, #PORTAL_15 #INTEGRATION a, #PORTAL_16 #GRID a { position: relative; top: 2px; background-color: white; color: #0a4e89; } PK3( # PKAAOEBPS/dcommon/bookicon.gif:GIF87a!!!)))111999BBBJJJRRRZZZccckkksss{{{ޭ{{ZRRcZZRJJJBB)!!skRB9{sν{skskcZRJ1)!֭ƽ{ZZRccZJJBBB999111)JJ9BB1ZZB!!ﭵBJJ9BB!!))Jk{)1!)BRZJ{BsR!RRJsJ!J{s!JsBkks{RsB{J{c1RBs1ZB{9BJ9JZ!1BJRRs!9R!!9Z9!1)J19JJRk19R1Z)!1B9R1RB!)J!J1R)J119!9J91!9BkksBBJ119BBR!))9!!!JB1JJ!)19BJRZckތ1)1J9B,H*\hp >"p`ƒFF "a"E|ժOC&xCRz OBtX>XE*O>tdqAJ +,WxP!CYpQ HQzDHP)T njJM2ꔀJ2T0d#+I:<жk 'ꤱF AB @@nh Wz' H|-7f\A#yNR5 /PM09u UjćT|q~Yq@&0YZAPa`EzI /$AD Al!AAal 2H@$ PVAB&c*ؠ p @% p-`@b`uBa l&`3Ap8槖X~ vX$Eh`.JhAepA\"Bl, :Hk;PKx[?:PKAAOEBPS/dcommon/conticon.gif^GIF87a!!!)))111999BBBJJJRRRZZZccckkksss{{{ZRR޽{{ssskkkcccZ991ccRZZBBJJZck)19ZcsBJZ19J!k{k)Z1RZs1!B)!J91{k{)J!B!B911)k{cs!1s!9)s!9!B!k)k1c!)Z!R{9BJcckZZcBBJ99B119{{!!)BBRBBZ!))999R99Z!!999c1!9!)19B1)!B9R,  oua\h2SYPa aowwxYi 9SwyyxxyYSd $'^qYȵYvh ч,/?g{н.J5fe{ڶyY#%/}‚e,Z|pAܠ `KYx,ĉ&@iX9|`p ]lR1khٜ'E 6ÅB0J;t X b RP(*MÄ!2cLhPC <0Ⴁ  $4!B 6lHC%<1e H 4p" L`P!/,m*1F`#D0D^!AO@..(``_؅QWK>_*OY0J@pw'tVh;PKp*c^PKAAOEBPS/dcommon/blafdoc.cssL@charset "utf-8"; /* Copyright 2002, 2011, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2011.10.7 */ body { font-family: Tahoma, sans-serif; /* line-height: 125%; */ color: black; background-color: white; font-size: small; } * html body { /* http://www.info.com.ph/~etan/w3pantheon/style/modifiedsbmh.html */ font-size: x-small; /* for IE5.x/win */ f\ont-size: small; /* for other IE versions */ } h1 { font-size: 165%; font-weight: bold; border-bottom: 1px solid #ddd; width: 100%; } h2 { font-size: 152%; font-weight: bold; } h3 { font-size: 139%; font-weight: bold; } h4 { font-size: 126%; font-weight: bold; } h5 { font-size: 113%; font-weight: bold; display: inline; } h6 { font-size: 100%; font-weight: bold; font-style: italic; display: inline; } a:link { color: #039; background: inherit; } a:visited { color: #72007C; background: inherit; } a:hover { text-decoration: underline; } a img, img[usemap] { border-style: none; } code, pre, samp, tt { font-family: monospace; font-size: 110%; } caption { text-align: center; font-weight: bold; width: auto; } dt { font-weight: bold; } table { font-size: small; /* for ICEBrowser */ } td { vertical-align: top; } th { font-weight: bold; text-align: left; vertical-align: bottom; } ol ol { list-style-type: lower-alpha; } ol ol ol { list-style-type: lower-roman; } td p:first-child, td pre:first-child { margin-top: 0px; margin-bottom: 0px; } table.table-border { border-collapse: collapse; border-top: 1px solid #ccc; border-left: 1px solid #ccc; } table.table-border th { padding: 0.5ex 0.25em; color: black; background-color: #f7f7ea; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } table.table-border td { padding: 0.5ex 0.25em; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } span.gui-object, span.gui-object-action { font-weight: bold; } span.gui-object-title { } p.horizontal-rule { width: 100%; border: solid #cc9; border-width: 0px 0px 1px 0px; margin-bottom: 4ex; } div.zz-skip-header { display: none; } td.zz-nav-header-cell { text-align: left; font-size: 95%; width: 99%; color: black; background: inherit; font-weight: normal; vertical-align: top; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-header-link { font-size: 95%; } td.zz-nav-button-cell { white-space: nowrap; text-align: center; width: 1%; vertical-align: top; padding-left: 4px; padding-right: 4px; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-button-link { font-size: 90%; } div.zz-nav-footer-menu { width: 100%; text-align: center; margin-top: 2ex; margin-bottom: 4ex; } p.zz-legal-notice, a.zz-legal-notice-link { font-size: 85%; /* display: none; */ /* Uncomment to hide legal notice */ } /*************************************/ /* Begin DARB Formats */ /*************************************/ .bold, .codeinlinebold, .syntaxinlinebold, .term, .glossterm, .seghead, .glossaryterm, .keyword, .msg, .msgexplankw, .msgactionkw, .notep1, .xreftitlebold { font-weight: bold; } .italic, .codeinlineitalic, .syntaxinlineitalic, .variable, .xreftitleitalic { font-style: italic; } .bolditalic, .codeinlineboldital, .syntaxinlineboldital, .titleinfigure, .titleinexample, .titleintable, .titleinequation, .xreftitleboldital { font-weight: bold; font-style: italic; } .itemizedlisttitle, .orderedlisttitle, .segmentedlisttitle, .variablelisttitle { font-weight: bold; } .bridgehead, .titleinrefsubsect3 { font-weight: bold; } .titleinrefsubsect { font-size: 126%; font-weight: bold; } .titleinrefsubsect2 { font-size: 113%; font-weight: bold; } .subhead1 { display: block; font-size: 139%; font-weight: bold; } .subhead2 { display: block; font-weight: bold; } .subhead3 { font-weight: bold; } .underline { text-decoration: underline; } .superscript { vertical-align: super; } .subscript { vertical-align: sub; } .listofeft { border: none; } .betadraft, .alphabetanotice, .revenuerecognitionnotice { color: #e00; background: inherit; } .betadraftsubtitle { text-align: center; font-weight: bold; color: #e00; background: inherit; } .comment { color: #080; background: inherit; font-weight: bold; } .copyrightlogo { text-align: center; font-size: 85%; } .tocsubheader { list-style-type: none; } table.icons td { padding-left: 6px; padding-right: 6px; } .l1ix dd, dd dl.l2ix, dd dl.l3ix { margin-top: 0ex; margin-bottom: 0ex; } div.infoboxnote, div.infoboxnotewarn, div.infoboxnotealso { margin-top: 4ex; margin-right: 10%; margin-left: 10%; margin-bottom: 4ex; padding: 0.25em; border-top: 1pt solid gray; border-bottom: 1pt solid gray; } p.notep1 { margin-top: 0px; margin-bottom: 0px; } .tahiti-highlight-example { background: #ff9; text-decoration: inherit; } .tahiti-highlight-search { background: #9cf; text-decoration: inherit; } .tahiti-sidebar-heading { font-size: 110%; margin-bottom: 0px; padding-bottom: 0px; } /*************************************/ /* End DARB Formats */ /*************************************/ @media all { /* * * { line-height: 120%; } */ dd { margin-bottom: 2ex; } dl:first-child { margin-top: 2ex; } } @media print { body { font-size: 11pt; padding: 0px !important; } a:link, a:visited { color: black; background: inherit; } code, pre, samp, tt { font-size: 10pt; } #nav, #search_this_book, #comment_form, #comment_announcement, #flipNav, .noprint { display: none !important; } body#left-nav-present { overflow: visible !important; } } PKʍPKAAOEBPS/dcommon/rightnav.gif&GIF89a1ֽ筽ޭƔkZZk{Bc{,@ ) l)- $CҠҀ ! D1 #:aS( c4B0 AC8 ְ9!%MLj Z * ctypJBa H t>#Sb(clhUԂ̗4DztSԙ9ZQҀEPEPEPEPEPEPEPM=iԍP Gii c*yF 1׆@\&o!QY00_rlgV;)DGhCq7~..p&1c:u֫{fI>fJL$}BBP?JRWc<^j+χ5b[hֿ- 5_j?POkeQ^hֿ1L^ H ?Qi?z?+_xɔŪ\썽O]χ>)xxV/s)e6MI7*ߊޛv֗2J,;~E4yi3[nI`Ѱe9@zXF*W +]7QJ$$=&`a۾?]N T䏟'X)Ɣkf:j |>NBWzYx0t!* _KkoTZ?K Gc+UyڹgNuh^iSo5{\ܹ3Yos}.>if FqR5\/TӮ#]HS0DKu{($"2xִ{SBJ8=}Y=.|Tsц2UЫ%.InaegKo z ݎ3ֹxxwM&2S%';+I',kW&-"_¿_ Vq^ܫ6pfT2RV A^6RKetto^[{w\jPZ@ޢN4/XN#\42j\(z'j =~-I#:q[Eh|X:sp* bifp$TspZ-}NM*B-bb&*xUr#*$M|QWY ~p~- fTED6O.#$m+t$˙H"Gk=t9r娮Y? CzE[/*-{c*[w~o_?%ƔxZ:/5𨴟q}/]22p qD\H"K]ZMKR&\C3zĽ[PJm]AS)Ia^km M@dК)fT[ijW*hnu Ͳiw/bkExG£@f?Zu.s0(<`0ֹoxOaDx\zT-^ѧʧ_1+CP/p[w 9~U^[U<[tĽwPv[yzD1W='u$Oeak[^ |Gk2xv#2?¹TkSݕ| rݞ[Vi _Kz*{\c(Ck_܏|?u jVڔ6f t?3nmZ6f%QAjJf9Rq _j7Z-y.pG$Xb]0')[_k;$̭?&"0FOew7 z-cIX岛;$u=\an$ zmrILu uٞ% _1xcUW%dtÀx885Y^gn;}ӭ)場QEQ@Q@Q@Q@Q@Q@!4xPm3w*]b`F_931˜[ן+(> E ly;<;MF-qst+}DH @YKlLmؤciN<|]IU)Lw(8t9FS(=>og<\Z~u_+X1ylsj'eՃ*U3`C!N9Q_WܱhKc93^ua>H ƕGk=8~e#_?{ǀe-[2ٔ7;=&K挑5zsLdx(e8#{1wS+ΝVkXq9>&yஏh$zq^0~/j@:/«Vnce$$uoPp}MC{$-akH@ɫ1O !8R9s5ԦYmϧ'OUṡ5T,!Ԛ+s#1Veo=[)g>#< s)ƽُA^䠮ωFUj(ǩ|N3Jڷ睁ϱuږZYGOTsI<&drav?A^_f׻B$,O__ԿC`it{6>G׈C~&$y؎v1q9Sc1fH[ѽ>,gG'0'@Vw,BO [#>ﱺg5ΒFVD%Yr:O5 Tu+O멃]ی38Ze}R&ѝ_xzc1DXgس;<,_,{ƽY'AS#oF.M#~cBuEx7G+Y)(5q+GCV;qF+CLQ)qEC&6z𿊘z}?&w=+)??&\g{;V??׻xGœdٿ׼-Nc')3K]N)iLTӿCdb7Q^a N sd>Fz[0S^s'Zi 77D}kWus ab~~H(>.fif9,~|Jk;YN3H8Y(t6Q݉k͇_÷Z+2߄&[ +Tr^藺97~c܎=[f1RrBǓ^kEMhxYVm<[џ6| kqbѱ| YA{G8p?\UM7Z66 g1U1igU69 u5Pƪ:VVZC=[@ҹ¨$kSmɳО\vFz~i3^a Osŧυ9Q}_3 όO{/wgoet39 vO2ea;Ύ7$U#?k+Ek&dpzbӱ+TaB0gN{[N7Gי}U7&@?>Fz~E!a@s ?'67XxO*!?qi]֏TQN@tI+\^s8l0)2k!!iW8F$(yOּT.k,/#1:}8uT˾+5=O/`IW G֯b.-<= HOm;~so~hW5+kS8s.zwE| ?4ӿw/K N 9?j(#0UT` Wzw}:_*9m>󑓀F?ELzv=8q:=WgJ`nDr Zе<ֹ](Q@Q@Q@Q@Q@Q@Q@Q@ 'IdC0EYJVcMty_~u+Sw-aO n<[YJgL#6i g5ЖDZ14cʝ!!\/M}/_AYR__>oC? _?7_G#RERW쏞KB}JxGSkǕA pƱơP m]hwB7U$Zq M95"3q1ioATߚ{g.t uu2k=;h#YB= fgS :TdLԃ!44mFK{Hrd^7oz|BVr<{)6AXգV»|>*/hS܏z͆OM=Εq (s|s׊LKQI :9NJ)P+!ʣoAF>+=@I}"x/}۠1aנc¹4emC:>p_xWKX` >R3_S½èųp3޺u3N e یbmͺ<_ mnݮ1Op?Gm)Qb%N585'%Ahs\6yw!"&Ɨ._wk)}GP;Z!#\"< *oƾ\)}N>"լ/~]Lg}pBG X?<zZ#x69S=6) jzx=y9O&>+e!!? ?s~k5Gʏ)?*ce7Ox~k5􇔾Q/e7/Ԑ#3OgNC0] ;_FiRl>Q.g>!%k#ú:Kn'&}?U@\pџPtp)v<{_i}Oվֲ3XIYIx~b<D?(=_JXH=bbi=Oh?_ C_O)}oW쏜? %Ƶ;-RYFi`wۭ{ϖZMtQ$"c_+ԃx1*0b;ԕ݋ESQEQEQEQEQEQEQEQEQEQZ(1F)h1K@XLRE&9P (bf{RӨ&)PEPEPbԴPGKZ(iإbn(:A%S0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((PKje88PKAAOEBPS/dcommon/help.gif!GIF89a1εֵ֜֜{kZsBc{,@ )sƠTQ$8(4ʔ%ŌCK$A HP`$h8ŒSd+ɡ\ H@%' 6M HO3SJM /:Zi[7 \( R9r ERI%  N=aq   qƦs *q-n/Sqj D XZ;PKއ{&!PKAA OEBPS/toc.htmCA Table of Contents

Contents

Title and Copyright Information

Preface

1 Oracle Database Client Installation Overview

2 Oracle Database Client Preinstallation Requirements

3 Installing Oracle Database Client

4 Oracle Database Client Postinstallation Tasks

5 Removing Oracle Database Client Software

A Installing Java Access Bridge

B Installing Oracle Database Client Using Response Files

C Configuring Oracle Database Globalization Support

D Troubleshooting the Oracle Database Client Installation

Glossary

Index

PKCCPKAAOEBPS/pre_install.htm Oracle Database Client Preinstallation Requirements

2 Oracle Database Client Preinstallation Requirements

This chapter describes the following tasks that you must complete before you can install the Oracle Database Client products:

2.1 Oracle Database Client Hardware Requirements

Table 2-1 lists the required hardware components for Oracle Database Client on Windows 32-bit.

Table 2-2 lists the required hardware components for Oracle Database Client on Windows x64.

Table 2-1 Windows 32-Bit Hardware Requirements

RequirementMinimum Value

System Architecture

Processor: Intel (x86), AMD64, and Intel EM64T

Note: Oracle provides 32-bit (Windows x86) and 64-bit (Windows x64) versions of Oracle Database Client. The 32-bit database client version runs on the 32-bit version of Windows on either x86 or x64 hardware. Oracle certifies 32-bit Oracle Database Client on Windows x64. Table 2-5 lists the operating systems supported on Windows 32-bit.

Physical memory (RAM)

512 MB minimum, 1 GB recommended

On Windows 7, 1 GB minimum

Virtual memory

Double the amount of RAM

Hard disk space

Total ranges between 300 - 1160 MB. See Table 2-3 for details.

Video adapter

256 colors

Screen Resolution

1024 X 768 minimum


Table 2-2 Windows x64 Hardware Requirements

RequirementMinimum Value

System Architecture

Processor: AMD64 and Intel EM64T

Note: Oracle provides 32-bit (Windows x86) and 64-bit (Windows x64) versions of Oracle Database Client. Oracle certifies 32-bit Oracle Database Client on Windows x64. Table 2-6 lists the operating systems supported on Windows x64.

Physical memory (RAM)

512 MB minimum, 1 GB recommended

On Windows 7, 2 GB minimum

Virtual memory

Double the amount of RAM

Hard disk space

Total ranges from 330 - 1260 MB. See Table 2-4 for details.

Video adapter

256 colors

Screen Resolution

1024 X 768 minimum


2.1.1 Hard Disk Space Requirements

This section lists system requirements for Windows platforms that use the NT File System (NTFS). Oracle strongly recommends that you install the Oracle database home (Oracle database binaries, trace files, and so on) on Oracle ACFS or NTFS; the database files themselves must be placed on Oracle ASM if using Oracle ACFS; otherwise they can be placed on NTFS. Usage of Oracle ACFS and Oracle ASM or NTFS instead of FAT32 is recommended to ensure security of these files.

The NTFS system requirements listed in this section are more accurate than the hard disk values reported by the Oracle Universal Installer Summary window. The Summary window does not include accurate values for disk space, the space required to create a database, or the size of compressed files that are expanded on the hard drive.

The hard disk requirements for Oracle Database Client components include space required to install Java Runtime Environment (JRE) and Oracle Universal Installer on the partition where the operating system is installed. If sufficient space is not detected, then installation fails and an error message appears.

Table 2-3 lists the Windows 32-Bit disk space requirements on NTFS.

Table 2-4 lists the Windows x64 disk space requirements on NTFS.

Table 2-3 Windows 32-Bit Disk Space Requirements on NTFS

Installation TypeTEMP SpaceSYSTEM_DRIVE:\Program Files\Oracle\InventoryOracle HomeTotal

Instant Client

130 MB

1.1 MB

215 MB

346.1 MB

Administrator

130 MB

1.1 MB

1024 MB

1155.1 MB

Runtime

130 MB

1.1 MB

735 MB

866.1 MB

Custom (all components installed)

130 MB

1.1 MB *

1024 MB *

1155.1 MB *


* Disk space requirements vary, depending on the components selected.

Table 2-4 Windows x64 Disk Space Requirements on NTFS

Installation TypeTEMP SpaceSYSTEM_DRIVE:\Program Files\Oracle\InventoryOracle HomeTotal

Instant Client

130 MB

5 MB

244 MB

380 MB

Administrator

130 MB

5 MB

1126.4 MB

1261.4 MB

Runtime

130 MB

5 MB

750 MB

885 MB

Custom (all components installed)

130 MB

5 MB *

1126.4 MB *

1261.4 MB *


* Disk space requirements vary, depending on the components selected.


Note:

If you want to configure only the Instant Client Light component of Instant Client, you need 30–32 MB of disk space to store the related files. Refer to "Configuring Instant Client Light" for more information.


See Also:

"NTFS File System and Windows Registry Permissions" in Oracle Database Platform Guide for Microsoft Windows

2.1.2 Verifying Hardware Requirements

To ensure that the system meets these requirements, follow these steps:

  1. Determine the physical RAM size. For example, on a Windows 2003 computer, double-click System in the Windows Control Panel and select the General tab.

    On a Windows Server 2008 R2 computer, click System and Security in the Windows Control Panel, then click System.

    If the size of the physical RAM installed in the system is less than the required size, then you must install more memory before continuing.

  2. Determine the size of the configured virtual memory (also known as paging file size). For example, on a Windows 2003 computer, double-click System, click the Advanced tab, and click Settings in the Performance section. Then select the Advanced tab.

    On a Windows Server 2008 R2 computer, click System and Security, then click System, click Advanced System Settings, click the Advanced tab on System Properties page, and then click Settings in the Performance section. Then select the Advanced tab on Performance Options page.

    The virtual memory is listed in the Virtual Memory section.

    If necessary, see your operating system documentation for information about how to configure additional virtual memory.

  3. Determine the amount of free disk space on the system. For example, on a Windows 2003 computer, double-click My Computer, right-click the drive where the Oracle software is to be installed, and select Properties.

    On a Windows Server 2008 R2 computer, right-click My Computer and click Open.

  4. Determine the amount of disk space available in the temp directory. This is equivalent to the total amount of free disk space, minus what will be needed for the Oracle software to be installed.

    On Windows 32-bit, if there is less than 500 MB of disk space available in the temp directory, then delete all unnecessary files. If the temp disk space is still less than 500 MB, then set the TEMP or TMP environment variable to point to a different hard drive location.

    On Windows x64, if there is less than 125 MB of disk space available in the temp directory, then delete all unnecessary files. If the temp disk space is still less than 125 MB, then set the TEMP or TMP environment variable to point to a different hard drive location.

    For example, to change the environment variables on a Windows Server 2003 computer, double-click System, click the Advanced tab, and click Environment Variables.

    On a Windows Server 2008 R2 computer, click System and Security, then click System, click Advanced System Settings, click the Advanced tab on System Properties page, and then click Environment Variables.

2.2 Oracle Database Client Software Requirements

This section covers the following topics:

2.2.1 General Oracle Database Client Software Requirements for Windows 32-Bit

Table 2-5 lists the software requirements for Oracle Database Client on Windows 32-bit.

Table 2-5 Windows 32-Bit Software Requirements

RequirementValue

Operating System

Oracle Database Client for Windows is supported on the following operating systems:

  • Windows Server 2003 - all editions

  • Windows Server 2003 R2 - all editions

  • Windows XP Professional

  • Windows Vista - Business, Enterprise, and Ultimate editions

  • Windows Server 2008 - Standard, Enterprise, Datacenter, Web, and Foundation editions. The specific operating system component that is not supported is Server Core. For information about Hyper-V support, visit My Oracle Support (formerly OracleMetaLink) at

    https://support.oracle.com/

  • Windows 7 - Professional, Enterprise, and Ultimate editions

Windows Multilingual User Interface Pack is supported.

Compiler

Pro*COBOL has been tested and certified with Net Express 5.0.

The following components are supported with the Microsoft Visual C++ .NET 2005 8.0, Microsoft Visual C++ .NET 2008 9.0, and Intel 10.1 C compilers:

  • Oracle Call Interface

  • External callouts

  • Pro*C/C++

  • XDK

Oracle C++ Call Interface is supported with

  • Microsoft Visual C++ .NET 2005 8.0

  • Microsoft Visual C++ .NET 2008 9.0 - OCCI libraries are installed under ORACLE_HOME\oci\lib\msvc\vc9. When developing OCCI applications with MSVC++ 9.0, ensure that the OCCI libraries are correctly selected from this directory for linking and executing.

  • Intel 10.1 C++ compiler with Microsoft Visual C++ .NET 2005 STLs.

Network Protocol

The Oracle Net foundation layer uses Oracle protocol support to communicate with the following industry-standard network protocols:

  • TCP/IP

  • TCP/IP with SSL

  • Named Pipes


2.2.2 General Oracle Database Client Software Requirements for Windows x64

Table 2-6 lists the software requirements for Oracle Database Client on Windows x64.

Table 2-6 Windows x64 Software Requirements

RequirementValue

Operating System

Oracle Database Client for Windows is supported on the following operating systems:

  • Windows Server 2003 - all x64 editions

  • Windows Server 2003 R2 - all x64 editions

  • Windows XP Professional x64

  • Windows Vista x64 - Business, Enterprise, and Ultimate editions

  • Windows Server 2008 x64 and Windows Server 2008 R2 x64 - Standard, Enterprise, Datacenter, Web, and Foundation editions. The Server Core option is not supported.

    Note: For more information about Hyper-V support, visit My Oracle Support (formerly OracleMetaLink) at

    https://support.oracle.com

  • Windows 7 x64 - Professional, Enterprise, and Ultimate editions

Windows Multilingual User Interface Pack is supported.

Compiler

Pro*COBOL has been tested and certified with Net Express 5.0.

The following components are supported with the Microsoft Visual C++ .NET 2005 8.0, Microsoft Visual C++ .NET 2008 9.0, and Intel 10.1 C compilers:

  • Oracle Call Interface

  • External callouts

  • Pro*C/C++

  • XDK

Oracle C++ Call Interface is supported with

  • Microsoft Visual C++ .NET 2005 8.0

  • Microsoft Visual C++ .NET 2008 9.0 - OCCI libraries are installed under ORACLE_HOME\oci\lib\msvc\vc9. When developing OCCI applications with MSVC++ 9.0, ensure that the OCCI libraries are correctly selected from this directory for linking and executing.

  • Intel 10.1 C++ compiler with Microsoft Visual C++ .NET 2005 STLs.

Network Protocol

The Oracle Net foundation layer uses Oracle protocol support to communicate with the following industry-standard network protocols:

  • TCP/IP

  • TCP/IP with SSL

  • Named Pipes


2.2.3 Instant Client Light Language and Character Set Requirements

In addition to the requirements described in the previous section, if you plan to use Instant Client Light, the applications must use the following languages and character sets:

  • Language: Any language that is supported by Oracle, but only US English error messages are returned for errors generated on the client side.

  • Territory: Any territory that is supported by Oracle.

  • Character sets:

    • Single byte

      • US7ASCII

      • WE8DEC

      • WE8ISO8859P1

      • WE8MSWIN1252

    • Unicode

      • UTF8

      • AL16UTF16

      • AL32UTF8

Instant Client Light can connect to databases having one of the following database character sets. An error is returned if a character set other than those in the list is used as the client or database character set.

  • US7ASCII

  • WE8DEC

  • WE8MSWIN1252

  • WE8ISO8859P1

  • WE8EBCDIC37C

  • WE8EBCDIC1047

  • UTF8

  • AL32UTF8

Instant Client Light can also operate with the OCI Environment handles created in the OCI_UTF16 mode.

The language, territory, and character sets are determined by the NLS_LANG parameter, which is stored in the registry under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_HomeName\NLS_LANG subkey, where HomeName<}*/span> is the unique name identifying the Oracle home.


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 "?") is substituted for it. This terminates parsing and raises an exception.



See Also:

Appendix C, "Configuring Oracle Database Globalization Support" for more information about NLS_LANG

2.3 Oracle Database Network Topics

Typically, the computer on which you want to install Oracle Database is connected to the network, has local storage to contain the Oracle Database installation, has a display monitor, and has a media drive.

This section describes how to install Oracle Database on computers that do not meet the typical scenario. It covers the following topics:

2.3.1 Installing Oracle Database on DHCP Computers

Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing allows a computer to have a different IP address each time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP addressing in a DHCP system.

In a DHCP setup, the software tracks IP addresses, which simplifies network administration. This lets you add a new computer to the network without having to manually assign that computer a unique IP address. However, before installing Oracle Database onto a computer that uses the DHCP protocol, you must install a loopback adapter to assign a static, non-routable IP address to that computer.

2.3.2 Installing Oracle Database on Computers with Multiple IP Addresses

You can install Oracle Database on a computer that has multiple IP addresses, also known as a multihomed computer. Typically, a multihomed computer has multiple network cards. Each IP address is associated with a host name; additionally, you can set up aliases for the host name. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name.

Clients must be able to access the computer using this host name, or using aliases for this host name. To check, ping the host name from the client computers using the short name (host name only) and the full name (host name and domain name). Both must work.

Setting the ORACLE_HOSTNAME Environment Variable

To set the ORACLE_HOSTNAME environment variable:

  1. Display System in the Windows Control Panel.

  2. In the System Properties dialog box, click Advanced.

  3. In the Advanced tab, click Environment Variables.

  4. In the Environment Variables dialog box, under System Variables, click New.

  5. In the New System Variable dialog box, enter the following information:

    • Variable name: ORACLE_HOSTNAME

    • Variable value: The host name of the computer to use.

  6. Click OK, then in the Environment Variables dialog box, click OK.

  7. Click OK in the Environment Variables dialog box, then in the System Properties dialog box, click OK.

2.3.3 Installing Oracle Database on Computers with Multiple Aliases

A computer with multiple aliases is registered with the naming service under a single IP address but with multiple aliases. The naming service resolves any of those aliases to the same computer. Before installing Oracle Database on such a computer, set the ORACLE_HOSTNAME environment variable to the computer whose host name you want to use.

2.3.4 Installing Oracle Database on Non-Networked Computers

You can install Oracle Database on a non-networked computer. If the computer, such as a laptop, is configured for DHCP and you plan to connect the computer to the network after the Oracle Database installation, perform these steps before you install Oracle Database on the non-networked computer.

  1. Install a loopback adapter on the computer.

    The loopback adapter and local IP address simulate a networked computer. If you connect the computer to the network, Oracle Database still uses the local IP address and host name.

  2. Ping the computer from itself, using only the host name and using the fully qualified name, which should be in the DRIVE_LETTER:\system32\drivers\etc\hosts file.

    For example, if you installed a loopback adapter on a computer called mycomputer on the mydomain.com domain, check the following:

    DRIVE_LETTER:\>ping mycomputer                Ping itself using just the hostname.
Reply from 10.10.10.10                    Returns local IP.
DRIVE_LETTER:\>ping mycomputer.mydomain.com   Ping using a fully qualified name.
Reply from 10.10.10.10                    Returns local IP.

    Note:

    When you ping a computer from itself, the ping command should return the local IP address (the IP address of the loopback adapter).

    If the ping command fails, contact your network administrator.

Connecting the Computer to the Network after Installation

If you connect the computer to a network after installation, the Oracle Database instance on your computer can work with other instances on the network. Remember that you must have installed a loopback adapter on your computer. Your computer can use a static IP or DHCP, depending on the network to which you are connected.

2.3.5 Installing a Loopback Adapter

When you install a loopback adapter, the loopback adapter assigns a local IP address for your computer. After the loopback adapter is installed, there are at least two network adapters on your computer: your own network adapter and the loopback adapter. To run Oracle Database on Windows, set the loopback adapter as the primary adapter.

You can change the bind order for the adapters without reinstalling the loopback adapter. The bind order of the adapters to the protocol indicates the order in which the adapters are used. When the loopback adapter is used first for the TCP/IP protocol, all programs that access TCP/IP first probe the loopback adapter. The local address is used for tools, such as Oracle Enterprise Manager. Any other applications that use a different Ethernet segment are routed to the network card.

A loopback adapter is required if:

This section covers the following topics:

2.3.5.1 Checking if a Loopback Adapter Is Installed on Your Computer

To check if a loopback adapter is installed on your computer, run the ipconfig /all command:

DRIVE_LETTER:\>ipconfig /all

Note:

Loopback Adapter installed on the computer should be made the Primary Network Adapter.

If there is a loopback adapter installed, you would see a section that lists the values for the loopback adapter. For example:

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.10
Subnet Mask . . . . . . . . . . . : 255.255.0.0

2.3.5.2 Installing a Loopback Adapter on Windows Server 2003, Windows Server 2003 R2, or Windows XP

To install a loopback adapter on Windows 2003, Windows Server 2003 R2, or Windows XP:

  1. Open the Windows Control Panel.

  2. Double-click Add Hardware to start the Add Hardware wizard.

  3. In the Welcome window, click Next.

  4. In the Is the hardware connected? window, select Yes, I have already connected the hardware, and click Next.

  5. In the The following hardware is already installed on your computer window, in the list of installed hardware, select Add a new hardware device, and click Next.

  6. In the The wizard can help you install other hardware window, select Install the hardware that I manually select from a list, and click Next.

  7. From the list of common hardware types, select Network adapters, and click Next.

  8. In the Select Network Adapter window, make the following selections:

    • Manufacturer: Select Microsoft.

    • Network Adapter: Select Microsoft Loopback Adapter.

  9. Click Next.

  10. In the The wizard is ready to install your hardware window, click Next.

  11. In the Completing the Add Hardware Wizard window, click Finish.

  12. If you are using Windows 2003, restart your computer.

  13. Right-click My Network Places on the desktop and choose Properties. If you are using Windows Vista or Windows Server 2008, then click Manage Network Connections. This displays the Network Connections Control Panel item.

  14. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

  15. On the General tab, select Internet Protocol (TCP/IP), and click Properties.

  16. In the Properties dialog box, click Use the following IP address and do the following:

    1. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

      • 192.168.x.x (x is any value between 0 and 255)

      • 10.10.10.10

    2. Subnet mask: Enter 255.255.255.0.

    3. Save the values you entered, which you need later in this procedure.

    4. Leave all other fields empty.

    5. Click OK.

  17. Click Close.

  18. Close Network Connections.

  19. Restart the computer.

  20. Add a line to the DRIVE_LETTER:\ WINDOWS\system32\drivers\etc\hosts file with the following format, after the localhost line:

    IP_address   hostname.domainname   hostname

    where:

    • IP_address is the non-routable IP address you entered in step 16.

    • hostname is the name of the computer.

    • domainname is the name of the domain.

    For example:

    10.10.10.10   mycomputer.mydomain.com   mycomputer

  21. Check the network configuration:


    Note:

    Domain name is optional.

    1. Open System in the Control Panel, and select the Computer Name tab. In Windows Vista and Windows Server 2008, the Computer Name tab is not available. In Full computer name, make sure you see the host name and the domain name, for example, sales.us.example.com.

    2. Click Change. In Computer name, you should see the host name, and in Full computer name, you should see the host name and domain name. Using the previous example, the host name would be sales and the domain would be us.example.com.

    3. Click More. In Primary DNS suffix of this computer, you should see the domain name, for example, us.example.com.

2.3.5.3 Installing a Loopback Adapter on Windows Vista and Windows Server 2008

To install a loopback adapter on Windows Vista or Windows Server 2008:

  1. Open the Windows Control Panel.

  2. Double-click Add Hardware to start the Add Hardware wizard.

  3. In the Welcome window, click Next.

  4. In the The wizard can help you install other hardware window, select Install the hardware that I manually select from a list, and click Next.

  5. From the list of hardware types, select the type of hardware you are installing window, select Network adapters, and click Next.

  6. In the Select Network Adapter window, make the following selections:

    • Manufacturer: Select Microsoft.

    • Network Adapter: Select Microsoft Loopback Adapter.

  7. Click Next.

  8. In the The wizard is ready to install your hardware window, click Next.

  9. In the Completing the Add Hardware Wizard window, click Finish.

  10. Go to step 12 of the previous section. The remaining steps are the same as given for Windows Vista.

2.3.5.4 Installing a Loopback Adapter on Windows 7 and Windows Server 2008 R2

To install a loopback adapter on Windows 7 and Windows Server 2008 R2:

  1. Click Start and enter hdwwiz in the Search box.

  2. Click hdwwiz to start the Add Hardware wizard.

  3. Go to step 3 of the previous section. The remaining steps are the same as given for Windows XP.

2.3.5.5 Removing a Loopback Adapter

To remove a loopback adapter:

  1. Display System in the Windows Control Panel.

  2. In the Hardware tab, click Device Manager. This tab is not available with Windows Vista and Windows Server 2008. Click Device Manager instead.

  3. In the Device Manager window, expand Network adapters. You should see Microsoft Loopback Adapter.

  4. Right-click Microsoft Loopback Adapter and select Uninstall.

  5. Click OK.

  6. Restart the computer.

  7. Remove the line from the DRIVE_LETTER:\WINDOWS\system32\drivers\etc\hosts file, added after the localhost line while installing the loopback adapter on other Windows operating systems.

2.4 Oracle Database Client Hardware and Software Certification

The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support (formerly OracleMetaLink) Web site for the most up-to-date list of certified hardware platforms and operating system versions. This Web site also provides compatible client and database versions, patches, and workaround information for bugs. The My Oracle Support (formerly OracleMetaLink) Web site is available at the following URL:

https://support.oracle.com/

You must register online before using My Oracle Support (formerly OracleMetaLink). After logging in, click the Certifications tab from the list of tabs in the home page. On the Certification Information page, choose a product by using the Select Product menu on the left side of the page. Other options include Product Roadmap, and Quick Links.

The following sections list the certification information:

2.4.1 Remote Desktop Services

On Windows, Oracle supports installing, configuring, and running Oracle Database through Remote Desktop Services, formerly known as Terminal Services. To install Oracle Database, Oracle recommends that you start all configuration tools from the Terminal Server console session of the server (using mstsc/console).

Platform-specific support information is as follows:

  • Windows 2003 and Windows Server 2003 R2: You can configure Windows 2003 and Windows Server 2003 R2 to use Terminal Services in Remote Desktop for Administration Mode or Terminal Server Mode.

  • Windows XP, Windows Vista, and Windows 7: The Remote Desktop is only available in Single User Mode.

  • Windows Server 2008 and Windows Server 2008 R2: You can have multiple Remote Desktop sessions.


See Also:

  • The Microsoft Web site for more information about Remote Desktop Services

    http://www.microsoft.com/

  • The My Oracle Support (formerly OracleMetaLink) Web site for the latest Terminal Services and Remote Desktop Services certification information

    https://support.oracle.com/


2.4.2 Oracle Services for Microsoft Transaction Server

Oracle Services for Microsoft Transaction Server running on Windows Vista requires a minimum of Service Pack 1 or higher.

2.4.3 Third-Party Database Certification for SQL Developer

You can use Oracle SQL Developer to view metadata and data of several non-Oracle databases. See "Database Certification for SQL Developer (Oracle and Third-Party)" in Oracle SQL Developer Installation Guide for more information.

2.4.4 Separate 32-Bit Client Software for 64-Bit Platforms

Starting with Oracle Database 11g Release 2 (11.2), the 64-bit client software does not contain any 32-bit client binaries. If you require 32-bit client binaries on 64-bit platforms, then install the 32-bit binaries from the respective 32-bit client software.

However, when you install the 32-bit client binaries on 64-bit platforms, the installer checks for the existence of 32-bit software.

2.4.5 Web Browser Support

The following Web browsers are supported for Oracle Enterprise Manager Database Control:

  • Netscape Navigator 8.1

  • Netscape Navigator 9.0

  • Microsoft Internet Explorer 6.0 SP2

  • Microsoft Internet Explorer 7.0 SP1

  • Microsoft Internet Explorer 8.0

  • Microsoft Internet Explorer 9.0

  • Firefox 2.0

  • Firefox 3.0.7

  • Firefox 3.5

  • Firefox 3.6

  • Safari 3.1

  • Safari 3.2

  • Safari 4.0.x

  • Google Chrome 3.0

  • Google Chrome 4.0

PK]yPKAAOEBPS/deinstall.htmW8 Removing Oracle Database Client Software

5 Removing Oracle Database Client Software

This chapter describes how to completely remove Oracle software and configuration files related to the specified Oracle home using the Deinstallation Tool.

The deinstall command removes the Oracle Database Client installations.

It includes information about the following topics:

5.1 About the Deinstallation Tool

The Deinstallation Tool (deinstall) is available in the installation media before installation, and is available in Oracle home directories after installation. It is located in ORACLE_HOME\deinstall.

The deinstall command uses the information you provide and the information gathered from the software home to create a parameter file. Alternatively, you can supply a parameter file generated previously by the deinstall command using the –checkonly option, or by editing the response file template.


Caution:

When you run the deinstall command, if the central inventory contains no other registered homes besides the home that you are deconfiguring and removing, then the Deinstallation tool removes the following files and directory contents in the Oracle base directory of the Oracle Database installation owner:

  • admin

  • cfgtoollogs

  • checkpoints

  • diag

  • oradata

  • flash_recovery_area

Oracle strongly recommends that you configure your installations using an Optimal Flexible Architecture (OFA) configuration, and that you reserve Oracle base and Oracle home paths for exclusive use of Oracle software. If you have any user data in these locations in the Oracle base that is owned by the user account that owns the Oracle software, then the deinstall command deletes this data.


The command uses the following syntax, where variable content is indicated by italics:

deinstall.bat -home complete path of Oracle home [-silent] [-checkonly] [-local]
[-cleanupOBase] [-paramfile complete path of input parameter property file] [-params name1=value name2=value . . .]
[-o complete path of directory for saving files] [-help]

The default method for running the deinstall tool is from the deinstall directory in the Oracle home as the installation owner:

%ORACLE_HOME%\deinstall
DRIVE_LETTER:\> deinstall

Provide information about your servers as prompted or accept the defaults.

The deinstall tool stops Oracle software, and removes Oracle software and configuration files on the operating system.

In addition, you can run the deinstall tool from other locations, or with a parameter file, or select other options to run the tool.

The options are:

  • -home

    Use this flag to indicate the home path of the Oracle home to check or deinstall. To deinstall Oracle software using the deinstall command in the Oracle home you plan to deinstall, provide a parameter file in another location, and do not use the -home flag.

    If you run deinstall from the ORACLE_HOME\deinstall path, then the -home flag is not required because the tool knows from which home it is being run. If you use the standalone version of the tool, then -home is mandatory.

  • -silent

    Use this flag to run the command in silent or response file mode. If you use the -silent flag, then you must use the -paramfile flag, and provide a parameter file that contains the configuration values for the Oracle home to deinstall or deconfigure.

    You can generate a parameter file to use or modify by running deinstall with the -checkonly flag. The deinstall command then discovers information from the Oracle home to deinstall and deconfigure. It generates the properties file, which you can then use with the -silent option.

    You can also modify the template file deinstall.rsp.tmpl, located in the response folder.

  • -checkonly

    Use this flag to check the status of the Oracle software home configuration. Running the command with the -checkonly flag does not remove the Oracle configuration. The -checkonly flag generates a parameter file that you can use with the deinstall command.

  • -local

    Use this flag on a multinode environment to deinstall Oracle software in a cluster.

    When you run deinstall with this flag, it deconfigures and deinstalls the Oracle software on the local node (the node where deinstall is run). On remote nodes, it deconfigures Oracle software, but does not deinstall the Oracle software.

  • -cleanupOBase

    Use this flag to force the removal of all the contents in the Oracle base directory, including the admin, oradata, and flash_recovery_area directories. This flag forces an Oracle base removal only if the Oracle home that you specify with the -home flag is the only Oracle home associated with the Oracle base directory. You must use the -cleanupOBase flag to force an Oracle base removal for both command-line interface deinstall and response file mode deinstall.

    This flag is available with the deconfig tool available in the Oracle Grid Infrastructure and Oracle Database 11.2.0.3 patch release, and from Oracle Technology Network (OTN).

  • -paramfile complete path of input parameter property file

    Use this flag to run deinstall with a parameter file in a location other than the default. When you use this flag, provide the complete path where the parameter file is located.

    The default location of the parameter file depends on the location of deinstall:

    • From the installation media or stage location: ORACLE_HOME\inventory\response.

    • From a unzipped archive file from OTN: ziplocation\response.

    • After installation from the installed Oracle home: ORACLE_HOME\deinstall\response.

  • -params [name1=value name 2=value name3=value . . .]

    Use this flag with a parameter file to override one or more values to change it in a parameter file you have already created.

  • -o complete path of directory for saving files

    Use this flag to provide a path other than the default location where the properties file is saved. The default location is \response\deinstall.rsp.tmpl.

    The default location of the parameter file depends on the location of deinstall:

    • From the installation media or stage location before installation: ORACLE_HOME\

    • From an unzipped archive file from OTN: \ziplocation\response\.

    • After installation from the installed Oracle home: ORACLE_HOME/deinstall/response.

  • -help

    Use the help option (-help) to obtain additional information about the optional flags.

5.2 Downloading the Deinstall Tool for Use With Failed Installations

If you require the Deinstallation Tool (deinstall) to remove failed or incomplete installations, then it is available as a separate download from the Oracle Technology Network (OTN) Web site.

To download the Deinstallation Tool from OTN:

  1. Go to the following URL:

    http://www.oracle.com/technology/software/products/database/index.html

  2. Under Oracle Database 11g Release 2, click See All for the respective platform for which you want to download the Deinstallation Tool.

    The Deinstallation Tool is available for download at the end of this web page.

5.3 Example of Running the Deinstallation Command

As the deinstall.bat command runs, you are prompted to provide the home directory of the Oracle software that you want to remove from your system. Provide additional information as prompted.

If you run the deinstall tool from the deinstall.zip file, you must include the -home flag, and the help is displayed. If you run the tool from the installed ORACLE_HOME, the -home flag is not required and deinstallation starts without prompting you for a home address.

In the following example, the deinstall.bat command is in the path C:\app\oracle\product\11.2.0\client_1\deinstall, and it uses a parameter file in the software owner location C:\Documents and Settings\oracle\.

DRIVE_LETTER:\> cd \app\oracle\product\11.2.0\client_1\deinstall\
DRIVE_LETTER:\> deinstall -home \app\oracle\product\11.2.0\client_1 -paramfile %HOMEPATH%\myparamfile.tmpl

5.4 Example of a Deinstallation Parameter File for an Oracle Database Client

You can run the deinstallation command on a standalone Oracle Database with the -paramfile option to use the values you specify in the parameter file. The following is an example of a parameter file, in which the Oracle Database binary owner is oracle, the Oracle Database home (Oracle home) is in the path D:\app\oracle\product\11.2.0\client_1, the Oracle base (where other Oracle software is installed) is D:\app\oracle, the Oracle Inventory home is C:\Program Files\Oracle\Inventory, the virtual IP address (VIP) is 192.0.2.1, and the local node (the node where you are running the deinstallation session from) is client1:

#Copyright (c) 2005, 2006 Oracle Corporation.  All rights reserved.
#Wed Feb 18 02:19:20 PST 2009
ORACLE_BASE=D\:\\app\\oracle
INVENTORY_LOCATION=C\:\\Program Files\\Oracle\\Inventory
CRS_HOME=false
HOME_TYPE=CLIENT
ORA_CRS_HOME=
silent=false
local=false
LOCAL_NODE=client1
LOGDIR=D\:\\app\\oracle\\product\\11.2.0\\client_1\\deinstall\\logs\\
ORACLE_HOME=D\:\\app\\oracle\\product\\11.2.0\\client_1
OLD_ACTIVE_ORACLE_HOME=
PK}K\8W8PK AAoa,mimetypePKAAxKhc:iTunesMetadata.plistPKAAYuMETA-INF/container.xmlPKAA(}HWCWOEBPS/advance.htmPKAA[pTO]OEBPS/cover.htmPKAA~u?[['`OEBPS/gblsupp.htmPKAA O77OEBPS/overview.htmPKAArOEBPS/title.htmPKAA.(( OEBPS/jbridge.htmPKAAHH2OEBPS/glossary.htmPKAASg]|OEBPS/post_install.htmPKAATeY,!'!OEBPS/preface.htmPKAA($;OEBPS/index.htmPKAA 9 û OEBPS/install.htmPKAA09646 ~OEBPS/ts.htmPKAA OEBPS/toc.ncxPKAAz&