Oracle® Universal Installer (OUI)

User's Guide

Release 13.2.0.0.0

E37799-03

June 2015

Oracle Universal Installer (OUI) User's Guide, Release 13.2.0.0.0

E37799-03

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

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, then 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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

- What's Changed

1 Introduction to Oracle Universal Installer (OUI)

- 1.1 Key Features

- 1.2 System Requirements

- 1.3 Prerequisite Checks

- 1.4 OUI Launcher

- 1.5 Actions Performed by OUI

- 1.5.1 Installation

- 1.5.2 Deinstallation

- 1.5.3 Cloning

- 1.5.4 Patching

- 1.5.5 Upgrades and Patchsets

- 1.5.6 Inventory Operations

- 1.6 Major Entities Created

- 1.6.1 Inventory

- 1.6.2 Oracle Home

- 1.7 Modes of Installation

- 1.7.1 Interactive Mode

- 1.7.2 Suppressed-Interactive Mode

- 1.7.3 Silent Mode

2 Managing Oracle Home Directories

- 2.1 Installing an Oracle Product

- 2.2 Determining the Default Oracle Home

- 2.3 Managing Multiple Oracle Homes

- 2.3.1 Target Home

- 2.4 Oracle Universal Installer Inventory

- 2.4.1 Structure of the Oracle Universal Installer Inventory

- 2.4.1.1 Central Inventory Pointer File

- 2.4.1.2 Central Inventory

- 2.4.1.3 Oracle Home Inventory

- 2.4.2 Creating the Central Inventory

- 2.4.2.1 Using Session Variables

- 2.4.2.2 Verifying the Operation

- 2.4.3 Detaching Oracle Homes from the Central Inventory

- 2.4.3.1 Using the Optional -local Option

- 2.4.3.2 Removing the Central Inventory

- 2.4.4 Consolidating Multiple Central Inventories

- 2.4.5 Reconstructing a Shared Central Inventory on a Nonshared Location

- 2.4.5.1 Oracle Recommendation Regarding Central Inventory Placement

- 2.4.5.2 Enforced Shared Inventory Check

- 2.4.5.3 Procedure to Reconstruct the Central Inventory

- 2.4.6 Upgrading and Patching the Oracle Home

- 2.4.7 Cloning Oracle Homes

- 2.4.8 Backing up the Central Inventory

- 2.4.9 Recovering from Central Inventory Corruption

- 2.4.9.1 Diagnosing and Recovering from Central Inventory Corruption

- 2.5 Home Selector (Available on Win32 Platforms)

- 2.5.1 Home Selector Overview

- 2.5.2 How Home Selector Works

- 2.5.3 Oracle Home Directory Structure for Windows Platforms

- 2.5.4 Optimal Flexible Architecture Directory Structure (on Unix)

- 2.5.4.1 ORACLE_BASE Directory

- 2.5.4.2 ORACLE_HOME Directory

- 2.6 Global Distribution Registry (GDR) Selections

- 2.6.1 Feature Set Groups

- 2.6.2 Install Types

- 2.6.3 Custom Selections

- 2.6.4 The InstallerConfig API

- 2.7 Removing or Deinstalling an Oracle Home

3 Creating and Customizing a Response File

- 3.1 About Response Files

- 3.1.1 What is a Silent Installation?

- 3.1.2 What is a Response File?

- 3.1.3 Why Perform a Silent Installation?

- 3.2 Modifying a Response File

- 3.3 Saving a Response File after Installation

- 3.4 Response File Format

- 3.4.1 Variable Values

- 3.4.1.1 Variable Lookup Order

- 3.4.1.2 Response File Entries Order

- 3.4.1.3 Setting the Recommendation Value

- 3.4.2 Comments

- 3.4.3 Headers

- 3.4.4 Response File Parameters

- 3.5 Installing with a Response File

- 3.5.1 Specifying a Response File

- 3.5.2 Optional Parameters When Specifying a Response File

- 3.5.3 Setting Response File Variables From the Command Line

- 3.5.3.1 Specifying the Value of a Session Variable

- 3.5.3.2 Specifying the Value of a Component Variable

4 Installing Products

- 4.1 Checking Prerequisites Before Installation

- 4.2 Installing Oracle Products

- 4.2.1 Getting Help While Installing Oracle Products

- 4.2.2 About the oraparam.ini File

- 4.2.3 Modes of Installation

- 4.2.4 Invocation Tools and Examples

- 4.2.5 Installation Media

- 4.2.5.1 Installing from a Single CD-ROM

- 4.2.5.2 Installing from Multiple CD-ROMs

- 4.2.5.3 Installing from a Staged HTTP Location

- 4.2.6 Special Instructions for UNIX Users

- 4.3 Deinstalling Oracle Products

- 4.4 Running Oracle Universal Installer After Installation

- 4.4.1 Starting Oracle Universal Installer

- 4.4.2 Command Line Arguments

- 4.4.3 Using Oracle Universal Installer Exit Codes

- 4.4.4 Cloning Considerations

- 4.5 About Oracle Universal Installer Log Files

5 Cloning Oracle Software

- 5.1 Cloning Features and Benefits

- 5.2 How Cloning Works

- 5.3 Cloning an NG Oracle Home

- 5.3.1 Phase 1: Preparing the Source Oracle Home

- 5.3.2 Phase 2: Cloning the Destination Home

6 Oracle Internationalization and Translation

- 6.1 Installation Language Dialogs

- 6.2 Product Language Selections

- 6.3 Language Add-on

7 Inventory Utilities

- 7.1 Inventory View

- 7.1.1 Console Output

- 7.1.2 CSV File Output

- 7.1.3 XML File Output

- 7.1.4 Inventory View Utility Usage

- 7.2 Inventory Compare

- 7.2.1 Console Output

- 7.2.2 CSV File Output

- 7.2.3 XML File Output

- 7.2.4 Inventory Compare Utility Usage

A Troubleshooting and Debugging OUI

- A.1 Oracle Universal Installer Errors

- A.2 Using SSH

- A.3 Other Tips

- A.3.1 Troubleshooting Third-Party Products

- A.4 Frequently Asked Questions

- A.5 Debugging Mechanisms in Oracle Universal Installer

- A.5.1 Installation Log

- A.5.2 Automated Inventory Backups

B Understanding OUI Commands

- B.1 Options Available in Oracle Universal Installer

- B.2 Command-Line Variables Available in Oracle Universal Installer

C Sample Files

- C.1 Sample Components File

- C.2 Sample oraparam.ini File

- C.3 Sample Components File

D Error Messages and Solutions

- D.1 OUI - 10001

- D.2 OUI - 10004

- D.3 OUI - 10005

- D.4 OUI - 10020

- D.5 OUI - 10021

- D.6 OUI - 10022

- D.7 OUI - 10024

- D.8 OUI - 10025

- D.9 OUI - 10028

- D.10 OUI - 10029

- D.11 OUI - 10030

- D.12 OUI - 10031

- D.13 OUI - 10033

- D.14 OUI - 10034

- D.15 OUI - 10035

- D.16 OUI - 10036

- D.17 OUI - 10038

- D.18 OUI - 10039

- D.19 OUI - 10040

- D.20 OUI - 10041

- D.21 OUI - 10044

- D.22 OUI - 10053

- D.23 OUI - 10054

- D.24 OUI - 10055

- D.25 OUI - 10056

- D.26 OUI - 10058

- D.27 OUI - 10059

- D.28 OUI - 10070

- D.29 OUI - 10082

- D.30 OUI - 10083

- D.31 OUI - 10088

- D.32 OUI - 10091

- D.33 OUI - 10092

- D.34 OUI - 10094

- D.35 OUI - 10095

- D.36 OUI - 10096

- D.37 OUI - 10104

- D.38 OUI - 10105

- D.39 OUI - 10116

- D.40 OUI - 10122

- D.41 OUI - 10135

- D.42 OUI - 10136

- D.43 OUI - 10137

- D.44 OUI - 10153

E Oracle Universal Installer API Inventory

- E.1 Package

- E.2 Class/Interface

- E.3 Annotation Type

- E.4 Enum

- E.5 Use

- E.6 Tree (Class Hierarchy)'

- E.7 Deprecated API

- E.8 Index

- E.9 Prev/Next

- E.10 Frames/No Frames

- E.11 All Classes

- E.12 Serialized Form

- E.13 Constant Field Values

Glossary

Index

Preface

This manual describes how to manage Oracle and third-party software using the Oracle Universal Installer. This guide provides instructions for installing, setting up, and starting the Oracle Universal Installer software. It also provides instructions on cloning and internationalization of Oracle software.

Audience

This manual is intended for users installing Oracle software products using the Oracle Universal Installer and covers only the generic functionality and concepts. Use this manual in conjunction with any product-specific installation guides available with your Oracle product.

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 that have purchased support 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 Documents

For more information, see the following documents in the Oracle Enterprise Manager Cloud Control 12c documentation set:

- Oracle OPatch User's Guide for Windows and UNIX

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

What's Changed

This table provides a brief overview of the document changes for the latest publication of the Oracle® Universal Installer (OUI) User's Guide:

Part Number

Change Summary

E37799-03

Updated to include a known issue about the oraparam.ini file.

E37799-02

Updated OUI command-line options in Table B-1.
Updated OUI command-line variables in Table B-2.

Updated terminology consistency.

1 Introduction to Oracle Universal Installer (OUI)

This chapter is designed to aid developers, administrators, and all other users who install Oracle software by understanding the system requirements, features, and key concepts of Oracle Universal Installer (OUI).

This chapter includes the following sections:

- Key Features

- System Requirements

- Prerequisite Checks

- OUI Launcher

- Actions Performed by OUI

- Major Entities Created

- Modes of Installation

1.1 Key Features

Oracle Universal Installer offers the following features:

- An XML-based centralized inventory
The XML format enables third-party Java applications to query the inventory for information about installed software.

- Cloning of existing Oracle homes
Enables you to copy an existing Oracle home to another location and "fix it up" by updating the installation configuration to be specific to the new environment. Cloning makes it easy to propagate a standard setup without having to install and configure after installation.

- True silent capability
When running Oracle Universal Installer in silent mode on a character mode console, you no longer need to specify an X-server or set the DISPLAY environment variable on UNIX. No GUI classes are instantiated, making the silent mode truly silent.

- Ability to record your Oracle Universal Installer session to a response file
This feature makes it easy to duplicate the results of a successful installation on multiple systems. All the options you selected during the installation are saved in the resulting response file.

- More accurate disk space calculations
Oracle Universal Installer now uses a more accurate method of calculating the disk space your Oracle products require. This feature reduces the risk of running out of disk space during an installation.

- Automatically launched software after installation
Some Oracle products now take advantage of a new feature that enables the software to launch automatically immediately after the installation.

- Cleaner deinstallation and upgrades
Deinstallation completely removes all software, leaving no "bits" behind. This also completely removes files associated with configuration assistants and patchsets. Oracle homes can also be removed from the inventory and registry.

- Integrated prerequisite checking
Provides a prerequisite checking tool to diagnose the readiness of an environment for installation. The prerequisite checks are run as part of the installation process, but can also be run as a separate application.

1.2 System Requirements

The minimum system requirements for Oracle Universal Installer are as follows:

- Java Runtime Environment (JRE) — Automatically installed with Oracle Universal Installer on most platforms. Check the Release Notes or installation guide of the products that you are installing for the required version.

- Memory Requirements — Memory requirements vary depending on the number of components installed. Check the Release Notes or installation guide for the products that you are installing for details. 32 MB is the minimum recommended on all platforms.

- Disk Space Requirements — Oracle recommends at least 200 MB for Oracle Universal Installer files on Windows platforms and 116 MB on UNIX. (UNIX requires more memory because of the difference in JRE sizes for the platforms.) You may need up to 1 MB for the related inventory files.
When you run Oracle Universal Installer from an NFS-mounted user home, especially for Linux, execute the quota command to check the space availability. Never perform an installation on a user home for which space is allocated based on quota.

1.3 Prerequisite Checks

A series of prerequisite checks are performed only if help is not specified. For OUI to perform the checks, include the -prereqchecker option in the command:

<command to be supplied> -prereqchecker
-executeSysPrereqs
-ignoreSysPrereqs

Where:

- -prereqchecker option performs a set of product-specific prerequisite checks, which depend on the product being installed as well as the platform.

- -executeSysPrereqs option checks the basic prerequisites for OUI itself (called system prerequisites, as opposed to prerequisites for the product being installed). After these checks are performed, the installer exits without installing the product.

- -ignoreSysPrereqs option checks system prerequisites but ignores the results.

Once invoked, the prereqchecker application is opened and uses the oraparam.ini file.

1.4 OUI Launcher

Beginning with OUI release 13.1, OUI-based installers are launched either by invoking a self-extracting executable file or by invoking a Java Virtual Machine. It is no longer necessary to manually unzip one or more files before invoking the installer.

Note:
For OUI release 13.1 and later, runInstaller (UNIX) and setup.exe (Windows) are no longer present.

OUI includes a Java-based launcher, which requires Java 1.6 or later. The OUI launcher includes the following features:

- Supports generic launching capabilities.

- Provides an optional, platform-specific self-extracting executable.

- Provides an optional, platform-specific binary executable.

- Supports all options supported by the previous (C-based) version of OUI.

1.5 Actions Performed by OUI

Oracle Universal Installer performs the following activities:

- Installation

- Deinstallation

- Cloning

- Patching

- Upgrades and Patchsets

- Inventory Operations

1.5.1 Installation

Installation is the process of choosing products from a release and deploying them in the target directory. There are four modes of installation, which are explained in Modes of Installation.

1.5.2 Deinstallation

Deinstallation is the process of removing files, directories, shortcuts, start menu items, and Windows registry entries that were created by the installer. These are artifacts known to OUI and tracked by OUI. Artifacts that are not known and tracked by OUI are not removed.

Note:
This process does not remove the files and directories created either by other tools or directly by the user. For example, deinstall does not remove artifacts created by other tools, such as:

- Domain directories ($ORACLE_HOME/user_projects)

- Logs ($ORACLE_HOME/logs)

- Individual files ($ORACLE_HOME/domain_registry.xml)

A de-installation can be executed either interactively or silently.

1.5.3 Cloning

Cloning is the process of copying an existing installation to a different location while preserving its configuration. You can install multiple copies of the Oracle product easily on different computers using cloning. During cloning, Oracle Universal Installer is invoked in clone mode to adapt the home to the target environment. Oracle Universal Installer in clone mode replays all the actions that have been executed to originally install the Oracle home. The difference between installation and cloning is that during cloning, Oracle Universal Installer runs the actions in the clone mode. Each action decides how to respond during cloning.

1.5.4 Patching

During patching, a small collection of files are copied over an existing installation to fix certain bugs. OPatch is an Oracle-supplied utility that facilitates Oracle software patching. For more information on OPatch, see the Oracle OPatch User's Guide:

http://docs.oracle.com/cd/E24628_01/doc.121/e39376/toc.htm

1.5.5 Upgrades and Patchsets

Oracle Universal Installer enables you to upgrade a product from one version to another version. An upgrade is a major product enhancement that often requires installation of the upgraded software.

A group of patches form a patchset, which allows you to upgrade a product incrementally (such as, from version 11.1 to version 11.1.0.7.0 or version 11.2).

1.5.6 Inventory Operations

Oracle Universal Installer supports the following inventory operations:

Attaching Oracle Home

Oracle Universal Installer uses the -attachHome option to attach an Oracle home to the inventory to set up the Central Inventory (a system-specific inventory of the installations on this system) or to register an existing Oracle home with the Central Inventory. You can use attachHome.sh (cmd) from an Oracle home.

For more information, see Creating the Central Inventory.

Detaching Oracle Home

Oracle Universal Installer uses the -detachHome option to remove an Oracle home from the Central Inventory. You can use detachHome.sh (cmd) from an Oracle home.

For more information, see Detaching Oracle Homes from the Central Inventory.

1.6 Major Entities Created

The following major entities are created when you run Oracle Universal Installer.

- Inventory

- Oracle Home

1.6.1 Inventory

The Oracle Universal Installer inventory stores information about all Oracle software products installed in all the Oracle homes on a host, provided the product was installed using Oracle Universal Installer. The inventory is organized as follows:

- Central Inventory

- Oracle home inventory

For more information on the inventory and the structure of the inventory, see Oracle Universal Installer Inventory.

1.6.2 Oracle Home

An Oracle home is the system context in which the Oracle products run. This context consists of the following:

- Directory location where the products are installed.

- Corresponding system path setup.

- Program groups associated with the products installed in that home (where applicable).

- Services running from that home.

For more information on Oracle homes, see Chapter 2, "Managing Oracle Home Directories."

1.7 Modes of Installation

You can run the Oracle Universal Installer in the following modes:

- Interactive Mode

- Suppressed-Interactive Mode

- Silent Mode

1.7.1 Interactive Mode

You can use the interactive mode to walk through the installation by providing information in the dialogs when prompted. This method is useful when installing a small number of products in different setups on a small number of hosts.

1.7.2 Suppressed-Interactive Mode

You can use this mode to supply the necessary information by using a combination of a response file or command line entries with certain interactive dialogs. This is useful when an installation has a common set of parameters that can be captured in a response file, in addition to the custom information that you must enter manually.

1.7.3 Silent Mode

You can use this mode to bypass the Graphical User Interface (GUI) and supply the necessary information in a response file. This method is useful when installing the same product multiple times on multiple hosts. By using the response files, you can also automate the installation of a product for which you know the installation parameters.

For more information on silent installation, see Chapter 3, "Creating and Customizing a Response File."

2 Managing Oracle Home Directories

The Oracle Universal Installer (OUI) supports the installation of several active Oracle home directories on the same host. An Oracle home is a directory into which all Oracle software is installed and is referenced by an environment variable. The Oracle home consists of the following:

- Directory location where the products are installed.

- Corresponding system path setup.

- Program groups associated with the products installed in the home (where applicable).

- Services running from the home.

The Oracle base location is the location where the binaries are stored. During installation, you are prompted for the Oracle base path. Typically, an Oracle base path for the database is created during Oracle Grid Infrastructure installation.

To prepare for installation, Oracle recommends that you only set the ORACLE_BASE environment variable to define paths for Oracle binaries and configuration files. OUI creates other necessary paths and environment variables in accordance with the Optimal Flexible Architecture (OFA) rules for well-structured Oracle software environments.

For example, with Oracle Database 11g, Oracle recommends that you do not set an Oracle home environment variable allow OUI to create it instead. If the Oracle base path is /u01/app/oracle, then by default, OUI creates the following Oracle home path:

/u01/app/oracle/product/11.2.0/dbhome_1

Ensure that the paths you select for Oracle software, such as Oracle home paths and the Oracle base path, use only ASCII characters. Because installation owner names are used by default for some paths, this ASCII character restriction applies to user names, file names, and directory names.

The following topics are discussed:

- Installing an Oracle Product

- Determining the Default Oracle Home

- Managing Multiple Oracle Homes

- Oracle Universal Installer Inventory

- Home Selector (Available on Win32 Platforms)

- Global Distribution Registry (GDR) Selections

- Removing or Deinstalling an Oracle Home

2.1 Installing an Oracle Product

When you install an Oracle product, an Oracle home is created.

To install the product and create the Oracle home, perform the following steps:

1. Run Oracle Universal Installer.

2. In the Specify Installation Location page, enter the Oracle home settings for the installation session. See Table 2-1 for a description of the fields in this section of the screen.

3. Continue with your installation. See Chapter 4, "Installing Products" for detailed information.

Table 2-1 Oracle Installation Settings for 'Specify Home Details' Page

Settings

Functions

Name

Enter a name for the Oracle home. This name identifies the program group associated with a particular home and the Oracle services installed on this home. The Oracle home name must be between 1 to 127 characters long, and can include only alphanumeric characters and underscores.

Software Location

Enter the full path to an Oracle home, or select an Oracle home from the drop-down list of existing Oracle homes. The Oracle home location is the directory where products are installed.

Data files may or may not be installed within an Oracle home. You can use the Browse button to choose a directory to install your product.

Note:
Oracle recommends that you designate an Oracle home location that is an empty or non-existing directory. If you select a directory for the Oracle home location that is not empty or already exists, you will be warned and asked if you want to proceed.
For silent installations, if a non-empty, existing directory is specified, an error is logged in the console and in the installActions<timestamp>.log file. Also, the Oracle Universal Installer aborts. To override this condition, use the -force option on the command line. The effect of using the -force option is the same as selecting Yes while installing in interactive mode. You receive a warning message, but the installation continues.

2.2 Determining the Default Oracle Home

By default, when you start Oracle Universal Installer, the software searches your system to determine the default Oracle home where Oracle software should be installed.

In all cases, the ORACLE_HOME name is taken first from the command line if it is specified, or else from the response file if specified. (See Chapter 3, "Creating and Customizing a Response File," for instructions for creating a response file.) If not specified, the value of DEFAULT_ORACLE_HOME_NAME in the oraparam.ini file is examined. Typically, the following convention is used for the name:

Ora<short_marketing_name_in_oraparam.ini>_<home_identifier>

Where <short_marketing_name_in oraparam.ini> is the short product marketing name as specified in the oraparam.ini file; for example, "Db11g", and <home_identifier> is a counter derived from the Central Inventory. For example, the ORACLE_HOME name could be OraDb11g_1.

The ORACLE_HOME path is taken first from the command line if specified, or else from the response file if specified. If not, the ORACLE_HOME environment variable is used. If neither is specified, the following conventions are used for the path:

- If ORACLE_BASE has been specified in the environment:

$ORACLE_BASE/product/<version>/<short_name>_<counter>

For example: $ORACLE_BASE/product/11.2.0/Db_1.

- If ORACLE_BASE has not been specified in the environment:

$HOME/product/<version>/<short_name>_<counter>

Where <short_name> is the short product name; for example, "Db", and <counter> is picked up based on the existence of the files. For example, the ORACLE_HOME path could be $HOME/product/11.2.0/Db_1.

The instance-related directory location is accepted first from the response file, if specified. If not, the oradata, flash_recovery_area, admin, and doc directories are created under ORACLE_BASE. If ORACLE_BASE has not been specified, the default is the $ORACLE_HOME/oradata directory. If the parent directory of the Oracle home is writable, these directories are created in the parent directory of the Oracle home.

2.3 Managing Multiple Oracle Homes

Oracle Universal Installer supports the installation of several active Oracle homes on the same host as long as the products support this at run-time. Multiple versions of the same product or different products can run from different Oracle homes concurrently. Products installed in one home do not conflict or interact with products installed on another home. You can update software in any home at any time, assuming all Oracle applications, services, and processes installed on the target home are shut down. Processes from other homes may still be running.

2.3.1 Target Home

The Oracle home currently accessed by Oracle Universal Installer for installation or deinstallation is the target home. To upgrade or remove products from the target homes, these products must be shut down or stopped.

2.4 Oracle Universal Installer Inventory

The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.

Inventory information is stored in Extensible Markup Language (XML) format. The XML format enables easier diagnosis of problems and faster loading of data. Any secure information is not stored directly in the inventory. As a result, during removal of some products, you may be prompted to enter the required credentials for validation.

Note:
Oracle recommends placing the central inventory on a local file system that is not shared by other systems, since the central inventory is a system-specific inventory of the installations on this system.
It is strongly recommended that you place the central inventory on a local disk so that installations from other systems do not corrupt the inventory. You should not place the central inventory in the Oracle Base.

The following OUI inventory topics are presented:

- Structure of the Oracle Universal Installer Inventory

- Creating the Central Inventory

- Detaching Oracle Homes from the Central Inventory

- Consolidating Multiple Central Inventories

- Reconstructing a Shared Central Inventory on a Nonshared Location

- Upgrading and Patching the Oracle Home

- Cloning Oracle Homes

- Backing up the Central Inventory

- Recovering from Central Inventory Corruption

2.4.1 Structure of the Oracle Universal Installer Inventory

The Oracle Universal Installer inventory has the following hierarchical structure:

- Central Inventory Pointer File

- Central Inventory

- Oracle Home Inventory

2.4.1.1 Central Inventory Pointer File

Every Oracle software installation has an associated Central Inventory where the details of all the Oracle products installed on a host are registered. The Central Inventory is located in the directory that the inventory pointer file specifies. Each Oracle software installation has its own Central Inventory pointer file that is unknown to another Oracle software installation.

For Oracle homes sharing the same Central Inventory, the Oracle Universal Installer components perform all read and write operations on the inventory. The operations on the Central Inventory are performed through a locking mechanism. This implies that when an operation such as installation, upgrade, or patching occurs on an Oracle home, these operations become blocked on other Oracle homes that share the same Central Inventory.

Table 2-2 shows the location of the default inventory pointer file for various platforms:

Table 2-2 Default Inventory Pointer File Locations

Platform

Default Inventory Pointer Location

Linux
Linux.PPC64
AIX

/etc/oraInst.loc

Solaris.SPARC
Solaris.X64
HPUX
HPIA
HP.TRU64
Linux.IA64
Linux.xSeries

/var/opt/oracle/oraInst.loc

Windows
Windows.X64
Windows.IA64

HKEY_LOCAL_MACHINE/Software/Oracle/inst.loc

The following string shows an example of the path for the oraInst.loc file:

inventory_loc=/home/oracle_db11g/product/11.2.0/db_1
inst_group=oracle

In UNIX, if you do not want to use the Central Inventory located in the directory specified by the inventory pointer file, you can use the -invPtrLoc option to specify another inventory pointer file. The syntax is as follows:

./launch -silent -invPtrLoc <Location_of_oraInst.loc> ORACLE_
HOME="<Location_of_Oracle_Home>"

Note:
If the contents of the oraInst.loc file is empty, Oracle Universal Installer prompts you to create a new inventory.

2.4.1.2 Central Inventory

The Central Inventory contains the information relating to all Oracle products installed on a host. It contains the following files and folders:

- Inventory File
This file lists all the Oracle homes installed on the node. For each Oracle home, it also lists the Oracle home name, home index, and nodes on which the home is installed. It also mentions if the home is an Oracle Clusterware home or a removed Oracle home. It can only detect removed Oracle homes created using Oracle Universal Installer version 11.2 and later. This file is present in the following location:

<central inventory location>/ContentsXML/inventory.xml

The following code shows a sample inventory.xml file:

<?xml version="1.0" standalone="yes" ?>
<!-- Copyright (c) 2009 Oracle Corporation. All rights Reserved -->
<!-- Do not modify the contents of this file by hand. -->
<INVENTORY>
<VERSION_INFO>
<SAVED_WITH>11.2.0.0.0</SAVED_WITH>
<MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME="OraDb11g_home1" LOC="/home/oracle_db11g/product/11.2.0/db_1" TYPE="O" IDX="1"/>
<HOME NAME="OUIHome" LOC="D:\OraHome1" TYPE="O" IDX="2" />
<HOME NAME="OUIHome12" LOC="D:\OraHome12" TYPE="O" IDX="3" />
<HOME NAME="OUIHome1" LOC="D:\homes\OraHome1" TYPE="O" IDX="4" />
</HOME_LIST>
</INVENTORY>

Note:
Oracle recommends that you do not remove or manually edit this file as it could affect installation and patching.

- Logs Directory
The Central Inventory contains installation logs in the following location:

<central inventory location>/logs

The logs directory contains the logs corresponding to all installations performed on a particular node. You can also find a copy of the installation log in the $ORACLE_HOME/cfgtoollogs directory.The installation logs for an installation are identified by the timestamp associated with the log files. These files are generally saved in the following format:

<Name_of_Action><YYYY-MM-DD_HH-MM-SS{AM/PM}>.log

For example, consider an attachHome operation performed on 17th, May, 2009 at 6.45AM. The associated log file would be created as follows:

AttachHome2009-05-17_06-45-00AM.log

2.4.1.3 Oracle Home Inventory

Oracle home inventory or local inventory is present inside each Oracle home. It only contains information relevant to a particular Oracle home. This file is located in the following location:

$ORACLE_HOME/inventory

It contains the following files and folders:

- Components File
This file contains the details about third-party applications like Java Runtime Environment (JRE) required by different Java-based Oracle tools and components. In addition, it also contains details of all the components as well as patchsets or interim patches installed in the Oracle home. This file is located here:

ORACLE_HOME/inventory/ContentsXML/comps.xml

For an example of the components file, see Sample Components File in Appendix C, "Sample Files."

- Home Properties File
This file contains the details about the node list, the local node name, and the Oracle Clusterware option for the Oracle home. In a shared Oracle home, the local node information is not present. This file also contains the following information:

- GUID — Unique global ID for the Oracle home.

- ARU ID — Unique platform ID. The patching and patchset application depends on this ID.

- ARU ID DESCRIPTION — Platform description.

The information in oraclehomeproperties.xml overrides the information in inventory.xml. This file is located here:

$ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml

The following example shows the Oracle home property file:

<GUID>893051798#.356758136</GUID>
<HOME CRS="T"/>
<ARU_PLATFORM_INFO>
<ARU_ID>46</ARU_ID>
<ARU_ID_DESCRIPTION>Linux x86</ARU_ID_DESCRIPTION>
</ARU_PLATFORM_INFO>
<CLUSTER_INFO>
<LOCAL_NODE NAME="stacg30"/>
<NODE_LIST><NODE NAME="stacg34"/><NODE
NAME="stacg30"/></NODE_LIST></CLUSTER_INFO>

Table 2-3 lists the ARU_IDs for some platforms:

Table 2-3 ARU_IDs for Platforms

Platform

ARU_ID

Apple Mac OS X (PowerPC)

421

HP Tru64 UNIX

87

HP-UX Itanium

197

HP-UX Itanium (32-bit)

278

HP-UX PA-RISC (32-bit)

2

HP-UX PA-RISC (64-bit)

59

IBM AIX on POWER Systems (32-bit)

319

IBM AIX on POWER Systems (64-bit)

212

IBM i on POWER Systems

43

IBM S/390-based Linux (31-bit)

211

IBM z/OS on System z

30

IBM: Linux on POWER Systems

227

IBM: Linux on System z

209

Linux Itanium

214

Linux x86

46

Linux x86-64

226

Microsoft Windows (32-bit)

912

Microsoft Windows Itanium (64-bit)

208

Microsoft Windows x64 (64-bit)

233

Oracle Solaris SPARC (32-bit)

453

Oracle Solaris SPARC (64-bit)

23

Oracle Solaris x86 (32-bit)

173

Oracle Solaris x86-64 (64-bit)

267

- Other Folders
Table 2-4 lists the other folders you can find in the Oracle home inventory:

Table 2-4 Other Folders in the Oracle Home Inventory

Folder Name

Description

Scripts

Contains the scripts used for the cloning operation.

ContentsXML

Contains the details of the components and libraries installed.

Templates

Contains the template files used for cloning.

oneoffs

Contains the details of the one-off patches applied.

2.4.2 Creating the Central Inventory

Oracle Universal Installer enables you to set up the Central Inventory on a clean host or register an existing Oracle home with the Central Inventory when it is lost or corrupted. If the Central Inventory does not already exist, Oracle Universal Installer creates the Central Inventory in the location specified by the oraInst.loc file.

You can set up the Central Inventory by using the -attachHome option of Oracle Universal Installer. The syntax is as follows:

./launch -silent -attachHome ORACLE_HOME="<Oracle_Home_Location>" "CLUSTER_NODES={<node1,node2>}" LOCAL_NODE="<node_name>"

Or you can use the attachHome.sh (cmd) script with the following syntax:

./attachHome.sh ORACLE_HOME="<Oracle_Home_Location>" "CLUSTER_NODES={<node1,node2>}" LOCAL_NODE="<node_name>"

2.4.2.1 Using Session Variables

You can use the following session variables:

- ORACLE_HOME

- CLUSTER_NODES

- REMOTE_NODES

- LOCAL_NODE

In a cluster installation:

- If you do not pass the CLUSTER_NODES session variable, Oracle Universal Installer takes it from the following file:

$ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml

- If you do not pass the LOCAL_NODE session variable, Oracle Universal Installer takes it from the following file:

$ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml

If it does not find an entry there, it takes it from the Oracle Clusterware stack. If it is not able to find it in the stack, the first node of the CLUSTER_NODES is taken as the LOCAL_NODE.

You can pass the REMOTE_NODES variable if you want to specify the list of remote nodes. If you want to set up the Central Inventory in the local node, you need to pass the -local option, and the REMOTE_NODES variable is empty. The syntax is as follows:

./launch -silent -attachHome -invPtrLoc ./oraInst.loc
ORACLE_HOME="<Oracle_Home_Location>" "REMOTE_NODES={}" -local

Note:
When you use the -local option, it performs the action on the local node irrespective of the cluster nodes specified.

For a non-Oracle Real Application Clusters setup, you do not need to pass the LOCAL_NODE variable, and the CLUSTER_NODES variable is empty. The syntax is as follows:

./launch -silent -attachHome -invPtrLoc ./oraInst.loc
ORACLE_HOME="<Oracle_Home_Location>" "CLUSTER_NODES={}"

You can use the -local option to attach the local Oracle home. If you are using a shared Oracle home with the -local option, use the -cfs option. This ensures that the local node information is not populated inside a shared Oracle home.

2.4.2.2 Verifying the Operation

After attaching the Oracle home, you can verify the success of the operation by verifying the contents of the log file present in the <central_inventory>/logs directory. You can also view the contents of the inventory.xml file under the <central-inventory>/ContentsXML directory to verify if the Oracle home is registered.

Note:
Oracle recommends cloning on Windows operating systems to create the Central Inventory.

2.4.3 Detaching Oracle Homes from the Central Inventory

You can detach an Oracle home from the Central Inventory. When you pass this option, it updates the inventory.xml file present in the Central Inventory. The syntax is as follows:

./launch -silent -detachHome -invPtrLoc ./oraInst.loc ORACLE_HOME="<Oracle_Home_Location>"

(Optional) If you need to point to a custom inventory, you have the option to use the detachHome.sh (cmd) script with the following syntax:

./detachHome.sh -invPtrLoc ./oraInst.loc ORACLE_HOME="<Oracle_Home_Location>"

2.4.3.1 Using the Optional -local Option

You can use the -local option to detach the Oracle home from the inventory of the local node. If you are using a shared Oracle home, use the -cfs option. This ensures that the local node information is not populated inside a shared Oracle home.

./launch -silent -local -cfs -detachHome
ORACLE_HOME="<Oracle_Home_Location>"

2.4.3.2 Removing the Central Inventory

Even after all the Oracle homes on a host are removed, you will find traces of the inventory with certain log files. If you do not want to maintain these files and want to remove the Central Inventory completely, do the following:

- For Unix. To remove the Central Inventory for Unix:

1. Locate the oraInst.loc file and get the Central Inventory location (inventory_loc parameter) from this file.
For Solaris, this file is located in the /var/opt/oracle folder.

For Linux, this file is located in the /etc folder.

2. Remove the Central Inventory by executing the following command:

rm -rf <central_inventory_location>

3. Remove the oraInst.loc file by executing the following command with root privileges:
Solaris:

rm /var/opt/oracle/oraInst.loc

Linux:

rm /etc/oraInst.loc

- For Windows. To remove the Central Inventory from Windows platforms:

1. Locate the registry key:

\\HKEY_LOCAL_MACHINE\Software\Oracle\inst_loc

2. Get the Central Inventory location from this key.

3. Delete the Central Inventory directory and all its contents.

4. Delete the registry key:

\\HKEY_LOCAL_MACHINE\Software\Oracle\inst_loc

2.4.4 Consolidating Multiple Central Inventories

The following procedure explains how to consolidate multiple central inventories into a single central inventory. For Oracle Clusterware and Oracle RAC homes, perform this procedure for each node.

1. Identify the Central Inventory to use and ensure that it is the same path on all nodes of the cluster.

2. Go to this Central Inventory directory and run orainstRoot.sh to ensure that the oraInst.loc file points to this inventory.

3. Identify the other central inventories on the system, then identify the Oracle homes for each Central Inventory.

4. Do the following for each Oracle home:

1. Enter the $ORACLE_HOME/oui/bin directory.

2. Run the following script:

./attachhome.sh -silent -local "CLUSTER_NODES={<List of nodes>}" LOCAL_NODE=<nodename> CRS="TRUE"

For single instance homes, run the ./attachhome.sh -silent script.

3. Verify the inventory updates by going to the ORACLE_HOME/OPatch directory and running the opatch lsinventory -detail command.

4. Verify that the overall inventory is being updated by running the ./launch command and clicking Installed Products... to bring up the contents of the central inventory. Ensure that the inventory shows the new home and the nodes.

2.4.5 Reconstructing a Shared Central Inventory on a Nonshared Location

The following sections provide advisory information about shared Central Inventories, explain the enforced shared inventory check, and provide a procedure for reconstructing the Central Inventory:

- Oracle Recommendation Regarding Central Inventory Placement

- Enforced Shared Inventory Check

- Procedure to Reconstruct the Central Inventory

2.4.5.1 Oracle Recommendation Regarding Central Inventory Placement

The Oracle Central Inventory is a repository for all Oracle products (software) installed on a system. Since the Central Inventory consists of system-specific information, it is required that the Central Inventory be saved on a local non-shared directory on the system. While software can be shared across nodes, the inventory should be local to each system.

If the Central Inventory is shared across system (nodes), this would reflect the installation information for a group of systems collectively. Such a configuration also mandates that all Oracle homes registered in the inventory are also shared. However, a shared inventory is contrary to Central Inventory design principles.

Consequently, Oracle recommends placing the Central Inventory on a local file system not shared by other systems, because the Central Inventory is a system-specific inventory of the installations on this system. Shared inventories are strongly discouraged.

2.4.5.2 Enforced Shared Inventory Check

Since a shared inventory is a recommended practice, OUI displays a warning if you attempt to specify a shared inventory location under the following circumstances:

- Grid Control upgrades from 10.1.x or 10.2.x to 10.2.0.4 or later

- 10.2.0.4 or later Grid Control patchset applications and 11g Grid Control installations

Exceptions are as follows:

- Shared storage prior to 10.2.0.4
If you have already set up your inventory on shared storage prior to Grid Control version 10.2.0.4, you can use the steps in Procedure to Reconstruct the Central Inventory below to reconstruct the central inventory on a non-shared location.

If you do not want to reconstruct the central inventory on a non-shared location, you can pass the -ignoreSharedInventory option to suppress the shared inventory error when invoking runInstaller.

- HPTru64 Cases
Tru64 is a special operating system where all storage is shared storage (including the operating system installed on shared storage). Therefore, a shared inventory is permissible.

2.4.5.3 Procedure to Reconstruct the Central Inventory

Perform the following steps as a Grid Control installation user, which is the user who owns the inventory.

1. Identify a non-shared location for the Central Inventory. This location should have sufficient permissions, such as read and write permissions. Make sure that the installation user creates this new location and that the location is part of the installation group.

2. Obtain the list of Oracle homes from the existing shared Central Inventory registered in oraInventory, use the opatch lsinventory -all command.
Since this is a shared inventory, you may see Oracle homes listed in the Central Inventory from other systems on which the inventory is shared. Identify the Oracle home pertinent to the current system.

3. Edit the default inventory pointer file indicating the location of the non-shared inventory:

inventory_loc=<location of non-shared inventory location>
inst_group=<inventory group>

The default inventory pointer file resides in this file:

/etc/oraInst.loc

All other Unix operating systems, such as Solaris and so forth reside in this file:

/var/opt/oracle/oraInst.loc

4. For each Oracle home in the existing shared inventory, do the following:

1. Detach the home from the existing inventory.

- For a non-RAC home, run:

$ORACLE_HOME/oui/bin/detachhome.sh

- For a Clusterware, RAC, or clustered Agent home, run the following command on each of the nodes:

$ORACLE_HOME/oui/bin/detachhome.sh -local

2. Attach a home to the new non-shared inventory.

- For a non-RAC home, run:

$ORACLE_HOME/oui/bin/attachhome.sh

- For a non-shared Clusterware home, run the following command on each of the nodes:

$ORACLE_HOME/oui/bin/attachhome.sh -local "CLUSTER_NODES=
{comma-separated nodelist}" LOCAL_NODE=<node on which command is run> CRS=true

- For a shared Clusterware home, run the following command on each of the nodes:

$ORACLE_HOME/oui/bin/attachhome.sh -local "CLUSTER_NODES=
{comma-separated nodelist}" LOCAL_NODE=<node on which command is run> CRS=true -cfs

- For a non-shared RAC or clustered Agent home, run the following command on each of the nodes:

$ORACLE_HOME/oui/bin/attachhome.sh -local "CLUSTER_NODES=
{comma-separated nodelist}" LOCAL_NODE=<node on which command is run>

- For a shared RAC or clustered Agent home, run the following command on each of the nodes:

$ORACLE_HOME/oui/bin/attachhome.sh -local "CLUSTER_NODES={comma separated nodelist}" LOCAL_NODE=<node on which command is run> -cfs

Note:
The old inventory becomes obsolete after this migration. You can delete the directory, but this is not mandatory.

2.4.6 Upgrading and Patching the Oracle Home

You can apply patchsets and upgrade an existing Oracle home. You can apply patchsets using Oracle Universal Installer. For more information on upgrading or applying patchsets for an Oracle product, refer to the respective Oracle product installation guide of the product that you want to upgrade.

2.4.7 Cloning Oracle Homes

You can clone an Oracle home using Oracle Universal Installer. For more information on cloning, see Chapter 5, "Cloning Oracle Software."

2.4.8 Backing up the Central Inventory

You can back up the Oracle home using your preferred method. You can use any method such as zip, tar, and cpio to compress the Oracle home.

It is highly recommended to back up the Oracle home before any upgrade or patch operation. You should also back up the Central Inventory when Oracle home is installed or deinstalled.

Example:

Consider a scenario where you have a Database Oracle home called DBHome that is registered with the default Central Inventory in the /product directory. You want to patch this database but decide to back up the database before patching.

1. Enter the following to back up the database:

2. cd /product/DBHome
tar cf - * | gzip > /product/archive/DBHome.tar.gz

If you are using a Win32 system, you could use WinZip to zip up the Oracle home. Do not use the jar command to zip the Oracle home, as this causes the file permissions to become lost.

3. Suppose you apply the patch and something goes wrong. You decide to delete the Oracle home from the Central Inventory and restore the original Oracle home. To delete the Oracle home from the Central Inventory, use the following command:

./launch -silent -detachHome ORACLE_HOME="/product/DBHome"

On Win32 systems, the command would be:

setup.exe -silent -detachHome ORACLE_HOME="C:\product\DBHome"

4. Delete the Oracle home:

cd /product
rm -rf /product/DBHome

5. Restore the original Oracle home and update the Central Inventory. Restore the Oracle home to its original location using the following commands:

mkdir -p /product/DBHome
gunzip  <  /product/archive/DBHome.tar.gz | tar xf -

6. Attach this Oracle home to the Central Inventory:

./launch -silent -attachHome ORACLE_HOME="/product/DBHome"

On Win32 systems, the command would be:

setup.exe -silent -attachHome ORACLE_HOME="C:\product\DBHome"

2.4.9 Recovering from Central Inventory Corruption

The inventory (Central and the Oracle home inventory) is critically important in the Oracle software life-cycle management. The following section explains what you need to do in case of inventory corruption.

2.4.9.1 Diagnosing and Recovering from Central Inventory Corruption

Problem: When you execute the opatch lsinventory -detail command or when you click Installed Products, the Oracle home does not appear.

Cause: This may result because of a missing or corrupted Oracle home inventory.

Action: If the Oracle home inventory is missing or corrupted, restore the Oracle home inventory. If you have not backed up the Oracle home inventory, you may have to install the software on a different node with the same platform and install the same patch levels including interim patches. After that, you can simply copy the inventory directory from the patched Oracle home to the location of the affected Oracle home.

Note:
For Oracle Universal Installer version 10.2.0.2.0 and above, you can use the following scripts in Oracle home to recover from Oracle home inventory corruption:

- detachHome.bat / detachHome.sh: Use this script if the Oracle home is corrupted or needs to be updated.

- attachHome.bat / attachHome.sh: Use this script if the Oracle home needs to be added to the inventory.

For information on recovering from Oracle Real Application Clusters Oracle home inventory corruption, see Diagnosing and Recovering from Central Inventory Corruption.

2.5 Home Selector (Available on Win32 Platforms)

The following sections describe the Home Selector, which is installed as part of Oracle Universal Installer on Windows computers.

To view the Home Selector, click the Environment tab of the Inventory dialog, which appears when you click the Installed Products button on several Oracle Universal Installer screens.

- Home Selector Overview

- How Home Selector Works

- Oracle Home Directory Structure for Windows Platforms

- Optimal Flexible Architecture Directory Structure (on Unix)

2.5.1 Home Selector Overview

The Home Selector is a part of the installation software. The Home Selector enables you to easily change your primary Oracle home (the one that appears first in the PATH environment variable). If you need to switch the active home or need to perform batch work which requires a "default home" to be active, you can use the Home Selector to change the Windows NT system settings.

When using the Home Selector to make a specific Oracle home the active one, the software installation in question is moved to the front of the PATH variable, making it the first directory to be scanned for executable and library files.

Use the GUI in the Environment tab of the Inventory dialog to establish the order of Oracle homes in your PATH variable.

2.5.2 How Home Selector Works

When you perform an installation on a system, Oracle Universal Installer runs the selectHome.bat file to register the Oracle home you selected. In silent mode, you perform this outside Oracle Universal Installer. The first Oracle home is named the "DEFAULT_HOME" and registers itself in the Windows NT registry under the key:

HKEY_LOCAL_MACHINE
Software
Oracle

This is the default Windows NT registry hive which contains all the "generic" Oracle settings. Also, the PATH variable is adjusted, and the BIN directory of the $ORACLE_HOME is added to the environment variable.

Some additional parameters is also written to the key:

HKEY_LOCAL_MACHINE
Software
Oracle
KEY_<ORACLE_Home_Name>

With Oracle Universal Installer, you can change the "DEFAULT_HOME" name to something else. Also, it registers all Oracle settings in the "KEY_<Home_NAME>" sub-key of the ORACLE key.

When an additional Oracle home is added to the system, the PATH variable is adjusted again to add the new BIN directory of the newly installed Oracle software. The registry variables are written to a key named "KEY_<HOME_NAME>".

2.5.3 Oracle Home Directory Structure for Windows Platforms

A typical Oracle home on Windows platforms contains the files and directories shown in Table 2-5.

Table 2-5 Oracle Home Directory for Windows Platforms

Oracle Home Directory

Contents

\BIN

Product executable and DLLs

\LIB

DLL files

\JLIB

All JAR files

\DBS

Common message files

\PROD1

PROD1 product files

\PROD2

PROD2 product files

2.5.4 Optimal Flexible Architecture Directory Structure (on Unix)

The Optimal Flexible Architecture (OFA) standard is a set of configuration guidelines for fast, reliable Oracle databases that require little maintenance.

OFA is designed to:

- Organize large amounts of complicated software and data on disk to avoid device bottlenecks and poor performance

- Facilitate routine administrative tasks such as software and data backup functions, which are often vulnerable to data corruption

- Alleviate switching among multiple databases

- Adequately manage and administer database growth

- Help eliminate fragmentation of free space in the data dictionary, isolate other fragmentation, and minimize resource contention

The OFA directory structure is described in the following sections:

- ORACLE_BASE Directory

- ORACLE_HOME Directory

2.5.4.1 ORACLE_BASE Directory

ORACLE_BASE specifies the BASE of the Oracle directory structure for OFA-compliant databases. A typical ORACLE_BASE directory structure is described in Table 2-6. When installing an OFA-compliant database using Oracle Universal Installer, ORACLE_BASE is set to /pm/app/oracle by default.

Table 2-6 Sample ORACLE_BASE Directory Structure and Content

Directory

Content

admin

Administrative files

doc

online documentation

local

Sub-tree for local Oracle software

product

Oracle software

2.5.4.2 ORACLE_HOME Directory

Table 2-7 shows an example of the Oracle home directory structure and content for an Oracle Server Installation.

If you install an OFA-compliant Oracle Server, the Oracle home directory is /mount_point/app/oracle/product/release_number. Under Unix, the Oracle home directory might contain the following subdirectories, as well as a subdirectory for each Oracle product selected.

Note:
The directory and content information in this table are only samples. The directories that appear in your own Oracle home depend on whether the corresponding products are installed and the version of the Oracle Database you are running.

Table 2-7 Sample Oracle Home Directory Structure and Content

Directory

Content

assistants

configuration Assistants

bin

binaries for all products

ctx

interMedia Text cartridge

dbs

initsid.ora, lksid

install

install related files

lib

Oracle product libraries

jlib

Java classes

md

Spatial cartridge

mlx

Xerox Stemmer (for interMedia Text cartridge)

network

Net8

nlsrtl

NLS run-time loadable data

ocommon

common files for all products

odg

data gatherer

opsm

Parallel Server Manager Components

oracore

core libraries

ord

data cartridges

otrace

Oracle TRACE

plsql

PL/SQL

precomp

precompilers

rdbms

server files and libraries required for the database

slax

SLAX parser

sqlplus

SQL*Plus

2.6 Global Distribution Registry (GDR) Selections

During an installation, prior to the actual installation of files, it may be required to prompt the user to obtain the list of selected features to install. The following sections describe how the selections are defined and how to drive the API which allows modification of these selections:

- Feature Set Groups

- Install Types

- Custom Selections

- The InstallerConfig API

2.6.1 Feature Set Groups

A feature set group, just like the name says, groups features together. From a feature selection and installation perceptive these groups are virtual constructs which are only used for display purposes. The underlying dependency graph does not consider feature set groups. When a feature selection tree is presented to the user the feature set groups are meant to be the parent tree nodes which help group the features into areas the user might be interested in.

The features set references defined under each feature set group have a Boolean attribute called selected which is true by default. This defines the default selection state of that feature when the graph is initialized to the default install type or when an install type is chosen.

The following is an example of two feature set groups you might see defined within a distribution definition. Here the core.feature and client.feature are selected by default, but the samples.feature is not.

<feature-set-group name="Core Product" display-name="Core Product">
<feature-set name="core.feature" version="12.0.0.0.0" visible="true"/>

<feature-set name="samples.feature" version="12.0.0.0.0" visible="true"
selected="false"/>
</feature-set-group>

<feature-set-group name="Client Product" display-name="Client Product">
<feature-set name="client.feature" version="12.0.0.0.0" visible="true"/>
</feature-set-group>

2.6.2 Install Types

The OUI distribution definition gives you the ability to define optional install types. If the distribution definition does not define an install type, then a default one is created internally with the name Typical, which holds the default set of selections which were defined in the feature set group section of the distribution definition. When a distribution definition defines its own install types, the feature set references within each install type override the default selections that were defined in the feature set groups for that specific install type.

Only one of the install types should be set as the default (default="true"). This install type will be used to initialize the selections in the case that no install type is chosen or custom selections changes are made. If a default is not defined or multiple defaults are defined, the first one encountered will be assumed as the default. Whenever a new install type is selected, the selection state of the graph is reset to reflect the selections that the chosen install type defines which will overwrite any custom selections that may have been performed up to that point.

The following is an example of three install types which were defined for the feature set groups in the example above.

<install-type name="Standard" default="true">
</install-type>

<install-type name="Standard With Examples">
<feature-set name="samples.feature" version="12.0.0.0.0" selected="true"/>
</install-type>

<install-type name="Client Only">
<feature-set name="core.feature" version="12.0.0.0.0" selected="false"/>
<feature-set name="samples.feature" version="12.0.0.0.0" selected="false"/>
</install-type>

The Standard install type does not define any overriding selection values for the feature sets. Since this install set provides no overriding values it simply takes on the selection states which were defined in the feature set groups above. This is also the default install type which means it will be used to initialize the default set of selections after the graph is built and in absence of a install type actually being chosen. This means that the initial selection state (or if this install type was chosen) of the features in the graph would contain the core.feature and client.feature in a selected state and the samples.feature in a non-selected state.

The Standard With Examples install set defines that the samples.feature will be selected if this install type is chosen. All other selection states will be inherited from defaults defined in the feature set group section. This means that if this install type were chosen the core.feature, client.feature, and samples.feature will all be in the selected state.

The Client Only install set defines that the core.feature and the samples.feature will not be selected if this install type is chosen. The selection state of the client.feature is inherited from the feature set groups and will be in the selected state. This means that if this install type were chosen the client.feature would be in a selected state and the core.feature and samples.feature will be in a non-selected state.

2.6.3 Custom Selections

If an installer allows for custom feature selection and the user chooses this option during the installation, the "selection tree" which the user is presented with is always a complete view of all feature set groups and visible features in the distribution. This is to say that all feature set groups defined in the distribution will be presented to the user for selection. The default state of the selections in the tree presented will be determined by the install set which was chosen or the default install set if one was not chosen.

2.6.4 The InstallerConfig API

The API for interacting with the feature selections is the com.oracle.cie.gdr.external.InstallerConfig class. This class lives in the com.oracle.cie.gdr_1.0.0.0.jar module. There are two pieces of data which are required any time you are interacting with this API:

- shipHomeDir - This location is the location of the <shiphome>/Disk1/stage directory itself (for example, FROM_LOCATION).

- homeDir - This is the Oracle home directory that was chosen by the user.

The first thing which should be done when interacting with this API is to create a session object. This is done by calling the getInstallerSession(File shipHomeDir, File homeDir) method. The session object which is obtained by calling this method should be kept and reused for all operations in the API which pertain to the shipHomeDir and homeDir which was chosen. If the user chooses a new Oracle home directory, a new session should be created. When the session object is created installation validation is performed. If there are any incompatibilities between the shiphome being installed and the chosen Oracle home a DependencyException error will be thrown.

Eventually, the API Installer may take this session object or a similar one when it is created, but for now as long as the shipHomeDir and homeDir provided to the API Installer match those used to create this session, the selections made via the InstallerConfig API should be honored.

Once you have the session object you should store a reference to this object and pass it to the other API methods:

- Set<String> getInstallTypes(InstallerSession session)
This method gets a Set of the names of the install types which are defined in the distribution. If no install types are defined this will return a Set containing one install type name which is the default and has a name of "Typical". If install types are defined in the distribution definition then this will return that set of names. If the installer wishes to present the user with install type selection, these are the names the user should be presented with. Once the user selects the install type you will call the setInstallType method.

- void setInstallType(InstallerSession session, String name) throws DependencyException, GdrException
This method sets the install type which was selected by the user. When the install type is set the selection state of the graph is reset to match the selections which were defined for that install type. If there's an issue with the dependencies of what was selected in the graph a DependencyException may be thrown. If the install type specified does not exist a GdrException is thrown.

- TreeModel getFeatureSelectionTreeModel(InstallerSession session)
This method gets a TreeModel which contains the feature set groups and features to allow for custom selection. All objects in this tree, with the exception of the root, implement the com.oracle.cie.gdr.selection.Selectable interface which provides the method setSelected(boolean) for modifying the selection state of each item. This model can be presented to the user in the UI and any modifications which are made to the selection state of the objects in the tree model will be automatically reflected in the underlying graph. If a selected feature has dependencies on other features these will automatically be selected to enforce the dependencies.

- Map<SelectableFeatureSetGroup, List<SelectableFeatureSet>> getFeatureSelectionWrappers(InstallerSession session)
This method provides a map of the Selectable objects which are used to create the TreeModel returned from the getFeatureSelectionTreeModel() method. This method is meant to be used only if you wish to populate your own custom TreeModel with the Selectable objects. Any changes to the selection state of these objects will be automatically reflected in the underlying dependency graph.

- void setSelectedFeatures(InstallerSession session, Set<Reference> featureRefs) throws GdrException, DependencyException
This method is meant to be used for programmatic selections of features. This would most likely be used for silent type installations where the user has provided some type of list of features they wish to have installed. The set of feature references provided to this method define the features you wish to have set to a selected state. Only the features in the set and their dependencies will be set as selected, all other features will be unselected.

- Reference createReference(String name, String version)
This is a convenience method for creating the Reference objects which are used in the setSelectedFeatures() method. You would pass the name and version of the feature and a resulting Reference is returned.

The following code snippet shows this API being driven:

File shiphomeDir = new File("/home/user/shiphome");
File oracleHomeDir = new File("/home/user/oraclehome");
try
{
InstallerSession session = InstallerConfig.getInstallerSession(shiphomeDir, oracleHomeDir);
Set<String> installTypes = InstallerConfig.getInstallTypes(session);
if(installTypes.size() > 1)
{
//prompt user to choose install type only if there is more then one since the selections will
//already be initialized to the default install set.
String installType = "Standard"; //installTypes.iterator().next();
InstallerConfig.setInstallType(session, installType);
}
// if the user chooses Custom, get the tree model and create a selction tree from it...

TreeModel model = InstallerConfig.getFeatureSelectionTreeModel(session);
FeatureSelectionTree tree = new FeatureSelectionTree(model);
}
catch(Exception e)
{
e.printStackTrace();
}

2.7 Removing or Deinstalling an Oracle Home

To remove or deinstall Oracle homes, you can either use the Deinstall tool included with the Shiphome, or use the Deinstall utility available as part of the Oracle home.

- To use the Deinstall tool, do the following to remove the Oracle home:

1. Change to the DeinstallTool directory.

2. Run:

deinstall -home <OracleHome>

- To use the Deinstall utility, do the following to remove the Oracle home:

1. Change to the $Oracle_Home/deinstall directory.

2. Run the Deinstall script.

3 Creating and Customizing a Response File

This chapter introduces you to Oracle Universal Installer's availability of response files for silent and suppressed installations. This chapter also describes how to modify or create a response file so you can customize and standardize the installation of Oracle products in your organization.

This chapter is organized into the following sections:

- About Response Files

- Modifying a Response File

- Saving a Response File after Installation

- Response File Format

- Installing with a Response File

3.1 About Response Files

This section answers the following questions:

- What is a Silent Installation?

- What is a Response File?

- Why Perform a Silent Installation?

3.1.1 What is a Silent Installation?

A silent installation runs in the console and does not use the GUI. The interactive dialogs you normally see are not displayed in a silent installation.

Instead of prompting you to select a series of installation options, Oracle Universal Installer installs the software using a predefined set of options stored in a response file or passed on the command line. You can view the progress of a silent installation in the console.

3.1.2 What is a Response File?

A response file is a specification file containing information you normally fetch through the Oracle Universal Installer user interface during an interactive installation session. Each answer is stored as a value for a variable identified in the response file.

For example, values for Oracle home or installation type can be set automatically within the response file.

The response file template for the installation of your product can be found on your stage (CD-ROM) under the <root of CD>/response directory, with pre-populated values. For example:

<Products.xml_Location>/Response/<product>.<installtype>.rsp

Note:
Check the installation guide for the product that you are installing to get the correct list of required files.

3.1.3 Why Perform a Silent Installation?

Silent installations can be useful if you have to install an Oracle product multiple times on multiple computers. If the options you select while installing on each computer are always the same, you save the time of reviewing each installation screen and selecting the various installation options.

Silent installations can also ensure that multiple users in your organization use the same installation options when they install your Oracle products. This makes supporting those users easier because you already know what components and options have been installed on each computer.

Before you perform a silent installation, you should review the settings in the response file template provided with your Oracle product.

Note:
If you attempt to perform a silent installation on a UNIX computer where no Oracle products have been installed, Oracle Universal Installer uses the default inventory location, then prompts you to run the oraInstRoot.sh script with root privileges upon successful installation.
The script is saved in the _*Central Inventory - oraInventory *_ directory. This script sets up the Central Inventory on a clean host. You can override the default location by setting it in INVENTORY_LOCATION. This location is ignored if a Central Inventory already exists and is pointed to by /var/opt/oracle/oraInst.loc (or /etc/oraInst.loc for Linux, AIX, and Sequent).

See Oracle Universal Installer Inventory for more information on the Central Inventory.

The remainder of this chapter describes the various parameters and settings you can modify within an Oracle Universal Installer response file.

3.2 Modifying a Response File

If your product installation includes a response file template, you can find it on your stage (CD-ROM) under the <root of CD>/response directory.

If your product installation does not include a response file template, you can create a response file based on the installation options you select.

To modify the response file:

1. Make a copy of the product's response file and open it in a text editor.

2. Review any information provided in the response file or in the product installation guide.
Many software products use settings in the response file to customize the installation of their particular product. See the response file template for suggestions or guidelines on how to set up the file for your installation.

3. Get familiar with the organization and content of the response file using the information in the Response File Format section.

4. Modify the response file to meet the needs of your organization and save the modified version.

5. See the Installing with a Response File section for information on starting Oracle Universal Installer using your modified response file.

3.3 Saving a Response File after Installation

You can use Oracle Universal Installer in interactive mode to record a response file, which you can edit and then use to complete silent mode or response file mode installations. This method is useful for custom or software-only installations. For more information, see "Recording a Response File" in the Oracle® Database Installation Guide 11g for Linux.

3.4 Response File Format

The following sections describe the organization and content of an Oracle Universal Installer response file:

- Variable Values

- Comments

- Headers

- Response File Parameters

Note:
Oracle recommends using an absolute path for the file name. However, if the file name is a relative path, it should be relative to the directory where the oraparam.ini file is present.

3.4.1 Variable Values

This section contains information on how variables are populated with values.

- Variable Lookup Order

- Response File Entries Order

- Setting the Recommendation Value

3.4.1.1 Variable Lookup Order

All variable values within a response file are in the name-value format. If two components have a variable with the same name, the expression should be written as follows to preserve each variable's uniqueness:

<component>:<variable>=<value>

Component Nomenclature and Version Ambiguity

If two components have the same internal name, but different versions, resolve the ambiguity by specifying the expression as follows:

<component>:<version>:<variable>=<value>

Order of Variables

Oracle Universal Installer looks for command line variables in the following order:

<component>:<version>:<variable>=<value>
<component>:<variable>=<value>
<variable>=<value>

Similarly, if command line variables are not found, Oracle Universal Installer looks for variables in the response file in the same order as shown above.

Note:
Oracle Universal Installer treats incorrect context, format, or type values within a response file as if no value were specified.

3.4.1.2 Response File Entries Order

There are no restrictions on where you place entries in the response file. You can insert entries in any order desired. You can also subsequently move existing entries to any other position within the file. Be aware, however, that although the order of the entries is unimportant, naming conventions require that the variable names must be unique regardless of where they appear in the file.

3.4.1.3 Setting the Recommendation Value

Values for variables are specified as:

<variable> = <recommendation> : <value>

The values that are given as <value_required> must be specified for a silent installation to be successful.

For values that are given as <value_unspecified>, you can optionally specify a value, where <value> can be one of the following types listed in Table 3-1.

Table 3-1 Variable Types and Representations

Type

Representation

Number

10

Boolean

TRUE or FALSE (case insensitive)

String

"Value"

String List

{"value1", "value2"}

The <recommendation> parameter can be specified as Forced or Default.

- If you specify Forced, no dialog appears during installation. The value is automatically used. You cannot change the value.

- If you specify Default, the dialog appears during installation with the value as the default. You can choose another value if desired.

- If nothing is specified for <recommendation>, Forced is used as the default.

3.4.2 Comments

Comments begin with a "#" (hash or pound) symbol. They contain information about the type of the variable, state whether the variable appears in dialog, and describe the function of the variable. A variable and a value are associated with a comment.

For example:

#TopLevelComponent;StringList;Used in Dialog
TopLevelComponent={"Demo", "1.0"}

3.4.3 Headers

The header is a comment that describes the different formats and comment conventions used in a response file.

For example:

#Parameter : UNIX_GROUP_NAME
#Type : String
#Description : UNIX group to be set for the inventory directory.
#Valid only on UNIX platforms.
#Example : UNIX_GROUP_NAME = "install"
UNIX_GROUP_NAME=<Value Unspecified>

3.4.4 Response File Parameters

The following list describes parameters for Oracle Universal Installer. All products installed using Oracle Universal Installer have these parameters in addition to product-specific variables.

Note:
The parameters provided below are OUI-specific and not necessarily the parameters applicable for your platform and version. Always check your specific installation guide for the list of valid response file parameters.

ACCEPT_LICENSE_AGREEMENT

Set this Boolean variable to TRUE if you agree with the license agreement. This parameter requires you to set this variable to TRUE to indicate your acceptance of the license agreement normally accepted in the GUI. This variable is used only in silent installations. Installation cannot continue until this variable is set to TRUE.

CLUSTER_NODES

This parameter lists the nodes on the cluster on which the Oracle home is installed or would be installed. For new installations, this would be the node list on which the installation needs to be done (including the local node). For patching or upgrades, this is the node list on which the Oracle home is already installed.

"CLUSTER_NODES={alpha-1, alpha-2}"

DECLINE_SECURITY_UPDATES

This parameter is used to decline receiving the security updates if a direct connection not available.

If the direct connection is unavailable, set this parameter to false if you do not want to configure Oracle Configuration Manager, or do not want to provide any proxy details for the connection. The default is False.

If you do not set MYORACLESUPPORT_USERNAME to any value and you set this parameter to true, the Oracle Configuration Manager is not configured.

For information on the Oracle Configuration Manager, see the Oracle® Configuration Manager Installation and Administration Guide:

http://docs.oracle.com/cd/E49269_01/doc.12/e48361/toc.htm

DEINSTALL_LIST

Use this parameter to enter a list of components to be removed during a silent deinstall session. For each component, specify the internal component name and version.

DEINSTALL_LIST={"sample1","1.0.0.0.0"}

DEPENDENCY_LIST

The DEPENDENCY_LIST is the list of dependents on which the component depends. These dependent components represent the list of components that appear as "selected" during installation. Following is a list of some of this parameter's characteristics:

FROM_LOCATION

The location of the source of the products to be installed. The default generated value for this parameter is a path relative to the location of the runInstaller command's oraparam.ini file. Relative paths are necessary for shared response files used by multiple users over a network. Since users may be mapping to different drives, absolute paths will not work for shared response files.

Notes:

- This parameter serves the same purpose as SOURCE in oraparam.ini. Use this parameter only if you need to override the default products.xml location.

- You must enter a value for FROM_LOCATION for a complete silent installation. You may want to use the command line to set this parameter. If the location is a relative path, remember that the path should be relative to the location of the oraparam.ini file.

- Make sure that /var/opt/oracle/oraInst.loc (or /etc/oraInst.loc for Linux, AIX, and Sequent) exists. The response file for UNIX has a public variable, setunixinstallgroup, that only becomes effective when it is the first Oracle Universal Installer installation and the oraInst.loc file is not already present in the location mentioned above.

FROM_LOCATION_CD_LABEL

This parameter is used in multiple-CD installations. It includes the label of the compact disk where the file products.jar exists. You can find the label in the disk.label file in the same directory as products.jar.

INCLUDE

This parameter specifies the list of response files to be included in this response file. If you want to include other response files in your main response file, you must use this parameter. Note that the values in the main response file have priority over the included response files.

INCLUDE={"file1.rsp","file2.rsp",............."filen.rsp"}

You should specify the absolute path in the INCLUDE statement for each response file to be included. If you wish to specify a relative path, note that the location is relative to the current working directory (the location of the oraparam.ini file).

INSTALL_TYPE

You can set the installation type variable to determine the installation type of the currently selected top level component.

The installation type variable is only generated for the top level components and only when there is more than one installation type available.

Note:
You must enter a value for INSTALL_TYPE.

LOCAL_NODE

This parameter specifies the current node on which the installation occurs.

LOCAL_NODE={}

LOCATION_FOR_DISK2

This parameter is for the complete path to other disks.

LOCATION_FOR_DISK2="F:\teststage\cd\Disk2"

If there are more than two disks, more variables will be added as LOCATION_FOR_DISK3, and so on.

The CD location for a silent installation is located by two mechanisms:

1. Oracle Universal Installer looks for the Location_For_Disk{DiskNumber} variable in the response file and uses that location.

2. If the variable does not have a value or does not have the required files, it looks for the components under ../../Disk{DiskNumber}/stage (from products.jar).
Therefore, you can either specify the location to look for it in the response file or you can copy them into the disk. For example:

<Product_Shiphome_Location>/stage

NEXT_SESSION

Set this boolean variable to TRUE if the installer needs to go to the File Locations page for another installation or to another response file if you are performing a silent installation.

NEXT_SESSION = TRUE

NEXT_SESSION_ON_FAIL

Set this boolean variable to TRUE to enable users to invoke another installation session even if the current installation session fails. This variable is used only if the
NEXT_SESSION variable is set to TRUE.

NEXT_SESSION_ON_FAIL = TRUE

NEXT_SESSION_RESPONSE

Use this string variable to enter the complete path of the next session's response file if you want to automatically begin another silent installation when the current installation is complete. If you specify only a file name, the Installer looks for the response file in the <TEMP>/orainstall directory. This variable is only used if NEXT_SESSION is set to TRUE; otherwise, Oracle Universal Installer ignores the value of this variable.

NEXT_SESSION_RESPONSE="/private/usr2/nextinstall.rsp"

MYORACLESUPPORT_PASSWORD

This parameter indicates the My Oracle Support password used in Oracle Configuration Manager (OCM) configuration. This parameter is used for validation only if the direct connection is available, or if there is a valid proxy connection (in case no direct connection is available). The default is Empty.

For information on OCM, see the Oracle® Configuration Manager Installation and Administration Guide.

MYORACLESUPPORT_USERNAME

This parameter indicates the My Oracle Support username/e-mail address used in Oracle Configuration Manager (OCM) configuration. This parameter validates the My Oracle Support user name only if the direct connection is available, or if there is a valid proxy connection (in case no direct connection is available).

To avoid configuring OCM, you do not need to pass any values for MYORACLESUPPORT_USERNAME or any other session variables except for DECLINE_SECURITY_UPDATES, which should be set to true. OCM will then be installed, but not configured.

Configuration Use Cases

If only MYORACLESUPPORT_USERNAME is provided,

- OUI does not validate the user name against My Oracle Support, but configures it in anonymous e-mail registration mode.

- there is not a direct connection, and DECLINE_SECURITY_UPDATES=true, OUI does not validate the user name against My Oracle Support, but configures it in disconnected mode.

- there is not a direct connection, and PROXY_* values are provided, OUI does not validate the user name against My Oracle Support, but configures it in anonymous e-mail registration mode.

- SECURITY_UPDATES_VIA_MYORACLESUPPORT=true, and MYORACLESUPPORT_PASSWORD is provided, OUI validates it against My Oracle Support and configures it in My Oracle Support user registration mode.

- SECURITY_UPDATES_VIA_MYORACLESUPPORT=true, and MYORACLESUPPORT_PASSWORD is provided, but there is not a direct connection and DECLINE_SECURITY_UPDATES=true, OUI configures in disconnected mode.

- SECURITY_UPDATES_VIA_MYORACLESUPPORT=true, MYORACLESUPPORT_PASSWORD is provided, but there is not a direct connection and PROXY_* values are provided, OUI configures in My Oracle Support user registration mode.

If MYORACLESUPPORT_USERNAME is empty and DECLINE_SECURITY_UPDATES = true, OUI does not configure OCM.

For information on OCM, see the Oracle® Configuration Manager Installation and Administration Guide.

OPTIONAL_CONFIG_TOOLS

While all the required configuration tools are launched by the installer, you can control the optional configuration tools you would want to launch by specifying the tool's internal names in the OPTIONAL_CONFIG_TOOLS section.

Note:
The OPTIONAL_CONFIG_TOOLS variable is only generated when at least one optional configuration tool is available.

You can call the Net Configuration Assistant or the Database Configuration Assistant at the end of a database installation in silent mode also. For example, to launch the Net Configuration Assistant in silent mode, you can pass the parameter s_responseFileName="netca.rsp".

You can specify both the Auto-launch optional tools and User-launch optional tools in a string list.

#Example : OPTIONAL_CONFIG_TOOLS = {"configtool2 ", "configtool3"}
OPTIONAL_CONFIG_TOOLS=<Value Unspecified>

If no value is specified for this variable, all the tools are run by default. If there is a value specified, only those optional tools are run while the rest of the tools are ignored.

Suppress the configuration tool by mentioning only the tools that you want to run as part of the OPTIONAL_CONFIG_TOOLS variable added for each component. You should use the internal names of the configuration tool. The response file generator generates these internal names also as part of the options provided for the variable.

For example, if oracle.server has Tool1 and Tool2 and you want to run only Tool1 in the response file, you can specify it as follows:

oracle.server:11.2.0.0.0:OPTIONAL_CONFIG_TOOLS={"Tool1"}

ORACLE_BASE

The location of the Oracle Base where all Oracle software and configuration-related files are stored.

ORACLE_HOME

The location where products are to be installed. You must enter a value for ORACLE_HOME for a complete silent installation.

PROXY_HOST

This proxy connection server is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.

PROXY_PORT

This proxy connection port is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.

PROXY_PWD

This proxy connection password is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.

PROXY_USER

This proxy connection user name is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.

REMOTE_NODES

This parameter lists the remote nodes (apart from the local node) on the cluster on which to install during a silent installation. Oracle Universal Installer installs on all named nodes.

"REMOTE_NODES={alpha-1, alpha-2}"

REMOVE_HOMES

Use this parameter to identify the Oracle homes you want to remove from the inventory during a deinstallation session. For each home, specify the home name using the full path information.

REMOVE_HOMES={"/home/oracle/ora9i","/home/oracle/ora8i"}

RESPONSEFILE_VERSION

This parameter specifies the version number of the response file.

RESPONSEFILE_VERSION = <version_number>

RESTART_SYSTEM

Set this boolean variable to TRUE if you want to restart the system without the user's confirmation. This is the force value for restarting the system.

SECURITY_UPDATES_VIA_MYORACLESUPPORT

This parameter is equivalent to the OUI window checkbox that enables users to receive security updates. ("I wish to receive security updates via My Oracle Support," followed by a My Oracle Support Password field.) This parameter enables you to set the password for My Oracle Support credentials. The default is False. If you set this to true, the user must enter a password.

SELECTED_LANGUAGES

You can set the languages in which the components will be installed. You must use the internal name while specifying the value:

en,   : English
fr,   : French
de,   : German
ja,   : Japanese

For example, to specify Japanese:

SELECTED_LANGUAGES = {"ja"}

For more information on the languages Oracle Universal Installer supports, see the Product Language Selections section.

Note:
The SELECTED_LANGUAGES variable is only generated when more than one language is available.

TOPLEVEL_COMPONENT

This parameter is the name of the component (products) and the version as a string list. You must enter a value for TOPLEVEL_COMPONENT.

Usually, the components are represented with a pair of strings: the first one representing the internal name, the second representing the version.

For example, RDBMS 11.2. may be represented as {"oracle.rdbms","11.2.0.0.0"}.

UNIX_GROUP_NAME

This parameter is the UNIX group name to be set for the inventory on UNIX platforms.

Note: The UNIX group name is used for first-time installations only.

3.5 Installing with a Response File

Many Oracle software products provide tools and procedures for running Oracle Universal Installer from the command line without displaying Oracle Universal Installer screens or responding to questions during the installation.

These are called silent installations. Instead of prompting you to select a series of installation options, Oracle Universal Installer installs the software using a predefined set of options. These options are stored in a response file (.rsp).

Consider the following information about response files:

- If your product installation includes a response file, you can find it on your stage (CD-ROM) under the <root of CD>/response directory.

- You can modify the response file for your Oracle product to customize an installation for your organization. See Modifying a Response File for more information.

- If you start Oracle Universal Installer from the command line, see Using Oracle Universal Installer Exit Codes.

The following sections describe how to specify a response file when you start Oracle Universal Installer.

Note:
If you attempt to perform a silent installation on a UNIX computer where no Oracle products have been installed, you will receive an error message. Before you can perform a silent installation on such a computer, you must first run the script oraInstRoot.sh, which is saved in the /oraInventory directory. You must run this script with root privileges. This enables Oracle Universal Installer to set up the Central Inventory on a clean host.
See the Oracle Universal Installer Inventory section for more information on the Central Inventory.

The following topics are covered:

- Specifying a Response File

- Optional Parameters When Specifying a Response File

- Setting Response File Variables From the Command Line

3.5.1 Specifying a Response File

To start Oracle Universal Installer and specify the response file, enter the following command at the command line in the directory where the executable file is installed:

setup.exe -responseFile <filename> <optional_parameters> (on Windows)
./launch -responseFile <filename> <optional_parameters> (on UNIX)

Note:
You must specify the complete responseFile path. If you do not, Oracle Universal Installer assumes the location to be relative to the oraparam.ini associated with the launched Oracle Universal Installer.

For help on command line usage, enter the following at the command line in the directory where the executable file is stored:

setup -help (on Windows)
./launch -help (on UNIX)

In Windows, when you execute setup -help, a new command window appears, with the "Preparing to launch..." message. A moment later, the help information appears in that window.

3.5.2 Optional Parameters When Specifying a Response File

Optional parameters you can use with the -responseFile option are:

- -nowelcome — Use the -nowelcome option with the -responseFile option to suppress the Welcome dialog that appears during installation.

- -silent — Use the -silent option with the -responseFile option to run Oracle Universal Installer in complete silent mode. Note that the Welcome dialog is suppressed automatically.

- -formCluster — Use the -formCluster option for Oracle Clusterware installations to specify the cluster.

Note that when you specify the -silent option, but no values are specified to a particular variable in a dialog, the installer stops. The success or failure of the installation when you specify this option is generated as follows:

- In a file named silentInstall<timestamp>.log for hosts without an Oracle inventory. This file is generated in the /tmp directory on UNIX and the directory specified by the variable TEMP on Windows platforms.

- In the inventory logs directory for hosts that already had an inventory.

Note:
Using the -nowelcome option with the -silent option is unnecessary since the Welcome screen does not appear when you use the -silent option.

3.5.3 Setting Response File Variables From the Command Line

With Oracle Universal Installer 2.1 and higher, you can specify the value of certain variables when you start Oracle Universal Installer from the command line. Specifically, you can specify session and component variables. For specific information about the format and organization of response files, see Modifying a Response File.

When you specify the value of a variable on the command line, that value overrides the value of the variable if it is defined in the response file.

3.5.3.1 Specifying the Value of a Session Variable

To specify the value of a session variable, use the following command syntax:

./launch session:<variable_name>=<value> (on UNIX)
setup.exe session:<variable_name>=<value> (on Windows)

For example, to install English and French files:

./launch session:COMPONENT_LANGUAGES="{"en","fr"}" (on UNIX)
setup.exe session:COMPONENT_LANGUAGES="{"en","fr"}" (on Windows)

Note that the "session:" tag is optional and is used mainly to remove any possible ambiguity.

3.5.3.2 Specifying the Value of a Component Variable

To specify the value of a component variable, use the following command syntax:

./launch <component_name>:<component_version>:<variable_name>=<value> (on UNIX)
setup.exe <component_name>:<component_version>:<variable_name>=<value> (on Windows)

For example, to modify the value of a variable VAR1 in version 1.1 of a component called COMP2:

./launch COMP2:1.1.0.0.0:VAR1="test" (on UNIX)
setup.exe COMP2:1.1.0.0.0:VAR1="test" (on Windows)

Note that the "<component_name>:" and "<component_version>:" optional tags are used mainly to remove any possible ambiguity. If two variables exist with the same name for different components/versions, use these tags to distinguish between them.

4 Installing Products

This chapter includes the following sections:

- Checking Prerequisites Before Installation

- Installing Oracle Products

- Deinstalling Oracle Products

- Running Oracle Universal Installer After Installation

- About Oracle Universal Installer Log Files

4.1 Checking Prerequisites Before Installation

Before installation, Oracle Universal Installer checks the environment to see whether it meets the requirements for successful installation. Early detection of problems with the system setup reduces the chances of encountering problems during installation; for instance, problems with insufficient disk space, missing patches, inappropriate hardware, and so on.

Oracle Universal Installer is required to perform all prerequisite checks defined for the installation before installing any software, whether they are Oracle Universal Installer-specific tests, or tests defined for a specific product. Specific prerequisite checks are defined for each operating system on which Oracle Universal Installer runs. All prerequisite check parameters must be defined in the oraparam.ini file (or another *.ini file that you define). All the results are logged in the install Actions<timestamp>.log file.

You can perform prerequisite checking automatically when you run the Oracle Universal Installer executable during an installation. Simply run Oracle Universal Installer to perform all predefined prerequisite checks.

Inputs to the checker are listed in the prerequisite.xml file. After running the checker, you can find the results, along with the predefined inputs, in the prerequisite_results.xml file. These files are located in the oraInventory/logs directory. You can reuse the prerequisite_results.xml file as an input file for subsequent executions of the checker.

4.2 Installing Oracle Products

The following sections describe how to start Oracle Universal Installer and install an Oracle product. Specifically, this section describes:

- Getting Help While Installing Oracle Products

- About the oraparam.ini File

- Modes of Installation

- Invocation Tools and Examples

- Installation Media

- Special Instructions for UNIX Users

4.2.1 Getting Help While Installing Oracle Products

At any time while installing your product, click Help for information about the screens specific to your installation.

Oracle Universal Installer provides two kinds of online help:

- Generic online help provided with every copy of Oracle Universal Installer.
These topics describe the screens and dialog boxes that all Oracle Universal Installer users see, regardless of the product they are installing.

- Online help specific to a particular installation (context-sensitive help).
These topics are created by the product developer and describe the screens and dialog boxes specific to the product you are installing. For example, the help topic for the Installation Types page is often a custom help topic the installation developer creates that describes the specific installation types for the product you are installing.

After you view an online help topic, choose Navigator from the Tools menu to display the navigator pane. From the navigator pane, you can browse the table of contents, select other topics, or search for a particular word or phrase in the online help.

Note:
Only generic help topics are available in the navigator or table of contents. You can only access custom help topics by clicking the Help button on the dialogs or windows they describe.

4.2.2 About the oraparam.ini File

The oraparam.ini file is the initialization file for Oracle Universal Installer. This file includes information that defines the behavior of certain Oracle Universal Installer features. Each product installation possesses a unique oraparam.ini file.

Generally, you should not have to edit the contents of this file, but in certain situations, understanding the contents of this file can help you troubleshoot problems and understand certain aspects of the Oracle Universal Installer product.

For example, for most installations, Oracle Universal Installer provides a default value on the File Locations page that points to the location of the product's installation kit or stage. This default value is stored in the oraparam.ini file. The oraparam.ini file also identifies the location of the Java Runtime Environment (JRE) required for the installation.

In the staging area, it is located in the same directory as the executable file. For example:

- For UNIX systems:

cd/<Product_Shiphome_Location>/install/solaris/runInstaller
cd/<Product_Shiphome_Location>/install/solaris/OraParam.ini

- For Windows systems:

cd\<Product_Shiphome_Location>\install\win32\setup.exe
cd\<Product_Shiphome_Location>\install\win32\OraParam.ini

In the staging area, the default OUI_LOCATION is relative to the location of the oraparam.ini file, as follows:

../../stage/

Once installed, the oraparam.ini file is located in the /oui directory.

Table 4-1 describes the parameters in the oraparam.ini file and how to use them.

Table 4-1 Parameters in the oraparam.ini Initialization File

Section/Parameter

Description

[ORACLE] Section

BOOTSTRAP_CLASSPATH

List of relative paths of files or directories to be specified in the -Xbootclasspath/a: JVM option to the target class. The separator is the OS-specific classpath separator. The paths are relative to the bootstrap base directory (pre-install) or ORACLE_HOME (post-install). Example:

BOOT_CLASSPATH=oui/modules/emocmclnt.jar:oui/modules/regexp.jar:oui/modules/xmlparserv2.jar

BOOTSTRAP_SIZE

Megabytes of free space required to bootstrap. The default depends on the platform. Example:

BOOTSTRAP_SIZE=52

COPY_THREADS

If the value is non-zero, the launcher passes the Java option -Doracle.installer.copythreads=value to the target class. The default is 0. Example:

COPY_THREADS=4

DISTRIBUTION

If TRUE (ignoring case), the context is pre-installation, and the underlying shiphome environment is assumed, with the Disk1/ directory structure. If FALSE, the context is post-installation, and the ORACLE_HOME environment and directory structure are assumed.

Default: DISTRIBUTION=FALSE

Example: DISTRIBUTION=TRUE

EXT_CLASSPATH

List of relative paths of files or directories to be prepended to the classpath of the target class. The separator is the OS-specific classpath separator. The paths are relative to the bootstrap base directory (pre-install) or ORACLE_HOME (post-install).

Enables product-specific bootstrap component artifacts to be included on the classpath of the target class. This parameter replaces EXT_JLIB. Example:

EXT_CLASSPATH=oui/modules/xyz.jar

HOTSPOT_JAVA_OPTIONS

Hotspot-specific JVM options, passed by the launcher to the JVM that executes the target class. This new parameter replaces JRE_MEMORY_OPTIONS. Example:

HOTSPOT_JAVA_OPTIONS=-mx512m -XX:MaxPermSize=256m

IBM_JAVA_OPTIONS

Options specific to the IBM JVM, passed by the launcher to the JVM that executes the target class. This parameter replaces JRE_MEMORY_OPTIONS. Example:

IBM_JAVA_OPTIONS=-Xbootclasspath/a:../stage/ext/jlib/osdt_core.jar

INSTALL_CLASS

Name of the class whose main method is invoked by the launcher. This value is superceded in some situations; for example, if the -attachHome option is specified, the launcher ignores INSTALL_CLASS.

Default: oracle.sysman.oii.oiic.OiicInstaller

Example: INSTALL_CLASS=oracle.sysman.oio.oioc.OiocOneClickInstaller

INSTALL_ONECLICK_CLASS

Name of the oneclick class, which is typically the target class if the -oneclick option is specified.

Default: oracle.sysman.oio.oioc.OiocOneClickInstaller.

JAVA_OPTIONS

Options passed by the launcher to the JVM that executes the target class. These options must be vendor independent. This parameter replaces JRE_MEMORY_OPTIONS. Example:

JAVA_OPTIONS=-mx512m

JAVA_VERSION

Minimum Java version required for executing the target class, expressed as a 2-node version.

Example: JAVA_VERSION=1.6

JROCKIT_JAVA_OPTIONS

JRockit-specific JVM options, passed by the launcher to the JVM that executes the target class. This parameter replaces JRE_MEMORY_OPTIONS.

Example: JROCKIT_JAVA_OPTIONS=-mx512m -Xverify:none

NLS_ENABLED

The launcher passes the Java option -Doracle.installer.nlsEnabled=boolean-value to the target class.

Default: TRUE

Example: NLS_ENABLED=TRUE

PLATFORM_PREREQS

If TRUE (ignoring case), the launcher executes the platform-specific prerequisite checks defined in oraparam.ini.

Default: FALSE

Example: PLATFORM_PREREQS=TRUE

SOURCE

Pre-install context: Relative path of the product-specific stage directory. The path is relative to the startup directory and is converted to an absolute path by the launcher. The launcher passes the argument -sourceLoc absolute-path to the target class.

Example: SOURCE=../../stage

USEJDKONLY

If TRUE (ignoring case), use only a JDK for launching, both in the pre-install and post-install contexts.

Default: FALSE

USEJREONLY

If TRUE (ignoring case), use only a JRE for launching, both in the pre-install and post-install contexts.

Default: FALSE

VM_TYPES

Comma-separated list of JVM types supported for launching. Legal types are JRockit, HotSpot, IBM. The launcher derives the actual type from the java.vm.name Java property.

Default: empty, meaning that any type is accepted

Example: VM_TYPES=JRockit,HotSpot.

[Certified Versions] Section

This section specifies the OS versions that are supported for installation of the product. Each value is a comma-separated list.

AIX

Example: AIX=5100,5200,5300,6100-05

Linux

OS version and vendor required for installation. Now includes IBM's Linux.

Example: Linux=redhat-3,redhat-4

HPUX

Example: HPUX=B.11.11,B.11.23

Solaris

OS versions supported for installation on Solaris, both SPARC and x86 platforms.

Example: Solaris=5.10,5.11

Windows

Example: Windows=5.1

[Generic Prereqs] Section

There are three kinds of prerequisites sections:

1. [Generic Prereqs] defines platform-independent prerequisites. There is only one such section.

2. Sections named [Solaris-5.10-required] and similar define required platform-specific prerequisites. Each supported OS platform may have its own section.

3. Sections named [Solaris-5.10-optional] and similar define optional prerequisites for each platform.

The following properties may appear in any of these sections. Some properties are evaluated only in some sections, or on specific platforms, as noted.

BUNDLE

HP-UX only.

CPU

Minimum CPU speed required for installation, in megahertz (MHz).

Example: CPU=500

FILESET

HP-UX only.

GLIBC

Minimum version of glibc required for installation. Linux only.

Example: GLIBC=2.3.2-95

GMAKE

Comma-separated list of acceptable gmake versions required for installation. IBM Linux only.

Example: GMAKE=3.81

JAVA_USE_64BIT

Comma-separated list of OUI platform names. These are platforms where a single JVM executable supports both 32-bit and 64-bit modes, and the product requires the 64-bit mode. If the currently-identified OUI platform is in this list, it is not supported.

Evaluated only in the [Generic Prereqs] section.

Example: JAVA_USE_64BIT=Solaris,Intel_Solaris32

KERNEL

The OS kernel version required for installation. Linux only.

Example: KERNEL=2.4.21

MIN_DISPLAY_COLORS

Minimum required color depth of the display device. Evaluated only in the [Generic Prereqs] section, if the installation is not silent.

Example: MIN_DISPLAY_COLORS=256

PACKAGES

Comma-separated list of OS packages, all of which are required for installation. UNIX only.

Example: PACKAGES=SUNWPython,SUNWTcl

PATCH

Comma-separated list of OS patches, all of which are required for installation. UNIX only.

Example: PATCHES=139555-08,125275-01

PERL

Comma-separated list of Perl versions, any one of which is required for installation. IBM Linux only.

Example: PERL=5.6.1,5.004

PROCESSOR

Comma-separated list of processors, any one of which is acceptable for installation. UNIX only.

Example: PROCESSOR=sun4v

SERVICE_PACK

Service pack(s) required for installation. If the value is a comma-separated list, then any match is acceptable. If there is a single value, then it is the minimum required service pack. Windows only.

Example: SERVICE_PACK=3

SWAP_SPACE

Minimum swap space required for installation, in megabytes (MB). Evaluated only in the [Generic Prereqs] section.

Example: SWAP_SPACE=512

TEMP_SPACE

Minimum free space in the bootstrap base directory required for installation, in megabytes (MB).

Example: TEMP_SPACE=300

The following message-related properties are mentioned (and commented out) in some installed oraparam.ini files. These properties do not support localization.

CERTIFIED_VERSION_LOCATION

The location of the file containing the list of OS versions certified for this installer.

CERTIFIED_VERSION_WARN

If TRUE, emit a message that names the file specified by CERTIFIED_VERSION_LOCATION.

LOG_PATCHES_TO_CONSOLE

If TRUE, print the list of required patches to the console.

BUNDLE_FAILURE_MESSAGE
CERTIFIED_VERSION_FAILURE_MESSAGE
CPU_FAILURE_MESSAGE
MIN_DISPLAY_COLORS_FAILURE_MESSAGE
FILESET_FAILURE_MESSAGE
GLIBC_FAILURE_MESSAGE
KERNEL_FAILURE_MESSAGE
PACKAGES_FAILURE_MESSAGE
PATCHES_FAILURE_MESSAGE
PROCESSOR_FAILURE_MESSAGE
SERVICE_PACK_FAILURE_MESSAGE
SWAP_SPACE_FAILURE_MESSAGE
TEMP_SPACE_FAILURE_MESSAGE

4.2.3 Modes of Installation

You can use Oracle Universal Installer to install Oracle products in any of the three following modes:

- Interactive: Use Oracle Universal Installer's interactive mode to use the graphical user interface to walk through the installation, providing information in the installation dialogs when prompted. This method is most useful when installing a small number of products in different setups on a small number of hosts.

- Suppressed: Use Oracle Universal Installer's suppressed mode to supply the necessary information by using a combination of a response file or command line entries with certain interactive dialogs. You can choose which dialogs to suppress by supplying the information at the command line when you invoke Oracle Universal Installer. This method is most useful when an installation has a common set of parameters that can be captured in a response file, in addition to custom information that must be input by hand.

- Silent: Use Oracle Universal Installer's silent installation mode to bypass the graphical user interface and supply the necessary information in a response file. This method is most useful when installing the same product multiple times on multiple hosts. By using a response file, you can automate the installation of a product for which you know the installation parameters. For more information, see Chapter 3, "Creating and Customizing a Response File," for detailed information on using response files and installing in silent mode.

Note:
You can use the -noConsole option on the Windows platform to suppress the display of messages in the console.

4.2.4 Invocation Tools and Examples

OUI can be launched using several tools, depending on the context (pre-install or post-install) and OS platform:

Native self-extractor (native SFX)

- For installation only.

- Contains a bundled JRE or JDK, as required by the product to be installed.

- Inherently platform-specific.

- Available for a subset of the supported platforms.

Examples:

setup_wls_win32.exe
setup_wls_win64.exe
wls_linux64.bin

Sample invocations (Windows 64):

- OUI Release 12.1 and later:

setup_wls_win64.exe -mode=console -debug -logLevel finest

- OUI Release 11.2 and earlier:

unzip wls.zip
cd wls/Disk1
setup.exe -debug -logLevel finest -jreLoc "%JAVA_HOME%"

Sample invocations (Linux 64):

- OUI Release 12.1 and later:

wls_linux64.bin -debug -logLevel finest

- OUI Release 11.2 and earlier:

unzip wls.zip
cd wls/Disk1
./launch -jreLoc $JAVA_HOME -debug -logLevel finest

Generic self-extractor (generic SFX)

- For installation only.

- Requires a previously installed JVM.

- Usable on any supported platform.

Sample invocations:

- OUI Release 12.1 and later (any platform):

java -jar wls_generic.jar -debug -logLevel finest

- OUI Release 12.1 and later (to start a 64-bit installation with a JVM that supports both 32- and 64-bits):

java -d64 -jar wls_generic.jar -debug -logLevel finest

- OUI Release 11.2 and earlier (UNIX):

unzip wls.zip
cd wls/Disk1
./launch -jreLoc $JAVA_HOME -debug -logLevel finest

- OUI Release 11.2 and earlier (Windows):

unzip wls.zip
cd wls\Disk1
setup.exe -debug -logLevel finest -jreLoc "%JAVA_HOME%"

Shiphome script or executable

- For installation only.

- Requires a previously installed JVM, specified using the -jreLoc option.

- Usable on any supported platform.

Sample invocations (Windows):

- OUI Release 12.1 and later

cd Disk1
install.exe -jreLoc c:\opt\jdk1.6.0_14 -debug

- OUI Release 11.2 and earlier:

cd Disk1
setup.exe -jreLoc c:\opt\jdk1.6.0_14 -debug

Sample invocations (UNIX):

- OUI Release 12.1 and later

cd Disk1
./install.sh -jreLoc $JAVA_HOME -debug

- OUI Release 11.2 and earlier:

cd Disk1
./launch -jreLoc $JAVA_HOME -debug

Installed ORACLE_HOME scripts or executable

- For post-installation only, from an installed ORACLE_HOME.

- Requires an installed JVM, specified explicitly using the -jreLoc option.

- Usable on any supported platform.

Sample invocations (Windows):

- OUI Release 12.1 and later

cd %ORACLE_HOME%\oui\bin
deinstall.cmd -debug

- OUI Release 11.2 and earlier:

cd %ORACLE_HOME%\oracle_common\oui\bin
setup.exe -deinstall -debug

Sample invocations (UNIX):

- OUI Release 12.1 and later

$ORACLE_HOME/oui/bin/deinstall.sh -debug

- OUI Release 11.2 and earlier:

$ORACLE_HOME/oracle_common/oui/bin/runInstaller.sh -deinstall -debug

4.2.5 Installation Media

For each of these three installation modes, you can install from three different media:

- Installing from a Single CD-ROM

- Installing from Multiple CD-ROMs

- Installing from a Staged HTTP Location

Notes:

- On Windows systems, when you start the installer from a shared drive, you need to map the shared drive and then invoke the installer from the shared drive.

- When you invoke the installation process, you should invoke it from the directory where this command is present, or you must specify the complete path.

4.2.5.1 Installing from a Single CD-ROM

While installing Oracle products contained on a single CD-ROM, start Oracle Universal Installer by running the executable file, setup.exe (Windows) or runInstaller.sh (UNIX), located in:

../install/<platform>

Where <platform> represents Win32, Win64, Oracle Solaris, Linux, and so on.

To define the invocation:

java -jar <distribution>_generic.jar

To define the invocation for self-extraction:

./<distribution>.bin

For UNIX systems, run the script by typing ./launch at the command line.

Note:
Oracle Universal Installer for Win64 functions like Oracle Universal Installer for Win32. However, the startup directory on the CD is "win64" instead of "win32." Launching Oracle Universal Installer from the Win32 directory launches Oracle Universal Installer in 32-bit mode, used for installing 32-bit software. Use win64 for installing 64-bit software.
When you install both 32-bit and 64-bit Oracle Universal Installer on a 64-bit machine, two different inventories are created and maintained. However, you cannot install 64-bit software in a 32-bit home, and vice versa.

4.2.5.2 Installing from Multiple CD-ROMs

If you are creating a multiple-CD installation on UNIX, you might need to launch runInstaller in the background using the following command:

./launch &

By launching runInstaller in the background, you can change your current directory after you launch Oracle Universal Installer, enabling you to eject the CD. (It may also help to launch runInstaller as a foreground process from a different directory.)

You may want to create a shell script that launches Oracle Universal Installer in the background and then exits. If you choose to create a shell script, remember to also pass all parameters that you passed to the shell script to runInstaller in the event that you want to install silently using a response file.

TEMP/TMP Directory

On both UNIX and Windows installations, temporary copies of Oracle Universal Installer and JRE are placed in the TEMP or TMP directory in a subdirectory named /OraInstall<timestamp> so that these applications can be launched when you change CD-ROMs. Note that temporary files are created for single-CD installations as well. On both UNIX and Windows, Oracle Universal Installer looks for %TEMP% then %TMP%. If neither is set, Oracle Universal Installer defaults to /tmp on UNIX and c:\temp on Windows.

Note:
.The TEMP/TMP directory should not be a cluster file system or a shared location.

Unmounting a CD

On UNIX, if you have trouble installing a product from multiple CD-ROMs, try using the following procedure to unmount the first CD-ROM and mount the second CD-ROM.

In most cases, the following procedure helps with any problems you experience while switching to a second CD-ROM while installing Oracle software. If you inadvertently run the installer while the current working directory is in the CD-ROM, follow these steps to mount the next CD-ROM:

1. Change to the root directory of your system and log in as the root user by using the following commands:

$ cd /
$ su root

2. Unmount and remove the CD-ROM from the drive with the following command:

# umount cdrom_mount_point_directory

3. Insert and mount the next CD-ROM into the drive by using the following command:

# mount options device_name cdrom_mount_point_directory

4. Enter the correct mount point in the Installation dialog box.

5. Click OK to continue.

4.2.5.3 Installing from a Staged HTTP Location

With Oracle Universal Installer, you can install products from the Web. You can publish your staging area from a Web server and then in the Oracle Universal Installer's Source location, specify the HTTP location for the products.xml file.

For example, you can enter:

http://www.oracle.com/product/ouiinstall/stage/products.xml

The Oracle Universal Installer recognizes a Web staging area just like a local, network, or CD-ROM stage.

System administrators of large customers who may want to deploy Oracle software to more than one target can use a combination of the Web installation and response file features:

1. Copy the staging area to a shared file system and make it accessible on the Intranet or a Web server.

2. Include predetermined response files on the same location. (Different groups of users might rely on different response files.)

3. Clients run Oracle Universal Installer locally and use the local response file that is mailed or downloaded so they can perform a silent installation.

The Web installation capability relies on some guidelines that must be followed at installation development time. Check the installation guide for your product to see if the installation of your product is certified for Web installation.

To test if your stage is Web-enabled, you can try the following procedure:

1. Copy the stage to your Web server.

2. Start the Oracle Universal Installer locally and point to the location of the products.xml file. For example:

http://smpweb.us.oracle.com/product/ouiinstall/stage/products.xml

4.2.6 Special Instructions for UNIX Users

The following sections describe special instructions that apply when you are installing certain products on a UNIX system:

Failed to Connect to Server Error

If you receive an Xlib error or a Failed to connect to Server error when you are running Oracle Universal Installer on the Solaris operating system:

1. Define the following environment variable on the host computer where you are running Oracle Universal Installer:

%setenv DISPLAY <machine name>:0.0

Where <machine name> is the name of the computer that will display Oracle Universal Installer.

2. On the computer that will display Oracle Universal Installer, enter the following command, which enables other computers to display information on the computer's monitor:

%xhost +

3. Rerun the runInstaller script after you have set the DISPLAY environment variable.

Note:
You can run Oracle Universal Installer without specifying the DISPLAY variable by running in silent mode using a response file.

Providing a UNIX Installater Location with Root Privileges

You must have root privileges to perform various installation operations on the UNIX platform. For example, you must have root privileges to be able to create the Oracle Universal Installer inventory.

If you are installing Oracle Universal Installer for the first time, you are prompted to run a shell script from another terminal window before proceeding with the installation. Oracle Universal Installer prompts you to run root.sh after installation completes only if the script is required to be run as root before configuration assistants are run. Otherwise, you are prompted to run root.sh as root later.

Note:
When running Oracle Universal Installer in silent mode, if root.sh is required prior to configuration assistants, Oracle Universal Installer skips configuration assistants during the installation. You must run root.sh as root and then run the skipped configuration assistants after the silent installation is complete.

To successfully run the required shell script:

1. Leave the Oracle Universal Installer window open and open another terminal window.

2. In the new terminal window, use the substitute user command to log in with root privileges:

su -root

3. Change directory to the Oracle home into which you are currently installing your Oracle software product.

4. Run the shell script ./root.sh.

5. When the script is finished and you are returned to the command prompt, exit from the new terminal window and return to Oracle Universal Installer to continue the installation.

Note:
Do not exit the installation to run the shell script. Exiting the installation removes this script.
You are prompted to run the script only the first time you install.

Providing a UNIX Group Name

If you are installing a product on a UNIX system, the Installer also prompts you to provide the name of the group that owns the base directory.

You must choose a UNIX group name that has permissions to update, install, and remove Oracle software. Members of this group must have write permissions to the base directory chosen.

Only users who belong to this group are able to install or remove software on this host.

4.3 Deinstalling Oracle Products

A deinstall can be performed by invoking the following scripts:

- For Windows systems:

NGHome\oui\bin\deinstall.cmd

- For UNIX systems:

NGHome/oui/bin/deinstall.sh

4.4 Running Oracle Universal Installer After Installation

The following sections describe the different ways that Oracle Universal Installer can be used after installation. Specifically, this section describes:

- Starting Oracle Universal Installer

- Command Line Arguments

- Using Oracle Universal Installer Exit Codes

- Cloning Considerations

4.4.1 Starting Oracle Universal Installer

OUI is installed in the Oracle home and is available for both Windows and UNIX under:

<Oracle home>/oui/bin

For all platforms, the executable installation file is located in the following directory:

<oui_location>/bin

A new version of Oracle Universal Installer replaces its older version.

To start Oracle Universal Installer:

- On Windows platforms, select Start, Programs, Oracle Installation Products, Oracle Universal Installer.

- On UNIX, execute the ./launch script from the directory where it is installed.
For example: if the Oracle home is /u01/app/oracle/, OUI will be located at OH/oui/u01/app/oracle/oui.

A runInstaller.sh script is also available, so that you can launch Oracle Universal Installer directly from a different directory.

When Oracle Universal Installer is first installed and run, it checks for the JRE path (the location from which it runs), using the location specified in the oraparam.ini file's JRE_LOCATION parameter. If Oracle Universal Installer cannot find the JRE specified, an error is returned.

4.4.2 Command Line Arguments

Following is the output from the runInstaller -help command, which gives you the full list of command line options and their descriptions, as well as command line variables usage:

<command> [ <option> | <option> <value> | <CommandLineVariable>=<value> ]

Table 4-2 shows the available <command> values. Table 4-3 shows the available <option> values.

Table 4-2 OUI Command Values

Command

Description

java -jar <jarfile>

Generic installer.

<product>.bin

Native installer (UNIX).

<product>.exe

Native installer (Windows).

<Oracle Home>/oui/bin/<command>.sh

Post-install utilities (UNIX).

<Oracle Home>\oui\bin\<command>.cmd

Post-install utilities (Windows).

Table 4-3 OUI Option Values

Option

Description

-silent

Use silent mode. The inputs are taken from the response file or from the command line as a list of <CommandLineVariable>=<value> pairs.

-install

Perform an installation. This is the default operation.

-noconsole

Do not allocate a console, and suppress the display of messages to the console.

Windows only.

-debug

Output debug information.

-nowait

Do not wait for the user to press Enter on the console after the operation (for example, install) is complete.

Windows only.

-ignoreSysPrereqs

Checks system prerequisites but ignores the results..

-paramFile <path>

Location of the oraparam.ini file.

-help

Display a help message showing all available commands and options.

-printtime

Log debug information about elapsed time.

-logLevel <level>

Omit log messages whose priority level is less than <level>. Valid levels are: severe, warning, info, config, fine, finer, finest.

-invPtrLoc <path of oraInst.loc>

Use the specified inventory pointer file instead of the default. The inventory pointer file contains:

inventory_loc=<location of central inventory>
inst_group=<UNIX group name>

UNIX only.

-executeSysPrereqs

Checks the basic prerequisites for OUI itself (called system prerequisites, as opposed to prerequisites for the product being installed). After these checks are performed, the installer exits without installing the product..

-printdiskusage

Log debug information about disk usage.

-force

Allow silent mode installation into a non-empty directory.

-responseFile <path>

Location of the response file containing input for OUI.

-printmemory

Log debug information about memory usage.

4.4.3 Using Oracle Universal Installer Exit Codes

If you are starting and stopping Oracle Universal Installer programmatically (for example, by invoking Oracle Universal Installer using a response file), you may need to consider the exit codes Oracle Universal Installer generates, and perform a particular action depending on the code Oracle Universal Installer returns.

Oracle Universal Installer returns one of the following exit codes:

Code

Description

0

All installations were successful.

1

All installations were successful, but some optional configuration tools failed.

2

Local installations were successful, but some remote operations failed.

3

All installations were successful, but some recommended configuration tools failed.

6

The installation was successful after you proceeded by disregarding a few prerequisite checks or warnings.

-1

At least one installation failed.

-2

The installation failed. One or more validation of variables failed.

-3

The attempted installation encountered a prerequisite failure. Some of the optional prerequisites have not been met. See the logs for details.
You can ignore this code if the prerequisite is optional.

-4

The installation was stopped.

Note that:

- This feature does not work if Oracle Universal Installer is running in "bootstrap" mode. In this case, the installation process launches the JRE process and returns immediately without waiting for the exit code. Oracle Universal Installer runs in "bootstrap" mode if the following line exists in the oraparam.ini file:

BOOTSTRAP=TRUE

- If you exit without installing any products (for example, if you exit from the "Welcome" screen), the exit code is -1.

4.4.4 Cloning Considerations

You can copy an existing Oracle home, then configure it for its new environment. This process is called cloning. The cloning process uses the NG OUI cloning functionality. This operation is driven by a set of scripts and add-ons that are included in the respective Oracle software. The cloning process has two phases:

- Phase 1: Preparing the Source Oracle Home

- Phase 2: Cloning the Destination Home

Note:
Patching and deinstallation on a cloned Oracle home act the same as a regularly installed Oracle home. You can directly patch a cloned installation.

See Chapter 5, "Cloning Oracle Software," for details to clone an Oracle home.

4.5 About Oracle Universal Installer Log Files

When you install or deinstall products using Oracle Universal Installer, important information about each installation is saved not only in the inventory, but also in a series of log files located in the following directory:

$ORACLE_HOME/cfgtoollogs

You can use these log files to troubleshoot installation problems. These files are also crucial for removing and configuring the various software components you install on your Windows or UNIX system. Oracle Universal Installer displays the name and location of the current session's log file on the Install page. Each installation or configuration utility provides a separate folder containing the installActions<timestamp>.log files inside the $ORACLE_HOME/cfgtoollogs folder.

Many exceptions can possibly occur and consequently appear in a log file, depending on the product, as shown in the following example:

globalVarQueries2.1.0.4.1  getGlobalVariable[[.variable = oracle.assistants.server.launchNETCA]]
[2009-09-07T01:17:46.646+00:00] [OUI] [NOTIFICATION] [] [OUI] [tid: 21]
[ecid: 0000IEI4dFFDScApJ^^Ayf1Ad5uS00000C,0]
[[Query Exception: VariableNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException]]

You can ignore the exception traces in the logs if the installation has subsequently continued.

Action logs are written on a per-session basis. The installer action log is created each time a new install session is started. What each action does and whether it occurred during installation or deinstallation is logged for every action in the installer action log. Each session is saved in the installActionstime_stamp.log file, where time_stamp is of the form:

yyyy-mm-dd_hh-mm-ss[AM|PM].log

The .err and .out files also use the time stamp in their file names, making it easier to keep track of these files for each session.

Product Removal Logs vs. Action Logs

Note that the logs used to remove products are different from the installActions<timestamp>.log file generated during the installation process. The installActions<timestamp>.log is easier to read and can be used to view the operations performed during installation.

Exceptions

Many exceptions can possibly occur and consequently appear in a log file, depending on the product, as shown in the following example:

globalVarQueries2.1.0.4.1  getGlobalVariable[[.variable = oracle.assistants.server.launchNETCA]]
[2009-09-07T01:17:46.646+00:00] [OUI] [NOTIFICATION] [] [OUI] [tid: 21]
[ecid: 0000IEI4dFFDScApJ^^Ayf1Ad5uS00000C,0]
[[Query Exception: VariableNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException]]

You do not need to take any action if the text that follows the exception message appears to ignore the exception.

yyyy-mm-dd_hh-mm-ss[AM|PM]

5 Cloning Oracle Software

Cloning is the process of copying an existing Oracle installation to a different location and updating the copied bits to work in the new environment. The changes made by one-off patches, which are applied on the source Oracle home, would also be present after the clone operation. The source and the destination path (host to be cloned) need not be the same. During cloning, NG OUI replays the actions that were run to install the home. The cloning process is similar to the installation process except that it runs the actions in a special mode that is referred to as clone mode.

This chapter provides information about Oracle cloning using Oracle Universal Installer (OUI). This chapter contains the following topics:

- Cloning Features and Benefits

- How Cloning Works

- Cloning an NG Oracle Home

5.1 Cloning Features and Benefits

Some situations in which cloning is useful are:

- Creating an installation that is a copy of a production, test, or development installation. Cloning enables you to create a new installation with all patches applied to it in a single step. This is in contrast with going through the installation process by performing separate steps to install, configure, and patch the installation.

- Rapidly deploying an instance and the applications that it hosts.

- Preparing an Oracle home and deploying it to many hosts.

NG OUI Cloning is more beneficial than using the tarball approach because cloning configures the Central Inventory and the Oracle home inventory in the cloned home. Cloning also makes the home manageable and allows the paths in the cloned home and the target home to be different.

5.2 How Cloning Works

The cloning process works by copying all of the files from the source Oracle home to the destination Oracle home. Thus, any files used by the source instance that are located outside the source Oracle home's directory structure are not copied to the destination location.

The cloned installation behaves the same as the source installation. For example, the cloned Oracle home can be removed using NG OUI or patched using OPatch. You can also use the cloned Oracle home as the source for another cloning operation. You can create a cloned copy of a test, development, or production installation by using the command-line cloning scripts. The default cloning procedure is adequate for most usage cases. However, you can also customize various aspects of cloning, for example, to specify custom port assignments, or to preserve custom settings.

The size of the binaries at the source and the destination may differ because these are relinked as part of the clone operation and the operating system patch levels may also differ between these two locations. Additionally, the number of files in the cloned home would increase because several files copied from the source, specifically those being instantiated, are backed up as part of the clone operation.

5.3 Cloning an NG Oracle Home

The cloning process uses the NG OUI cloning functionality. This operation is driven by a set of scripts and add-ons that are included in the respective Oracle software. The cloning process has two phases:

- Phase 1: Preparing the Source Oracle Home

- Phase 2: Cloning the Destination Home

5.3.1 Phase 1: Preparing the Source Oracle Home

To prepare the source Oracle home to be cloned, archive and compress the source Oracle home using your preferred archiving tool. For example, you can use WinZip on Microsoft Windows system computers and tar or gzip on UNIX. Regardless of your preferred method, you must make sure that it preserves the permissions and file timestamps.

The following example shows how to archive and compress the source for various UNIX platforms:

- For Oracle Solaris or Linux systems:

tar cpfX - excludeListFile . | compress -fv > temp_dir/archiveName.tar.Z

- For AIX or HPUX systems:

tar cpf - . | compress -fv > temp_dir/archiveName.tar.Z

5.3.2 Phase 2: Cloning the Destination Home

To clone the Oracle home:

1. Create a new directory for the cloned Oracle home:

mkdir Destination_oracle_homecd

2. Unarchive the Oracle home on the destination system:

- For Oracle Solaris or Linux systems:

temp_dir/archiveName.tar.Z | tar xBpf

- For AIX or HPUX systems:

temp_dir/archiveName.tar.Z | tar xpf

3. Use the -clone option to complete the cloning process:

- For Oracle Solaris, Linux, and other UNIX systems:

Destination_oracle_home/oui/bin/launch.sh -clone -silent ORACLE_HOME= <Destination_oracle_home>

- For Windows systems:

Destination_oracle_home\oui\bin\launch.cmd -clone -silent ORACLE_HOME= <Destination_oracle_home>

Optional parameters:

- ORACLE_HOME_NAME= < Destination_oracle_home name>

- -responseFile <response file location>

Note:
NG OUI supports all the parameters used during installation in cloning.
It also supports response file inputs.

6 Oracle Internationalization and Translation

The following sections describe how Oracle Universal Installer supports multiple languages and internationalization:

- Installation Language Dialogs

- Product Language Selections

- Language Add-on

6.1 Installation Language Dialogs

Oracle Universal Installer runs in the language of the operating system. Oracle Universal Installer uses the language that Java detects, the system locale value, and sets that to the default language. The Oracle Universal Installer dialogs are displayed in this language if available. If specific Oracle Universal Installer dialogs are not translated in the language of the operating system, these dialogs are shown in English.

Oracle Universal Installer displays the translated GUI only if the variable NLS_ENABLED has been set to TRUE in the oraparam.ini file. If the NLS_ENABLED variable is set to FALSE, all text is shown in English.

6.2 Product Language Selections

If multiple languages are defined for the products installed, Oracle Universal Installer enables language selection for all installation types through the Languages button (shown on the Available Products page when there is more than one top-level component).

Note:
If there is only one top-level component, the Languages button is shown on the Install Types page.
If the staging area has only one top-level component with only one installation type, the button is not shown and a Language Selection dialog is displayed later in the installation. You can also control the selected languages by setting the SELECTED_LANGUAGES variable in a response file or through the command line:

setup.exe SELECTED_LANGUAGES={"fr","de"}

The language selections are for the top-level component being installed. A top-level component is the product selected on the Products Selection dialog, one per installation session. If any sub-components (not top-level) do not have files defined for the language you select, only English only is installed. The English files are always installed for all components, regardless of user selection or operating system language.

During installation, Oracle Universal Installer examines the language list of each file and file group to determine which files need to be copied.

The Oracle Universal Installer product is translated into nine languages, as shown in Table 6-1, and includes translations for all generic Oracle Universal Installer dialogs. Note that any custom dialogs and product-specific information that are part of your installations must be translated and staged independently.

Table 6-1 Oracle Universal Installer Translated Languages

Language

Abbreviation

French

fr

Brazilian Portuguese

pt_BR

German

de

Italian

it

Japanese

ja

Korean

ko

Simplified Chinese

zh_CN

Spanish

es

Traditional Chinese

zh_TW

6.3 Language Add-on

Oracle Universal Installer supports post-installation language translation additions. To get a version of an Oracle product with a particular language up and running, you need to invoke Oracle Universal Installer in -addLangs mode.

Perform the following steps to change the language of an installation using Oracle Universal Installer:

1. Execute the following command:

./launch -addLangs

A welcome page with a language add-on specific message appears.

2. Click Next. The Specify Home Details page appears.

3. Select the name and full path of the home containing the product to which you want to add languages and click Next. The Language Selection page appears.

4. Select the languages for which you want your Oracle products to be upgraded and click Next. A summary page displaying a snapshot of your preferences appears.

5. Review your preferences and click Install. After the languages are successfully updated, the End of Language Upgradation page appears.

6. Click Exit.

7 Inventory Utilities

The inventory utilities are designed to aid in the analysis of the contents of an Oracle Home. These utilities provide the ability to output basic information about an specific Oracle Home, or compare the contents of two different Oracle Homes, using a variety of output formats.

The following inventory utilities are described:

- Inventory View

- Inventory Compare

7.1 Inventory View

This utility provides the ability to output the following information from an Oracle Home:

- Distributions: Name and version.

- Feature-sets: Name and version.

- Components: Name and version.

- Patches: Patch ID and Unique ID.

The information can be presented in the following formats:

- Console Output

- CSV File Output

- XML File Output

See Inventory View Utility Usage for the available parameters for the inventory view utility.

7.1.1 Console Output

This mode outputs the information to the console in a format that allows the viewer to identify the hierarchy of the distributions, feature-sets, components, and patches. Example 7-1 show a sample of how this output format looks:

Example 7-1 Inventory View Console Output Example

Oracle Home: D:\P4\src\gdr\1.0\src\test\xml\TestInventory\oracle_home
Distribution: ComponentArchiveInstallerDistribution 1.0.0.0
FeatureSet: ComponentArchiveInstallerFeature 1.0.0.0
Component: test.dirs 12.0.0.0.0
Patch: ID: test.patch UID: 1
Component: test.dirs.multi 12.0.0.0.0
Component: test.files 12.0.0.0.0
Component: test.files.multi 12.0.0.0.0
Component: test.filters 12.0.0.0.0
Component: test.rules 12.0.0.0.0
Distribution: TestDistribution 1.0.0.0
FeatureSet: TestFeature 1.0.0.0
Component: test.component 12.0.0.0.0
Patch: ID: test.patch.2 UID: 2

7.1.2 CSV File Output

This mode outputs the information to a .csv file. The first column contains the identifiers for the structure being presented (distribution, feature-set, component or patch) followed by the name and version, or IDs, depending on the structure. Figure 7-1 shows an example of how this output format looks:

Figure 7-1 Inventory View CSV File Output Example

7.1.3 XML File Output

This mode outputs the information to a XML file. Figure 7-2 shows an example of how this output format looks:

Figure 7-2 Inventory View XML File Output Example

7.1.4 Inventory View Utility Usage

An executable file will be installed as part of any OUI distribution in the <OracleHome>/oui/bin directory. The command that must be called differs between Windows and Unix-based systems:

- For Windows:

viewInventory.cmd

- For Unix-based systems (such as, Oracle Solaris):

viewInventory.sh

Table 7-1 shows the parameters the command accepts:

Table 7-1 Inventory View Parameters

Parameter

Description

-oracle_home

Not required. The complete path of the Oracle Home to analyze. If not present, then Inventory View will assume you are under an oracle home and will view it.

-output_format

Not required. The <xml, csv or report> identifier indicates the output format for this operation. For example, xml and csv will create an output file of that format, and a report will print to the console.

If this parameter is not specified, the output will be automatically detected based on the output_file parameter.

-output_file

Not required. Only used when the desired output file should be xml or csv. If this parameter is not specified, the output will be printed in the console.

7.2 Inventory Compare

This utility provides the ability to compare two oracle homes and output the information described below:

- Oracle Home: It displays the oracle home directory.

- Distributions: Name and version.

- Feature-sets: Name and version.

- Components: Name and version.

- Patches: Patch ID and Unique ID.

All of the artifacts will be listed and those that are different between the two oracle home directories will be indicated with either an oh1 or oh2 identifier.

The information can be presented in the following formats:

- Console Output

- CSV File Output

- XML File Output

See Inventory Compare Utility Usage for the available parameters for the inventory compare utility.

7.2.1 Console Output

This mode outputs the information to the console in a format that allows the viewer to identify the hierarchy of the distributions, feature-sets, components, and patches. Example 7-2 shows a sample output of the successful execution of an inventory compare:

Example 7-2 Inventory Compare Console Output Example

Oracle Home1: D:\ade\depot\src\gdr\1.0\src\test\xml\TestInventory\oh_more
Oracle Home2: D:\ade\depot\src\gdr\1.0\src\test\xml\TestInventory\oh_less
Distribution: ComponentArchiveInstallerDistribution 1.0.0.0
FeatureSet: ComponentArchiveInstallerFeature 1.0.0.0
Component: test.dirs 12.0.0.0.0
Patch:  ID:1234 UID:4321
Component: test.dirs.multi 12.0.0.0.0,oh1
Component: test.files 12.0.0.0.0,oh1
Component: test.files.multi 12.0.0.0.0,oh1
Component: test.filters 12.0.0.0.0
Component: test.rules 12.0.0.0.0
Distribution: TestDistribution 1.0.0.0,oh1
FeatureSet: TestFeature 1.0.0.0,oh1
Component: test.component 12.0.0.0.0,oh1
Patch:  ID:12345 UID:54321,oh1

7.2.2 CSV File Output

This mode outputs the information to a .csv file. The first column contains the identifiers for the structure being presented (oracle-home, distribution, feature-set, component, or patch) followed by the name and version, or IDs, depending on the structure. The last column shows the difference with an oh1 or oh2 identifier. Figure 7-3 shows an example of how this output format looks:

Figure 7-3 Inventory Compare CSV File Output Example

7.2.3 XML File Output

This mode outputs the information to a XML file. Figure 7-4 shows an example of how this output format looks:

Note:
The oh-diff attribute will contain the information about the difference between oracle homes. When both oracle homes are having the same artifact, it will contain the value both.
This value will be used only in this xml file output. In the other formats, it is assumed that not showing it means that both oracle homes have the same artifact.

Figure 7-4 Inventory Compare XML File Output Example

7.2.4 Inventory Compare Utility Usage

An executable file will be installed as part of any OUI distribution in the <OracleHome>/oui/bin directory. The command that must be called differs between Windows and Unix-based systems:

- For Windows:

compareInventory.cmd

- For Unix-based systems:

compareInventory.sh

These are the parameters the command accepts:

Table 7-2 Inventory Compare Parameters

Parameter

Description

-oracle_home1

Required. The complete path of the Oracle Home1 to compare with, it can be either an xml file or a directory.

-oracle_home2

Required. The complete path of the Oracle Home2 to compare with, it can be either an xml file or a directory.

-input_type1

Not required. A <dir or xml> is used to specify the source for the first oracle home. If this parameter is not provided, then Inventory Compare will automatically detect it.

-input_type2

Not required. A <dir or xml> is used to specify the source for the second oracle home. If this parameter is not provided, then Inventory Compare will automatically detect it.

-output_file

Not required. Only used when the desired output is either xml or csv. The file will be generated in the specified location and with the given name.

If this parameter is not specified, then the inventory compare will be output to the console.

If this parameter is provided, then the output file will be generated based on the extension.

-help

Prints usage instructions.

A Troubleshooting and Debugging OUI

This appendix is organized into the following troubleshooting sections:

- Oracle Universal Installer Errors

- Using SSH

- Other Tips

- Frequently Asked Questions

- Debugging Mechanisms in Oracle Universal Installer

A.1 Oracle Universal Installer Errors

Refer to the release notes for information on any Oracle Universal Installer limitations for a particular version.

The most common Oracle Universal Installer errors are listed below:

- Out of "temp" space
Make sure you have enough space in the default TEMP or TMP directory. Otherwise, the installation will not succeed. The amount of space required depends on the product being installed.

Note:
On UNIX and Windows, Oracle Universal Installer looks for %TEMP% then %TMP%. If neither is set, Oracle Universal Installer will default to /tmp on UNIX and c:\temp on Windows.

- Incomplete stage and missing files in file groups
Make sure you have a good staging area. You may have incorrectly copied the staging area from the CD to the hard disk.

- Exceptions from action libraries:

- NT Services, if a service is already started

- File permissions

- UNCAUGHT_RUNTIME exception when you try to install the product on your machine
This is a blanket error catch that catches any run-time errors like NullPointers from libraries. Check if the temp\OraInstall\<timestamp>.err has any stack trace. You will need to call support to debug the staging area.

A.2 Using SSH

SSH sets up a connection with remote host, using username and password, and runs commands that are called by the server.

During this process if any user profile file gets loaded, then the ssh output of the command gets corrupted.

Currently, there is no way to handle this; therefore, it is recommended for users to not have scripts in their profile files which execute each time an ssh connection is set up.

A.3 Other Tips

The following tips may help you to troubleshoot problems:

- Make sure the correct version of the JRE is specified in the PATH.

- You can use the following debugging options in the runInstaller command:

- -printdiskusage
Logs debug information for disk usage.

- -printmemory
Logs debug information for memory usage.

- -printtime
Logs debug information for time usage.

- If Java cannot run applications from a Sun machine on an NCD X terminal (Oracle Universal Installer does not start), remove the following file:

$JAVA_HOME/lib/font.properties

- If you are deleting an Oracle home manually without using Oracle Universal Installer, the products remain registered with Oracle Universal Installer. You must then simulate a de-install so that all Oracle Universal Installer references are removed.

- If the installation is canceled:

- Products will not be registered with Oracle Universal Installer.

- Some files may have been copied, depending on when you issued the cancellation.

X terminal emulators that were tested with Oracle Universal Installer are listed in the following sections.

A.3.1 Troubleshooting Third-Party Products

This section describes some common troubleshooting techniques for third-party products.

Exceed

There is a known compatibility issue that Hummingbird has identified to be a problem with Exceed. You can fix it by going into XConfig/Screen Definition/Screen 0 and changing Window Manager from "Default to Native" to "Native." Figure A-1 shows the proper setup.

Figure A-1 Setting Exceed's Window Manager to "Native"

Another known issue where Exceed fails to recognize fonts is documented at the following site:

http://developer.java.sun.com/developer/bugParade/bugs/4262023.html

Reflection X

- Refection X 6.2+: Select Settings/Window Manager/ Default Local Window Manager/ Reflection Window Manager. You may also have to select "X terminal desktop."

- Reflection X 6.0: Select Connection/New XDMCP Connection/Connection Settings/Direct method/ type host destination and click Connect.

Tarantella

There is a known problem when using Tarantella to send DISPLAY to your Windows system, for instance, when using hosted UNIX systems. The bottoms of some Oracle Universal Installer screens may appear truncated, with buttons not visible. The problem occurs only when you use an individual Tarantella terminal window so that the Oracle Universal Installer window appears alone without a broader X-windowing environment.

To work around this problem, do one of the following:

- Use keyboard shortcuts to invoke these commands:

- Use Alt-N for Next to move to the next screen.

- On the summary page, use Alt-I to start the installation.

- Use the Window Manager window in Tarantella, which displays the entire screen as if it were a UNIX monitor. Installer dialogs will appear properly in Window Manager.

A.4 Frequently Asked Questions

This section answers the frequently asked questions for Oracle Universal Installer.

On Windows, when I run Oracle Universal Installer, it is not invoked.

This may occur because some system resources are being held by some services. If you stop these services, Oracle Universal Installer can be invoked.

To run Oracle Universal Installer again, execute the following command:

setup -J-Dsun.java2d.noddraw=true -Dsun.awt.nopixfmt=true

When I start Oracle Universal Installer from any location, after setting the PATH environment variable, I receive an error that reads "Could not read any NLS message catalogue!". What do I do?

Oracle Universal Installer needs some files in the directory where the installation process is running. So, when you invoke the installation, you should invoke it from the directory where this command is present, or you must specify the complete path.

I have lost my Central Inventory, but have a valid Oracle home(s). What do I do?

Oracle Universal Installer enables you to set up the Central Inventory or register an existing ORACLE_HOME with the Central Inventory in case of inventory corruption or loss. You need to execute the command with the -attachHome option. For more information, see section Creating the Central Inventory.

I want to deploy multiple Oracle home(s) from an existing Oracle home. How do I do this?

Oracle Universal Installer creates Oracle homes during Oracle software installation. To deploy multiple Oracle homes using an existing one, you need to clone the Oracle home. For more information on cloning and mass deployment, see Chapter 5, "Cloning Oracle Software."

I have lost my Oracle home inventory (comps.xml). What can I do?

Oracle recommends backing up the inventory when an Oracle home is installed or removed. Ensure that you back up the comps.xml that has the latest time-stamp. For more information on backing up the inventory, see Backing up the Central Inventory.

When your Oracle home inventory is corrupted or lost, you can restore from the backup or you can install the Oracle home from an identical installation.

When I run the configuration assistants, they fail. What do I do?

To recover from this problem, rename the configToolAllCommands and configToolFailedCommands files as follows:

- In UNIX, rename the configToolAllCommands and configToolFailedCommands files located in the OracleHome/cfgtoollogs/ directory to configToolAllCommands.sh and configToolFailedCommands.sh respectively and execute them.

- In Windows, rename the configToolAllCommands and configToolFailedCommands files located in the OracleHome/cfgtoollogs/ directory to configToolAllCommands.bat and configToolFailedCommands.bat respectively and execute them.

ConfigToolAllCommands(.sh/.bat) is used when the installation was done with a -noConfig option and you want to run all the configuration assistants in standalone mode, outside the OUI context.

ConfigToolFailedCommands(.sh/.bat) is used when the install was done with failed configuration assistants and you want to run only the failed configuration assistants later in standalone mode, outside the OUI context.

When I apply a patchset or an interim patch, the installer tries to propagate to a node that I disconnected a long time ago. What do I do?

This may occur because the Oracle home is present in the Central Inventory.

Oracle Universal Installer enables you to remove the Oracle home from the Central Inventory in cases where the Oracle home is uninstalled. To remove the Oracle home, you need to execute runInstaller with the -detachHome option. You can also completely remove the Central Inventory to remove traces of log files. For more information, see the section Detaching Oracle Homes from the Central Inventory.

When I apply a patchset or an interim patch, the patch is not propagated to some of my Oracle Real Application Clusters nodes. What do I do?

In an Oracle Real Application Clusters environment, the inventory contains a list of nodes associated with an Oracle home. It is important that during the application of a patchset or an interim patch, the inventory is correctly populated with the list of nodes. If the inventory is not correctly populated with values, the patch is propagated only to some of the nodes in the cluster.

Oracle Universal Installer enables you to update inventory.xml with the nodes available in the cluster using the -updateNodeList option in Oracle Universal Installer.

What if I just want to update the inventory without reapplying a one-off patch?

The OPatch addpatch.pl tool enables you to update the inventory with a given one-off patch without actually reapplying it to the Oracle home. Use this tool if you are certain that the patch is present in the Oracle home but not in the inventory.

You can download it from My Oracle Support at patch number 4321390 to just add the patch to the inventory. After using this option, opatch lsinventory shows the one-off patch information along with other installed one-offs.

On two separate occasions, I experienced a corrupt inventory and a failed installation. Does OUI provide a backup facility I could use before I try to install again?

OUI provides automated backups for the Central Inventory and Oracle home Inventory. For more information, see Automated Inventory Backups.

A.5 Debugging Mechanisms in Oracle Universal Installer

Oracle provides the following types of debugging mechanisms:

- Installation Log

- Automated Inventory Backups

A.5.1 Installation Log

During the installation, Oracle Universal Installer writes a text file that contains information on:

- Variable settings

- Action calls

- Queries

- Exception information

The log of installation actions is written to a file named installActions<date>.log, located in the <oraInventory>/logs directory. The oraInstall<timestamp>.err and oraInstall<timestamp>.out files are also created and stored in the same logs directory. The .log, .err, and .out files for a particular session will be named with the same timestamp.

The installation log is used for debugging purposes only. All actions, queries, everything that happens during the installation, and all modifications to the target host are logged in the file.

Example A-1 shows a sample file:

Example A-1 Installation Actions File

Using paramFile: /scratch/cd/Disk1/install/oraparam.ini

Checking swap space: must be greater than 500 MB.   Actual 9810 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 65536    Passed

The commandline for unzip:
/scratch/sandgoya/cd/Disk1/install/unzip -qqqo ../stage/Components/oracle.swd.jre/1.5.0.11.0/1/DataFiles/\*.jar -d /tmp/OraInstall2012-10-04_12-48-35AM
The commandline for unzip:
/scratch/sandgoya/cd/Disk1/install/unzip -qqqo ../stage/Components/oracle.swd.oui/11.2.0.4.0/1/DataFiles/\*.jar -d /tmp/OraInstall2012-10-04_12-48-35AM
The commandline for unzip:
/scratch/sandgoya/cd/Disk1/install/unzip -qqqo ../stage/Components/oracle.swd.oui.core/11.2.0.4.0/1/DataFiles/\*.jar -d /tmp/OraInstall2012-10-04_12-48-35AM

The number of files bootstrapped for the jre is 1045.

The number of files bootstrapped for the oui is 224.
No umask is available from oraparam.ini. Using the default value '007'.

Execvp of the child jre : the cmdline is /tmp/OraInstall2012-10-04_12-48-35AM/jre/1.5.0/bin/java, and the argv is
/tmp/OraInstall2012-10-04_12-48-35AM/jre/1.5.0/bin/java
-Doracle.installer.library_loc=/tmp/OraInstall2012-10-04_12-48-35AM/oui/lib/linux64
-Doracle.installer.oui_loc=/tmp/OraInstall2012-10-04_12-48-35AM/oui
-Doracle.installer.bootstrap=TRUE
-Doracle.installer.startup_location=/scratch/sandgoya/cd/Disk1/install
-Doracle.installer.jre_loc=/tmp/OraInstall2012-10-04_12-48-35AM/jre/1.5.0
-Doracle.installer.nlsEnabled="TRUE"
-Doracle.installer.prereqConfigLoc=
-Doracle.installer.unixVersion=2.6.18-308.0.0.0.1.el5xen
-mx96m
-cp
/tmp/OraInstall2012-10-04_12-48-35AM::/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/OraInstaller.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/oneclick.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/xmlparserv2.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/share.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/OraInstallerNet.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/emCfg.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/emocmutl.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/OraPrereq.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/jsch.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/ssh.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/remoteinterfaces.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/http_client.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/OraSuiteInstaller.jar:../stage/Components/oracle.swd.opatch/11.2.0.4.0/1/DataFiles/jlib/opatch.jar:../stage/Components/oracle.swd.opatch/11.2.0.4.0/1/DataFiles/jlib/opatchactions.jar:../stage/Components/oracle.swd.opatch/11.2.0.4.0/1/DataFiles/jlib/opatchprereq.jar:../stage/Components/oracle.swd.opatch/11.2.0.4.0/1/DataFiles/jlib/opatchutil.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/OraCheckPoint.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstImages.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_de.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_es.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_fr.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_it.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_ja.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_ko.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_pt_BR.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_zh_CN.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/InstHelp_zh_TW.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/oracle_ice.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/help4.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/help4-nls.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/ewt3.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/ewt3-swingaccess.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/ewt3-nls.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/swingaccess.jar::/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/jewt4.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/jewt4-nls.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/orai18n-collation.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/orai18n-mapping.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/ojmisc.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/xml.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/srvm.jar:/tmp/OraInstall2012-10-04_12-48-35AM/oui/jlib/srvmasm.jar
oracle.sysman.oii.oiic.OiicInstaller
-scratchPath
/tmp/OraInstall2012-10-04_12-48-35AM
-sourceLoc
/scratch/sandgoya/cd/Disk1/install/../stage/products.xml
-sourceType
network
-timestamp
2012-10-04_12-48-35AM
INFO: Environment Variables:

INFO:   ORACLE_HOME =

INFO:   PATH = /bin:/usr/bin:/usr/dev_infra/platform/bin:/usr/dev_infra/generic/bin:/usr/local/bin:/usr/X11R6/bin:/usr/local/ade/bin

INFO:   CLASSPATH =

INFO: Username:sandgoya

INFO: Install area Control created with access level  1

INFO: Unable to read the list of homes from the inventory.

INFO: Oracle Universal Installer version is 11.2.0.4.0

INFO: Setting variable 'PREREQ_CONFIG_LOCATION' to ''. Received the value from variable association.
INFO: Reader/Writer 'oracle.sysman.oii.oiic.OiicGlobalContextXMLReaderWriter' was created.
INFO:
*** Welcome Page***
INFO: Unable to read /scratch/sandgoya/oraInventory111/ContentsXML/comps.xml. Some inventory information may be lost.
INFO: Initializing install inventory
INFO: Setting up install inventory
INFO:
*** Specify Source Location Page***
INFO: Initializing OUI Shiphome access setup
INFO: Loading global variables
INFO: Loading of globalvariables complete
INFO: DefaultifyLangiages : Value of oracle.installer.defaultifyLanguages : false
INFO: fetch the file: /scratch/sandgoya/cd/Disk1/stage/shiphomeinfo.properties
INFO: fetching the pre copy and post copy script files if they exist
INFO: the /tmp/OraInstall2012-10-04_12-48-35AM/shiphomeinfo.properties doesnt exists
INFO: the /tmp/OraInstall2012-10-04_12-48-35AM/shiphomeinfo.properties doesnt exists
INFO: Done fetching the ship home info properties
INFO: Performing operation for OUI Shiphome access setup
INFO:
*** Select a Product to Install Page***
INFO: Setting the 'TopLevelComp ( ToplevelComp )' property to 'oracle.swd, 11.2.0.4.0, >0.0.0.0.0, [ 46 ][OH:2]'. Received the value from the default settings.
INFO:
*** Select Installation Type Page***
INFO: Setting the 'InstallType ( DEP_MODE )' property to 'Complete'. Received the value from the UI page.
INFO: Setting the 'TopLevelInstallType ( TLDepModes )' property to 'Complete'. Received the value from the UI page.
INFO: The selected install type is "Complete".
INFO:
*** Specify Home Details Page***
INFO: Setting the 'OracleHome ( ORACLE_HOME )' property to '/scratch/sandgoya/installations/oui111'. Received the value from the UI page.
INFO: Setting the 'OracleHomeName ( ORACLE_HOME_NAME )' property to 'OUIHome1111'. Received the value from the UI page.
INFO: Initializing OUI Oracle Home access setup
INFO: Setting variable 'ORACLE_HOME' to '/scratch/sandgoya/installations/oui111'. Received the value from the UI page.
INFO: DefaultifyLangiages : Value of oracle.installer.defaultifyLanguages : false
INFO: Setting the PROD_HOME variable of 'oracle.swd_11.2.0.4.0' to ''. Received the value from the variable calculation.
INFO: oracle.swd Product Location: Empty path specified.
INFO: Setting the PROD_HOME variable of 'oracle.swd.oil_11.2.0.4.0' to '/scratch/sandgoya/installations/oui111/osp/Libraries'. Received the value from the variable calculation.
INFO: Setting the PROD_HOME variable of 'oracle.swd.oui_11.2.0.4.0' to '/scratch/sandgoya/installations/oui111/oui'. Received the value from the variable calculation.
INFO: Setting the PROD_HOME variable of 'oracle.swd.opatch_11.2.0.1.2' to '/scratch/sandgoya/installations/oui111/OPatch'. Received the value from the variable calculation.
INFO: Setting the PROD_HOME variable of 'oracle.swd.oui.core_11.2.0.4.0' to '/scratch/sandgoya/installations/oui111/oui'. Received the value from the variable calculation.
INFO: Setting the PROD_HOME variable of 'oracle.swd.jre_1.5.0.11.0' to '/scratch/sandgoya/installations/oui111/jre/1.5.0'. Received the value from the variable calculation.
INFO: Performing operation for OUI Oracle Home access setup
INFO: Unable to read /scratch/sandgoya/installations/oui111/inventory/ContentsXML/comps.xml. Some inventory information may be lost.
INFO:

*** Oracle Universal Installer Page***
INFO: Setting the value of DECLINE_SECURITY_UPDATES
INFO: Setting variable 'DECLINE_SECURITY_UPDATES' to 'false'. Received the value from a code block.
INFO: Setting variable 'PROXY_USER' to ''. Received the value from a code block.
INFO: Setting variable 'PROXY_PWD' to '*Protected value, not to be logged*'. Received the value from a code block.
INFO: Setting variable 'PROXY_HOST' to ''. Received the value from a code block.
INFO: Setting variable 'PROXY_PORT' to ''. Received the value from a code block.
INFO: Setting variable 'COLLECTOR_SUPPORTHUB_URL' to ''. Received the value from a code block.
INFO: Setting variable 'MYORACLESUPPORT_PASSWORD' to '*Protected value, not to be logged*'. Received the value from a code block.
INFO: Setting variable 'METALINK_PASSWORD' to '*Protected value, not to be logged*'. Received the value from a code block.
INFO: Setting the value of METALINK_PASSWORD with the value of MYORACLESUPPORT_PASSWORD
INFO: Setting the value of SECURITY_UPDATES_VIA_METALINK
INFO: Setting variable 'SECURITY_UPDATES_VIA_METALINK' to 'false'. Received the value from a code block.
INFO: Setting the value of SECURITY_UPDATES_VIA_METALINK with the value of SECURITY_UPDATES_VIA_MYORACLESUPPORT
INFO: Setting variable 'COLLECTOR_RESPONSE_FILE' to ''. Received the value from a code block.
INFO: Is the component oracle.sysman.ccr found in the Shiphome ? false
INFO: Is the component eligible to be installed in the home ? false
So setting the system property oracle.sysman.ccrinstall to false
INFO: The user has chosen to include the collector, but with the shiphomeinfo.properties value, is the collector included for configuration ? : false
INFO: Can we show the collector page ? false
INFO: Setting the value of METALINK_PASSWORD
INFO: Setting variable 'METALINK_PASSWORD' to '*Protected value, not to be logged*'. Received the value from a code block.
INFO: Setting the value of SECURITY_UPDATES_VIA_METALINK
INFO: Setting variable 'SECURITY_UPDATES_VIA_METALINK' to 'false'. Received the value from a code block.
INFO: Setting the value of METALINK_USERNAME
INFO: Setting the 'MyOracleSupportPassword ( MYORACLESUPPORT_PASSWORD )' property to '*Protected value, not to be logged*'. Received the value from a code block.
INFO: Setting the 'ProxyUsername ( PROXY_USER )' property to ''. Received the value from a code block.
INFO: Setting the 'ProxyPassword ( PROXY_PWD )' property to '*Protected value, not to be logged*'. Received the value from a code block.
INFO: Setting the 'ProxyServer ( PROXY_HOST )' property to ''. Received the value from a code block.
INFO: Setting the 'ProxyPort ( PROXY_PORT )' property to ''. Received the value from a code block.
INFO: Setting the 'DeclineUpdates ( DECLINE_SECURITY_UPDATES )' property to 'false'. Received the value from a code block.
INFO: Setting the 'EnableMyOracleSupportPassword ( SECURITY_UPDATES_VIA_MYORACLESUPPORT )' property to 'false'. Received the value from the default settings.
INFO: Setting the 'RepeaterURL ( COLLECTOR_SUPPORTHUB_URL )' property to ''. Received the value from a code block.
INFO: SRVM ClusterInfo.IsLocalOnly() called. Return value obtained is 'false'.
INFO: The CRS clusterware location for 'oracle.crs 10.1.0.2.0' is not found.
INFO: CRS clusterware not found. Defaulting to vendor clusterware.
INFO: Vendor clusterware is not detected.
INFO: This is not a cluster system.
INFO: Node selection page will not be shown.
INFO: Defaulting prerequisite location to '/scratch/sandgoya/cd/Disk1/stage/prereq'.
INFO:
*** Product-Specific Prerequisite Checks Page***
INFO: OUI-10185:Unable to copy '/scratch/sandgoya/cd/Disk1/stage/prereq/prerequisite.properties' to '/scratch/sandgoya/installations/oui111/inventory/prereqs/prerequisite.properties'. OUI-10186:The source file '/scratch/sandgoya/cd/Disk1/stage/prereq/prerequisite.properties' does not exist.
INFO: No prerequisite checks specified for this installation.
INFO: Install type for "Oracle Installation Products 11.2.0.4.0 " is "Complete".
INFO: OUI-10066:Not all the dependencies for the component Oracle Installation Products 11.2.0.4.0  could be found. Missing component oracle.swd.osp 11.2.0.4.0.
INFO: Install type for "Oracle Installation Libraries 11.2.0.4.0 " is "Custom".
INFO: Install type for "Oracle Universal Installer 11.2.0.4.0 " is "Custom".
INFO:   Conflict while setting install type of "Oracle One-Off Patch Installer 11.2.0.1.2 "  to "Custom (Custom)". Install type already set to "Maximum (Complete)". Seting it to "Custom (Custom)".
INFO: OUI-10066:Not all the dependencies for the component Oracle Universal Installer 11.2.0.4.0  could be found. Missing component oracle.sysman.ccr 10.3.1.0.0.
INFO: Install type for "Oracle One-Off Patch Installer 11.2.0.1.2 " is "Custom".
INFO: Install type for "Installer SDK Component 11.2.0.4.0 " is "Custom".
INFO: Install type for "Java Runtime Environment 1.5.0.11.0 " is "Custom".
INFO: Setting the PRE_REQUISITE variable of 'oracle.swd_11.2.0.4.0' to 'true'. Received the value from the variable calculation.
INFO: Setting the PRE_REQUISITE variable of 'oracle.swd.jre_1.5.0.11.0' to 'true'. Received the value from the variable calculation.
INFO: Setting the PRE_REQUISITE variable of 'oracle.swd.oil_11.2.0.4.0' to 'true'. Received the value from the variable calculation.
INFO: Setting the PRE_REQUISITE variable of 'oracle.swd.oui_11.2.0.4.0' to 'true'. Received the value from the variable calculation.
INFO: Setting the PRE_REQUISITE variable of 'oracle.swd.opatch_11.2.0.1.2' to 'true'. Received the value from the variable calculation.
INFO: Setting the PRE_REQUISITE variable of 'oracle.swd.oui.core_11.2.0.4.0' to 'true'. Received the value from the variable calculation.
INFO:
*** Language Selection Page***
INFO: Setting the 'SelectedLanguages ( SELECTED_LANGUAGES )' property to 'en'. Received the value from the default settings.
INFO:
*** Specify Local Host Name Page***
INFO: Setting the 'HostName ( ORACLE_HOSTNAME )' property to 'adc2100128.us.oracle.com'. Received the value from the default settings.
INFO: *** Entering Component: oracle.swd installation
INFO: *** Entering Component: oracle.swd.oil installation
INFO: *** Entering Component: oracle.swd.oui installation
INFO: Setting variable 'platDir' to ''. Received the value from the variable calculation.
INFO: Calling Query generalQueries10.2.0.2.0  isCurrentPlatformInGroup

platGroup = WINDOWS
INFO: Query Returned: false
INFO: Setting variable 'isPlatGroupWindows' to 'false'. Received the value from the variable calculation.
INFO: Setting variable 'MSVCREDIST_LOC' to ''. Received the value from the variable calculation.
INFO: Setting variable 'MSVCREDIST_INSTALL' to ''. Received the value from the variable calculation.
INFO: Setting variable 'MSVCREDIST_FLAGS' to ''. Received the value from the variable calculation.
INFO: Setting variable 'JRE_MEMORY_OPTIONS' to ''. Received the value from the variable calculation.
INFO: Setting variable 'JRE_LOCATION' to ''. Received the value from the variable calculation.
INFO: Setting variable 'InstVer' to '11.2.0.4.0'. Received the value from the variable calculation.
INFO: Setting variable 'ABSOLUTE_JRE_LOCATION' to ''. Received the value from the variable calculation.
INFO: Setting variable 's_extLib' to '/scratch/sandgoya/installations/oui111/inventory/Scripts/ext/lib'. Received the value from the variable calculation.
INFO: Setting variable 's_extJlib' to '/scratch/sandgoya/installations/oui111/inventory/Scripts/ext/jlib'. Received the value from the variable calculation.
INFO: Setting variable 's_extBin' to '/scratch/sandgoya/installations/oui111/inventory/Scripts/ext/bin'. Received the value from the variable calculation.
INFO: Setting variable 'OUIFolder' to 'null\Oracle Installation Products'. Received the value from the variable calculation.
INFO: Setting variable 'InstLocProp' to '/scratch/sandgoya/installations/oui111/oui'. Received the value from the variable calculation.
INFO: *** Entering Component: oracle.swd.opatch installation
INFO: *** Entering Component: oracle.swd.oui.core installation
INFO: Setting variable 'platDir' to ''. Received the value from the variable calculation.
INFO: Setting variable 'InstVer' to '11.2.0.4.0'. Received the value from the variable calculation.
INFO: *** Entering Component: oracle.swd.jre installation
INFO: oracle.srvm.formCluster:false
INFO:
*** Summary Page***
INFO:

-----------------------------------------------------------------------------
Summary
Global Settings
Source: /scratch/sandgoya/cd/Disk1/stage/products.xml
Oracle Home: /scratch/sandgoya/installations/oui111 (OUIHome1111)
Installation Type: Complete
Product Languages
English
Space Requirements
/ Required 128MB (includes 25MB temporary) : Available 60.49GB
New Installations (6 products)
Oracle Installation Products 11.2.0.4.0
Oracle Installation Libraries 11.2.0.4.0
Oracle Universal Installer 11.2.0.4.0
Oracle One-Off Patch Installer 11.2.0.1.2
Installer SDK Component 11.2.0.4.0
Java Runtime Environment 1.5.0.11.0
-----------------------------------------------------------------------------
INFO: The default response file generated with recorded values is null
INFO: -destinationFile option was not provided. Saving the default response file as null
INFO: Recording the installation in file null.
INFO: Checkpoint:getting indexSession from checkpoint factory
INFO: Checkpoint:Index file :/scratch/sandgoya/installations/oui111/inventory/checkpoints/oui/index.xml not found.
INFO: Checkpoint:Initializing checkpointindex session in oiifwactionsphasewcde.
INFO: Checkpoint:Location is- /scratch/sandgoya/installations/oui111/inventory
INFO: Setting checkpoint object
INFO: Method 'dispose()' Not implemented in class 'oracle.sysman.oii.oiif.oiifp.OiifpWizIntroPanel'
INFO: config-context initialized
INFO: *** Install Page***
INFO: Checkpoint:Initializing checkpoint session in oiifwinstallphasewcce.
INFO: Checkpoint:Index session object added to oiicexitops.
INFO: FastCopy : File Version is Compatible
INFO: Install mode is fastcopy mode for component 'oracle.swd' with Install type 'Complete'.
INFO: Link phase has been specified as needed
INFO: Setup phase has been specified as needed
INFO: HomeSetup JRE files in Scratch :1045
INFO: Setting variable 'ROOTSH_LOCATION' to '/scratch/sandgoya/installations/oui111/root.sh'. Received the value from a code block.
INFO: Setting variable 'ROOTSH_LOCATION' to '/scratch/sandgoya/installations/oui111/root.sh'. Received the value from a code block.
INFO: Performing fastcopy operations based on the information in the file 'oracle.swd_Complete_dirs.lst'.
INFO: Performing fastcopy operations based on the information in the file 'oracle.swd_Complete_exp_1.xml'.
INFO: Performing fastcopy operations based on the information in the file 'racfiles.jar'.
INFO: Performing fastcopy operations based on the information in the file 'oracle.swd_Complete_filemap.jar'.
INFO: Performing fastcopy operations based on the information in the file 'oracle.swd_Complete_1.xml'.
INFO: Performing fastcopy operations based on the information in the file 'setperms1.sh'.
INFO: Number of threads for fast copy :1
INFO: The expanded list location :/tmp/OraInstall2012-10-04_12-48-35AM/fastcopy/oracle.swd_Complete_exp_1.xml
INFO: Executing permissions file from :/tmp/OraInstall2012-10-04_12-48-35AM/fastcopy/setperms1.sh
INFO: chmod 0755 oui/admin_langs.xml oui/runtime_langs.xml oui/nlsrtlmap.xml
INFO: chmod 0750 oui/prov/resources/sPaths.properties oui/prov/resources/sshConnectivity-usage.txt oui/prov/resources/ssPaths_sol.properties oui/prov/resources/ssPaths_hpi.properties oui/prov/resources/platformInfo.properties oui/prov/resources/ssh_system.properties oui/prov/resources/system.properties oui/prov/resources/logging_conf.xml oui/prov/resources/ssPaths_linux_zseries64.properties oui/prov/resources/ssPaths_linux_ia64.properties oui/prov/resources/ssPaths_msplats.properties oui/prov/resources/ssPaths_decunix.properties oui/prov/resources/ignoreMessages.txt oui/prov/resources/ssPaths_linuxx64.properties oui/prov/resources/ssPaths_solx86.properties oui/prov/resources/Paths.properties oui/prov/resources/ssPaths_hpuix.properties oui/prov/resources/ssPaths_linux_ppc64.properties oui/prov/resources/ssPaths_aix.properties oui/prov/resources/userPaths.properties oui/prov/resources/scripts/validatePaths oui/prov/resources/scripts/sshUserSetupNT.sh oui/prov/resources/scripts/sshUserSetup.sh oui/prov/resources/scripts/ouiSetup oui/prov/resources/scripts/sshConnectivity.sh
INFO: chmod 0755 oui/bin/filesList.bat oui/bin/filesList.properties oui/bin/filesList.sh
INFO: chmod 0750 oui/instImages/bg.jpg oui/instImages/10gOneClickbusybar.gif oui/instImages/splashScr.gif oui/instImages/oneclickbg.gif oui/instImages/images.properties
INFO: chmod 0740 diagnostics/config/registration/OUI.xml
INFO: chmod 0640 oui/jlib/ewt3.jar oui/jlib/ewt3-nls.jar oui/jlib/jewt4.jar oui/jlib/help4.jar oui/jlib/help4-nls.jar oui/jlib/InstHelp.jar oui/jlib/InstHelp_de.jar oui/jlib/InstHelp_es.jar oui/jlib/InstHelp_fr.jar oui/jlib/InstHelp_it.jar oui/jlib/InstHelp_ja.jar oui/jlib/InstHelp_ko.jar oui/jlib/InstHelp_pt_BR.jar oui/jlib/InstHelp_zh_CN.jar oui/jlib/InstHelp_zh_TW.jar oui/jlib/InstImages.jar oui/jlib/oracle_ice.jar oui/jlib/swingaccess.jar oui/jlib/ewt3-swingaccess.jar oui/jlib/classes12.jar oui/jlib/orai18n-collation.jar oui/jlib/orai18n-mapping.jar oui/jlib/ojmisc.jar oui/jlib/xml.jar oui/jlib/srvm.jar oui/jlib/srvmasm.jar oui/jlib/remoteinterfaces.jar oui/jlib/ssh.jar oui/jlib/jsch.jar oui/jlib/filesList.jar
INFO: chmod 0755 oui/schema/filemap.xsd
INFO: chmod 644 OPatch/opatch.pl OPatch/opatch.ini OPatch/emdpatch.pl OPatch/opatchprereqs/oui/knowledgesrc.xml OPatch/opatchprereqs/opatch/opatch_prereq.xml OPatch/opatchprereqs/opatch/rulemap.xml OPatch/opatchprereqs/opatch/runtime_prereq.xml OPatch/jlib/opatch.jar OPatch/jlib/opatchutil.jar OPatch/jlib/opatchprereq.jar OPatch/jlib/opatchactions.jar OPatch/jlib/opatchext.jar OPatch/jlib/opatchfmw.jar
INFO: chmod 754 OPatch/fmw/application.py OPatch/fmw/init_def.py OPatch/fmw/main_driver.py OPatch/fmw/node_manager.py OPatch/fmw/prereq.py OPatch/fmw/start_stop.py
INFO: chmod 644 OPatch/opatchprereqs/prerequisite.properties
INFO: chmod 755 OPatch/opatch OPatch/opatch.bat
INFO: chmod 754 OPatch/crs/auto_patch.pl OPatch/crs/crsconfig_lib.pm OPatch/crs/crsdelete.pm OPatch/crs/crspatch.pm OPatch/crs/oracss.pm OPatch/crs/patch112.pl OPatch/crs/s_crsconfig_defs OPatch/crs/s_crsconfig_lib.pm OPatch/crs/log/dummy
INFO: chmod 644 OPatch/docs/FAQ OPatch/docs/Users_Guide.txt OPatch/docs/Prereq_Users_Guide.txt
INFO: chmod 0750 srvm/admin/ractrans oui/lib/win64/oraInstaller.dll oui/lib/win32/RemoteExec.exe oui/lib/win32/oraInstaller.dll oui/lib/linux/liboraInstaller.so oui/lib/linux/libsrvm11.so oui/lib/intelsolaris/dummy oui/lib/linux64/liboraInstaller.so oui/lib/linux64/libsrvm11.so oui/lib/linuxS390/dummy
INFO: chmod 0640 oui/oraparam.ini oui/clusterparam.ini
INFO: chmod 0750 oui/bin/resource/cons_ja.nls oui/bin/resource/cons_de.nls oui/bin/resource/cons.nls oui/bin/resource/cons_pt_BR.nls oui/bin/resource/cons_ko.nls oui/bin/resource/cons_fr.nls oui/bin/resource/cons_it.nls oui/bin/resource/cons_es.nls oui/bin/resource/cons_zh_TW.nls oui/bin/resource/cons_zh_CN.nls oui/bin/platform/oraparam.ini oui/bin/platform/runInstaller oui/bin/platform/filesList.bat oui/bin/platform/filesList.properties oui/bin/platform/clusterparam.var oui/bin/platform/lsnodes oui/bin/platform/setup.exe oui/bin/platform/oraparam.var oui/bin/platform/filesList.sh oui/bin/platform/oui.var oui/bin/platform/win32/addNode.bat oui/bin/platform/win32/access_setup.bat oui/bin/platform/win32/clusterparam.ini oui/bin/platform/win32/addLangs.stage oui/bin/platform/win32/setup.exe oui/bin/platform/win32/oraparam.ini oui/bin/platform/win32/oraparam.stage oui/bin/platform/win32/detachHome.bat oui/bin/platform/win32/addLangs.bat oui/bin/platform/win32/attachHome.bat oui/bin/platform/win32/runConfig.bat oui/bin/platform/win32/unzip.exe oui/bin/platform/win32/resource/cons_zh_TW.nls oui/bin/platform/win32/resource/cons_it.nls oui/bin/platform/win32/resource/cons_es.nls oui/bin/platform/win32/resource/cons_zh_CN.nls oui/bin/platform/win32/resource/cons.nls oui/bin/platform/win32/resource/cons_pt_BR.nls oui/bin/platform/win32/resource/cons_ja.nls oui/bin/platform/win32/resource/cons_de.nls oui/bin/platform/win32/resource/cons_ko.nls oui/bin/platform/win32/resource/cons_fr.nls oui/bin/platform/win64/oraparam.ini oui/bin/platform/win64/setup.exe oui/bin/platform/win64/oraparam.stage oui/bin/platform/win64/detachHome.bat oui/bin/platform/win64/addNode.bat oui/bin/platform/win64/attachHome.bat oui/bin/platform/win64/clusterparam.ini oui/bin/platform/win64/runConfig.bat oui/bin/platform/win64/addLangs.stage oui/bin/platform/win64/unzip.exe oui/bin/platform/win64/addLangs.bat oui/bin/platform/win64/access_setup.bat oui/bin/platform/win64/resource/cons_fr.nls oui/bin/platform/win64/resource/cons_zh_TW.nls oui/bin/platform/win64/resource/cons_ko.nls oui/bin/platform/win64/resource/cons_de.nls oui/bin/platform/win64/resource/cons_ja.nls oui/bin/platform/win64/resource/cons.nls oui/bin/platform/win64/resource/cons_zh_CN.nls oui/bin/platform/win64/resource/cons_pt_BR.nls oui/bin/platform/win64/resource/cons_es.nls oui/bin/platform/win64/resource/cons_it.nls oui/bin/platform/linux/runSSHSetup.sh oui/bin/platform/linux/runInstaller.sh oui/bin/platform/linux/runConfig.sh oui/bin/platform/linux/lsnodes oui/bin/platform/linux/addLangs.sh oui/bin/platform/linux/addNode.sh oui/bin/platform/linux/detachHome.sh oui/bin/platform/linux/unzip oui/bin/platform/linux/runInstaller oui/bin/platform/linux/clusterparam.ini oui/bin/platform/linux/oraparam.ini oui/bin/platform/linux/runInstaller.var oui/bin/platform/linux/attachHome.sh oui/bin/platform/linux/resource/cons_it.nls oui/bin/platform/linux/resource/cons_zh_CN.nls oui/bin/platform/linux/resource/cons_es.nls oui/bin/platform/linux/resource/cons_zh_TW.nls oui/bin/platform/linux/resource/cons_ja.nls oui/bin/platform/linux/resource/cons.nls oui/bin/platform/linux/resource/cons_de.nls oui/bin/platform/linux/resource/cons_ko.nls oui/bin/platform/linux/resource/cons_fr.nls oui/bin/platform/linux/resource/cons_pt_BR.nls oui/bin/platform/resource/cons_ja.nls oui/bin/platform/resource/cons_de.nls oui/bin/platform/resource/cons.nls oui/bin/platform/resource/cons_pt_BR.nls oui/bin/platform/resource/cons_ko.nls oui/bin/platform/resource/cons_fr.nls oui/bin/platform/resource/cons_it.nls oui/bin/platform/resource/cons_es.nls oui/bin/platform/resource/cons_zh_TW.nls oui/bin/platform/resource/cons_zh_CN.nls oui/bin/platform/linux64/runSSHSetup.sh oui/bin/platform/linux64/runInstaller.sh oui/bin/platform/linux64/runConfig.sh oui/bin/platform/linux64/lsnodes oui/bin/platform/linux64/addLangs.sh oui/bin/platform/linux64/addNode.sh oui/bin/platform/linux64/detachHome.sh oui/bin/platform/linux64/unzip oui/bin/platform/linux64/runInstaller oui/bin/platform/linux64/clusterparam.ini oui/bin/platform/linux64/oraparam.ini oui/bin/platform/linux64/runInstaller.var oui/bin/platform/linux64/attachHome.sh oui/bin/platform/linux64/resource/cons_it.nls oui/bin/platform/linux64/resource/cons_zh_CN.nls oui/bin/platform/linux64/resource/cons_es.nls oui/bin/platform/linux64/resource/cons_zh_TW.nls oui/bin/platform/linux64/resource/cons_ja.nls oui/bin/platform/linux64/resource/cons.nls oui/bin/platform/linux64/resource/cons_de.nls oui/bin/platform/linux64/resource/cons_ko.nls oui/bin/platform/linux64/resource/cons_fr.nls oui/bin/platform/linux64/resource/cons_pt_BR.nls oui/bin/platform/linuxS390/dummy
INFO: chmod 0640 oui/jlib/OraPrereqChecks.jar oui/jlib/emCfg.jar oui/jlib/OraPrereq.jar oui/jlib/OraInstallerNet.jar oui/jlib/OraSuiteInstaller.jar oui/jlib/OraInstaller.jar oui/jlib/emocmutl.jar oui/jlib/OraCheckPoint.jar oui/jlib/http_client.jar oui/jlib/prov_fixup.jar oui/jlib/oneclick.jar oui/jlib/share.jar oui/jlib/xmlparserv2.jar oui/jlib/jlib/emocmcommon.jar oui/jlib/jlib/emocmclnt.jar oui/jlib/jlib/regexp.jar oui/jlib/jlib/emocmclnt-14.jar oui/jlib/jlib/jsse.jar oui/jlib/jlib/osdt_jce.jar oui/jlib/jlib/jnet.jar oui/jlib/jlib/xmlparserv2.jar oui/jlib/jlib/osdt_core3.jar oui/jlib/jlib/jcert.jar oui/jlib/jlib/http_client.jar oui/jlib/jlib/log4j-core.jar
INFO: chmod 555 jre/1.5.0/CHANGES jre/1.5.0/COPYRIGHT jre/1.5.0/LICENSE jre/1.5.0/README jre/1.5.0/THIRDPARTYLICENSEREADME.txt jre/1.5.0/Welcome.html jre/1.5.0/man/man1/java.1 jre/1.5.0/man/man1/keytool.1 jre/1.5.0/man/man1/kinit.1 jre/1.5.0/man/man1/klist.1 jre/1.5.0/man/man1/ktab.1 jre/1.5.0/man/man1/orbd.1 jre/1.5.0/man/man1/pack200.1 jre/1.5.0/man/man1/policytool.1 jre/1.5.0/man/man1/rmid.1 jre/1.5.0/man/man1/rmiregistry.1 jre/1.5.0/man/man1/servertool.1 jre/1.5.0/man/man1/tnameserv.1 jre/1.5.0/man/man1/unpack200.1 jre/1.5.0/man/ja_JP.eucJP/man1/java.1 jre/1.5.0/man/ja_JP.eucJP/man1/keytool.1 jre/1.5.0/man/ja_JP.eucJP/man1/kinit.1 jre/1.5.0/man/ja_JP.eucJP/man1/klist.1 jre/1.5.0/man/ja_JP.eucJP/man1/ktab.1 jre/1.5.0/man/ja_JP.eucJP/man1/orbd.1 jre/1.5.0/man/ja_JP.eucJP/man1/pack200.1 jre/1.5.0/man/ja_JP.eucJP/man1/policytool.1 jre/1.5.0/man/ja_JP.eucJP/man1/rmid.1 jre/1.5.0/man/ja_JP.eucJP/man1/rmiregistry.1 jre/1.5.0/man/ja_JP.eucJP/man1/servertool.1 jre/1.5.0/man/ja_JP.eucJP/man1/tnameserv.1 jre/1.5.0/man/ja_JP.eucJP/man1/unpack200.1 jre/1.5.0/man/ja/man1/java.1 jre/1.5.0/man/ja/man1/keytool.1 jre/1.5.0/man/ja/man1/kinit.1 jre/1.5.0/man/ja/man1/klist.1 jre/1.5.0/man/ja/man1/ktab.1 jre/1.5.0/man/ja/man1/orbd.1 jre/1.5.0/man/ja/man1/pack200.1 jre/1.5.0/man/ja/man1/policytool.1 jre/1.5.0/man/ja/man1/rmid.1 jre/1.5.0/man/ja/man1/rmiregistry.1 jre/1.5.0/man/ja/man1/servertool.1 jre/1.5.0/man/ja/man1/tnameserv.1 jre/1.5.0/man/ja/man1/unpack200.1 jre/1.5.0/lib/charsets.jar jre/1.5.0/lib/classlist jre/1.5.0/lib/content-types.properties jre/1.5.0/lib/flavormap.properties jre/1.5.0/lib/fontconfig.RedHat.2.1.bfc jre/1.5.0/lib/fontconfig.RedHat.2.1.properties.src jre/1.5.0/lib/fontconfig.RedHat.3.bfc jre/1.5.0/lib/fontconfig.RedHat.3.properties.src jre/1.5.0/lib/fontconfig.RedHat.8.0.bfc jre/1.5.0/lib/fontconfig.RedHat.8.0.properties.src jre/1.5.0/lib/fontconfig.RedHat.9.0.bfc jre/1.5.0/lib/fontconfig.RedHat.9.0.properties.src jre/1.5.0/lib/fontconfig.RedHat.bfc jre/1.5.0/lib/fontconfig.RedHat.properties.src jre/1.5.0/lib/fontconfig.SuSE.bfc jre/1.5.0/lib/fontconfig.SuSE.properties.src jre/1.5.0/lib/fontconfig.Sun.2003.bfc jre/1.5.0/lib/fontconfig.Sun.2003.properties.src jre/1.5.0/lib/fontconfig.Sun.bfc jre/1.5.0/lib/fontconfig.Sun.properties.src jre/1.5.0/lib/fontconfig.Turbo.8.0.bfc jre/1.5.0/lib/fontconfig.Turbo.8.0.properties.src jre/1.5.0/lib/fontconfig.Turbo.bfc jre/1.5.0/lib/fontconfig.Turbo.properties.src jre/1.5.0/lib/fontconfig.bfc jre/1.5.0/lib/fontconfig.properties.src jre/1.5.0/lib/jce.jar jre/1.5.0/lib/jsse.jar jre/1.5.0/lib/jvm.hprof.txt jre/1.5.0/lib/logging.properties jre/1.5.0/lib/net.properties jre/1.5.0/lib/psfont.properties.ja jre/1.5.0/lib/psfontj2d.properties jre/1.5.0/lib/rt.jar jre/1.5.0/lib/sound.properties jre/1.5.0/lib/zi/CET jre/1.5.0/lib/zi/CST6CDT jre/1.5.0/lib/zi/EET jre/1.5.0/lib/zi/EST jre/1.5.0/lib/zi/EST5EDT jre/1.5.0/lib/zi/GMT jre/1.5.0/lib/zi/HST jre/1.5.0/lib/zi/MET jre/1.5.0/lib/zi/MST jre/1.5.0/lib/zi/MST7MDT jre/1.5.0/lib/zi/PST8PDT jre/1.5.0/lib/zi/WET jre/1.5.0/lib/zi/ZoneInfoMappings jre/1.5.0/lib/zi/Etc/GMT jre/1.5.0/lib/zi/Etc/GMT+1 jre/1.5.0/lib/zi/Etc/GMT+10 jre/1.5.0/lib/zi/Etc/GMT+11 jre/1.5.0/lib/zi/Etc/GMT+12 jre/1.5.0/lib/zi/Etc/GMT+2 jre/1.5.0/lib/zi/Etc/GMT+3 jre/1.5.0/lib/zi/Etc/GMT+4 jre/1.5.0/lib/zi/Etc/GMT+5 jre/1.5.0/lib/zi/Etc/GMT+6 jre/1.5.0/lib/zi/Etc/GMT+7 jre/1.5.0/lib/zi/Etc/GMT+8 jre/1.5.0/lib/zi/Etc/GMT+9 jre/1.5.0/lib/zi/Etc/GMT-1 jre/1.5.0/lib/zi/Etc/GMT-10 jre/1.5.0/lib/zi/Etc/GMT-11 jre/1.5.0/lib/zi/Etc/GMT-12 jre/1.5.0/lib/zi/Etc/GMT-13 jre/1.5.0/lib/zi/Etc/GMT-14 jre/1.5.0/lib/zi/Etc/GMT-2 jre/1.5.0/lib/zi/Etc/GMT-3 jre/1.5.0/lib/zi/Etc/GMT-4 jre/1.5.0/lib/zi/Etc/GMT-5 jre/1.5.0/lib/zi/Etc/GMT-6 jre/1.5.0/lib/zi/Etc/GMT-7 jre/1.5.0/lib/zi/Etc/GMT-8 jre/1.5.0/lib/zi/Etc/GMT-9 jre/1.5.0/lib/zi/Etc/UCT jre/1.5.0/lib/zi/Etc/UTC jre/1.5.0/lib/zi/Asia/Aden jre/1.5.0/lib/zi/Asia/Almaty jre/1.5.0/lib/zi/Asia/Amman jre/1.5.0/lib/zi/Asia/Anadyr jre/1.5.0/lib/zi/Asia/Aqtau jre/1.5.0/lib/zi/Asia/Aqtobe jre/1.5.0/lib/zi/Asia/Ashgabat jre/1.5.0/lib/zi/Asia/Baghdad jre/1.5.0/lib/zi/Asia/Bahrain jre/1.5.0/lib/zi/Asia/Baku jre/1.5.0/lib/zi/Asia/Bangkok jre/1.5.0/lib/zi/Asia/Beirut jre/1.5.0/lib/zi/Asia/Bishkek jre/1.5.0/lib/zi/Asia/Brunei jre/1.5.0/lib/zi/Asia/Calcutta jre/1.5.0/lib/zi/Asia/Choibalsan jre/1.5.0/lib/zi/Asia/Chongqing jre/1.5.0/lib/zi/Asia/Colombo jre/1.5.0/lib/zi/Asia/Damascus jre/1.5.0/lib/zi/Asia/Dhaka jre/1.5.0/lib/zi/Asia/Dili jre/1.5.0/lib/zi/Asia/Dubai jre/1.5.0/lib/zi/Asia/Dushanbe jre/1.5.0/lib/zi/Asia/Gaza jre/1.5.0/lib/zi/Asia/Harbin jre/1.5.0/lib/zi/Asia/Hong_Kong jre/1.5.0/lib/zi/Asia/Hovd jre/1.5.0/lib/zi/Asia/Irkutsk jre/1.5.0/lib/zi/Asia/Jakarta jre/1.5.0/lib/zi/Asia/Jayapura jre/1.5.0/lib/zi/Asia/Jerusalem jre/1.5.0/lib/zi/Asia/Kabul jre/1.5.0/lib/zi/Asia/Kamchatka jre/1.5.0/lib/zi/Asia/Karachi jre/1.5.0/lib/zi/Asia/Kashgar jre/1.5.0/lib/zi/Asia/Katmandu jre/1.5.0/lib/zi/Asia/Krasnoyarsk jre/1.5.0/lib/zi/Asia/Kuala_Lumpur jre/1.5.0/lib/zi/Asia/Kuching jre/1.5.0/lib/zi/Asia/Kuwait jre/1.5.0/lib/zi/Asia/Macau jre/1.5.0/lib/zi/Asia/Magadan jre/1.5.0/lib/zi/Asia/Makassar jre/1.5.0/lib/zi/Asia/Manila jre/1.5.0/lib/zi/Asia/Muscat jre/1.5.0/lib/zi/Asia/Nicosia jre/1.5.0/lib/zi/Asia/Novosibirsk jre/1.5.0/lib/zi/Asia/Omsk jre/1.5.0/lib/zi/Asia/Oral jre/1.5.0/lib/zi/Asia/Phnom_Penh jre/1.5.0/lib/zi/Asia/Pontianak jre/1.5.0/lib/zi/Asia/Pyongyang jre/1.5.0/lib/zi/Asia/Qatar jre/1.5.0/lib/zi/Asia/Qyzylorda jre/1.5.0/lib/zi/Asia/Rangoon jre/1.5.0/lib/zi/Asia/Riyadh jre/1.5.0/lib/zi/Asia/Riyadh87 jre/1.5.0/lib/zi/Asia/Riyadh88 jre/1.5.0/lib/zi/Asia/Riyadh89 jre/1.5.0/lib/zi/Asia/Saigon jre/1.5.0/lib/zi/Asia/Sakhalin jre/1.5.0/lib/zi/Asia/Samarkand jre/1.5.0/lib/zi/Asia/Seoul jre/1.5.0/lib/zi/Asia/Shanghai jre/1.5.0/lib/zi/Asia/Singapore jre/1.5.0/lib/zi/Asia/Taipei jre/1.5.0/lib/zi/Asia/Tashkent jre/1.5.0/lib/zi/Asia/Tbilisi jre/1.5.0/lib/zi/Asia/Tehran jre/1.5.0/lib/zi/Asia/Thimphu jre/1.5.0/lib/zi/Asia/Tokyo jre/1.5.0/lib/zi/Asia/Ulaanbaatar jre/1.5.0/lib/zi/Asia/Urumqi jre/1.5.0/lib/zi/Asia/Vientiane jre/1.5.0/lib/zi/Asia/Vladivostok jre/1.5.0/lib/zi/Asia/Yakutsk jre/1.5.0/lib/zi/Asia/Yekaterinburg jre/1.5.0/lib/zi/Asia/Yerevan jre/1.5.0/lib/zi/Indian/Antananarivo jre/1.5.0/lib/zi/Indian/Chagos jre/1.5.0/lib/zi/Indian/Christmas jre/1.5.0/lib/zi/Indian/Cocos jre/1.5.0/lib/zi/Indian/Comoro jre/1.5.0/lib/zi/Indian/Kerguelen jre/1.5.0/lib/zi/Indian/Mahe jre/1.5.0/lib/zi/Indian/Maldives jre/1.5.0/lib/zi/Indian/Mauritius jre/1.5.0/lib/zi/Indian/Mayotte jre/1.5.0/lib/zi/Indian/Reunion jre/1.5.0/lib/zi/Europe/Amsterdam jre/1.5.0/lib/zi/Europe/Andorra jre/1.5.0/lib/zi/Europe/Athens jre/1.5.0/lib/zi/Europe/Belgrade jre/1.5.0/lib/zi/Europe/Berlin jre/1.5.0/lib/zi/Europe/Brussels jre/1.5.0/lib/zi/Europe/Bucharest jre/1.5.0/lib/zi/Europe/Budapest jre/1.5.0/lib/zi/Europe/Chisinau jre/1.5.0/lib/zi/Europe/Copenhagen jre/1.5.0/lib/zi/Europe/Dublin jre/1.5.0/lib/zi/Europe/Gibraltar jre/1.5.0/lib/zi/Europe/Helsinki jre/1.5.0/lib/zi/Europe/Istanbul jre/1.5.0/lib/zi/Europe/Kaliningrad jre/1.5.0/lib/zi/Europe/Kiev jre/1.5.0/lib/zi/Europe/Lisbon jre/1.5.0/lib/zi/Europe/London jre/1.5.0/lib/zi/Europe/Luxembourg jre/1.5.0/lib/zi/Europe/Madrid jre/1.5.0/lib/zi/Europe/Malta jre/1.5.0/lib/zi/Europe/Minsk jre/1.5.0/lib/zi/Europe/Monaco jre/1.5.0/lib/zi/Europe/Moscow jre/1.5.0/lib/zi/Europe/Oslo jre/1.5.0/lib/zi/Europe/Paris jre/1.5.0/lib/zi/Europe/Prague jre/1.5.0/lib/zi/Europe/Riga jre/1.5.0/lib/zi/Europe/Rome jre/1.5.0/lib/zi/Europe/Samara jre/1.5.0/lib/zi/Europe/Simferopol jre/1.5.0/lib/zi/Europe/Sofia jre/1.5.0/lib/zi/Europe/Stockholm jre/1.5.0/lib/zi/Europe/Tallinn jre/1.5.0/lib/zi/Europe/Tirane jre/1.5.0/lib/zi/Europe/Uzhgorod jre/1.5.0/lib/zi/Europe/Vaduz jre/1.5.0/lib/zi/Europe/Vienna jre/1.5.0/lib/zi/Europe/Vilnius jre/1.5.0/lib/zi/Europe/Volgograd jre/1.5.0/lib/zi/Europe/Warsaw jre/1.5.0/lib/zi/Europe/Zaporozhye jre/1.5.0/lib/zi/Europe/Zurich jre/1.5.0/lib/zi/Africa/Abidjan
INFO: chmod 555 jre/1.5.0/lib/zi/Africa/Accra jre/1.5.0/lib/zi/Africa/Addis_Ababa jre/1.5.0/lib/zi/Africa/Algiers jre/1.5.0/lib/zi/Africa/Asmara jre/1.5.0/lib/zi/Africa/Bamako jre/1.5.0/lib/zi/Africa/Bangui jre/1.5.0/lib/zi/Africa/Banjul jre/1.5.0/lib/zi/Africa/Bissau jre/1.5.0/lib/zi/Africa/Blantyre jre/1.5.0/lib/zi/Africa/Brazzaville jre/1.5.0/lib/zi/Africa/Bujumbura jre/1.5.0/lib/zi/Africa/Cairo jre/1.5.0/lib/zi/Africa/Casablanca jre/1.5.0/lib/zi/Africa/Ceuta jre/1.5.0/lib/zi/Africa/Conakry jre/1.5.0/lib/zi/Africa/Dakar jre/1.5.0/lib/zi/Africa/Dar_es_Salaam jre/1.5.0/lib/zi/Africa/Djibouti jre/1.5.0/lib/zi/Africa/Douala jre/1.5.0/lib/zi/Africa/El_Aaiun jre/1.5.0/lib/zi/Africa/Freetown jre/1.5.0/lib/zi/Africa/Gaborone jre/1.5.0/lib/zi/Africa/Harare jre/1.5.0/lib/zi/Africa/Johannesburg jre/1.5.0/lib/zi/Africa/Kampala jre/1.5.0/lib/zi/Africa/Khartoum jre/1.5.0/lib/zi/Africa/Kigali jre/1.5.0/lib/zi/Africa/Kinshasa jre/1.5.0/lib/zi/Africa/Lagos jre/1.5.0/lib/zi/Africa/Libreville jre/1.5.0/lib/zi/Africa/Lome jre/1.5.0/lib/zi/Africa/Luanda jre/1.5.0/lib/zi/Africa/Lubumbashi jre/1.5.0/lib/zi/Africa/Lusaka jre/1.5.0/lib/zi/Africa/Malabo jre/1.5.0/lib/zi/Africa/Maputo jre/1.5.0/lib/zi/Africa/Maseru jre/1.5.0/lib/zi/Africa/Mbabane jre/1.5.0/lib/zi/Africa/Mogadishu jre/1.5.0/lib/zi/Africa/Monrovia jre/1.5.0/lib/zi/Africa/Nairobi jre/1.5.0/lib/zi/Africa/Ndjamena jre/1.5.0/lib/zi/Africa/Niamey jre/1.5.0/lib/zi/Africa/Nouakchott jre/1.5.0/lib/zi/Africa/Ouagadougou jre/1.5.0/lib/zi/Africa/Porto-Novo jre/1.5.0/lib/zi/Africa/Sao_Tome jre/1.5.0/lib/zi/Africa/Tripoli jre/1.5.0/lib/zi/Africa/Tunis jre/1.5.0/lib/zi/Africa/Windhoek jre/1.5.0/lib/zi/SystemV/AST4 jre/1.5.0/lib/zi/SystemV/AST4ADT jre/1.5.0/lib/zi/SystemV/CST6 jre/1.5.0/lib/zi/SystemV/CST6CDT jre/1.5.0/lib/zi/SystemV/EST5 jre/1.5.0/lib/zi/SystemV/EST5EDT jre/1.5.0/lib/zi/SystemV/HST10 jre/1.5.0/lib/zi/SystemV/MST7 jre/1.5.0/lib/zi/SystemV/MST7MDT jre/1.5.0/lib/zi/SystemV/PST8 jre/1.5.0/lib/zi/SystemV/PST8PDT jre/1.5.0/lib/zi/SystemV/YST9 jre/1.5.0/lib/zi/SystemV/YST9YDT jre/1.5.0/lib/zi/Pacific/Apia jre/1.5.0/lib/zi/Pacific/Auckland jre/1.5.0/lib/zi/Pacific/Chatham jre/1.5.0/lib/zi/Pacific/Easter jre/1.5.0/lib/zi/Pacific/Efate jre/1.5.0/lib/zi/Pacific/Enderbury jre/1.5.0/lib/zi/Pacific/Fakaofo jre/1.5.0/lib/zi/Pacific/Fiji jre/1.5.0/lib/zi/Pacific/Funafuti jre/1.5.0/lib/zi/Pacific/Galapagos jre/1.5.0/lib/zi/Pacific/Gambier jre/1.5.0/lib/zi/Pacific/Guadalcanal jre/1.5.0/lib/zi/Pacific/Guam jre/1.5.0/lib/zi/Pacific/Honolulu jre/1.5.0/lib/zi/Pacific/Johnston jre/1.5.0/lib/zi/Pacific/Kiritimati jre/1.5.0/lib/zi/Pacific/Kosrae jre/1.5.0/lib/zi/Pacific/Kwajalein jre/1.5.0/lib/zi/Pacific/Majuro jre/1.5.0/lib/zi/Pacific/Marquesas jre/1.5.0/lib/zi/Pacific/Midway jre/1.5.0/lib/zi/Pacific/Nauru jre/1.5.0/lib/zi/Pacific/Niue jre/1.5.0/lib/zi/Pacific/Norfolk jre/1.5.0/lib/zi/Pacific/Noumea jre/1.5.0/lib/zi/Pacific/Pago_Pago jre/1.5.0/lib/zi/Pacific/Palau jre/1.5.0/lib/zi/Pacific/Pitcairn jre/1.5.0/lib/zi/Pacific/Ponape jre/1.5.0/lib/zi/Pacific/Port_Moresby jre/1.5.0/lib/zi/Pacific/Rarotonga jre/1.5.0/lib/zi/Pacific/Saipan jre/1.5.0/lib/zi/Pacific/Tahiti jre/1.5.0/lib/zi/Pacific/Tarawa jre/1.5.0/lib/zi/Pacific/Tongatapu jre/1.5.0/lib/zi/Pacific/Truk jre/1.5.0/lib/zi/Pacific/Wake jre/1.5.0/lib/zi/Pacific/Wallis jre/1.5.0/lib/zi/America/Adak jre/1.5.0/lib/zi/America/Anchorage jre/1.5.0/lib/zi/America/Anguilla jre/1.5.0/lib/zi/America/Antigua jre/1.5.0/lib/zi/America/Araguaina jre/1.5.0/lib/zi/America/Aruba jre/1.5.0/lib/zi/America/Asuncion jre/1.5.0/lib/zi/America/Atikokan jre/1.5.0/lib/zi/America/Bahia jre/1.5.0/lib/zi/America/Barbados jre/1.5.0/lib/zi/America/Belem jre/1.5.0/lib/zi/America/Belize jre/1.5.0/lib/zi/America/Blanc-Sablon jre/1.5.0/lib/zi/America/Boa_Vista jre/1.5.0/lib/zi/America/Bogota jre/1.5.0/lib/zi/America/Boise jre/1.5.0/lib/zi/America/Cambridge_Bay jre/1.5.0/lib/zi/America/Campo_Grande jre/1.5.0/lib/zi/America/Cancun jre/1.5.0/lib/zi/America/Caracas jre/1.5.0/lib/zi/America/Cayenne jre/1.5.0/lib/zi/America/Cayman jre/1.5.0/lib/zi/America/Chicago jre/1.5.0/lib/zi/America/Chihuahua jre/1.5.0/lib/zi/America/Costa_Rica jre/1.5.0/lib/zi/America/Cuiaba jre/1.5.0/lib/zi/America/Curacao jre/1.5.0/lib/zi/America/Danmarkshavn jre/1.5.0/lib/zi/America/Dawson jre/1.5.0/lib/zi/America/Dawson_Creek jre/1.5.0/lib/zi/America/Denver jre/1.5.0/lib/zi/America/Detroit jre/1.5.0/lib/zi/America/Dominica jre/1.5.0/lib/zi/America/Edmonton jre/1.5.0/lib/zi/America/Eirunepe jre/1.5.0/lib/zi/America/El_Salvador jre/1.5.0/lib/zi/America/Fortaleza jre/1.5.0/lib/zi/America/Glace_Bay jre/1.5.0/lib/zi/America/Godthab jre/1.5.0/lib/zi/America/Goose_Bay jre/1.5.0/lib/zi/America/Grand_Turk jre/1.5.0/lib/zi/America/Grenada jre/1.5.0/lib/zi/America/Guadeloupe jre/1.5.0/lib/zi/America/Guatemala jre/1.5.0/lib/zi/America/Guayaquil jre/1.5.0/lib/zi/America/Guyana jre/1.5.0/lib/zi/America/Halifax jre/1.5.0/lib/zi/America/Havana jre/1.5.0/lib/zi/America/Hermosillo jre/1.5.0/lib/zi/America/Inuvik jre/1.5.0/lib/zi/America/Iqaluit jre/1.5.0/lib/zi/America/Jamaica jre/1.5.0/lib/zi/America/Juneau jre/1.5.0/lib/zi/America/La_Paz jre/1.5.0/lib/zi/America/Lima jre/1.5.0/lib/zi/America/Los_Angeles jre/1.5.0/lib/zi/America/Maceio jre/1.5.0/lib/zi/America/Managua jre/1.5.0/lib/zi/America/Manaus jre/1.5.0/lib/zi/America/Martinique jre/1.5.0/lib/zi/America/Mazatlan jre/1.5.0/lib/zi/America/Menominee jre/1.5.0/lib/zi/America/Merida jre/1.5.0/lib/zi/America/Mexico_City jre/1.5.0/lib/zi/America/Miquelon jre/1.5.0/lib/zi/America/Moncton jre/1.5.0/lib/zi/America/Monterrey jre/1.5.0/lib/zi/America/Montevideo jre/1.5.0/lib/zi/America/Montreal jre/1.5.0/lib/zi/America/Montserrat jre/1.5.0/lib/zi/America/Nassau jre/1.5.0/lib/zi/America/New_York jre/1.5.0/lib/zi/America/Nipigon jre/1.5.0/lib/zi/America/Nome jre/1.5.0/lib/zi/America/Noronha jre/1.5.0/lib/zi/America/Panama jre/1.5.0/lib/zi/America/Pangnirtung jre/1.5.0/lib/zi/America/Paramaribo jre/1.5.0/lib/zi/America/Phoenix jre/1.5.0/lib/zi/America/Port-au-Prince jre/1.5.0/lib/zi/America/Port_of_Spain jre/1.5.0/lib/zi/America/Porto_Velho jre/1.5.0/lib/zi/America/Puerto_Rico jre/1.5.0/lib/zi/America/Rainy_River jre/1.5.0/lib/zi/America/Rankin_Inlet jre/1.5.0/lib/zi/America/Recife jre/1.5.0/lib/zi/America/Regina jre/1.5.0/lib/zi/America/Rio_Branco jre/1.5.0/lib/zi/America/Santiago jre/1.5.0/lib/zi/America/Santo_Domingo jre/1.5.0/lib/zi/America/Sao_Paulo jre/1.5.0/lib/zi/America/Scoresbysund jre/1.5.0/lib/zi/America/St_Johns jre/1.5.0/lib/zi/America/St_Kitts jre/1.5.0/lib/zi/America/St_Lucia jre/1.5.0/lib/zi/America/St_Thomas jre/1.5.0/lib/zi/America/St_Vincent jre/1.5.0/lib/zi/America/Swift_Current jre/1.5.0/lib/zi/America/Tegucigalpa jre/1.5.0/lib/zi/America/Thule jre/1.5.0/lib/zi/America/Thunder_Bay jre/1.5.0/lib/zi/America/Tijuana jre/1.5.0/lib/zi/America/Toronto jre/1.5.0/lib/zi/America/Tortola jre/1.5.0/lib/zi/America/Vancouver jre/1.5.0/lib/zi/America/Whitehorse jre/1.5.0/lib/zi/America/Winnipeg jre/1.5.0/lib/zi/America/Yakutat jre/1.5.0/lib/zi/America/Yellowknife jre/1.5.0/lib/zi/America/Indiana/Indianapolis jre/1.5.0/lib/zi/America/Indiana/Knox jre/1.5.0/lib/zi/America/Indiana/Marengo jre/1.5.0/lib/zi/America/Indiana/Petersburg jre/1.5.0/lib/zi/America/Indiana/Vevay jre/1.5.0/lib/zi/America/Indiana/Vincennes jre/1.5.0/lib/zi/America/Kentucky/Louisville jre/1.5.0/lib/zi/America/Kentucky/Monticello jre/1.5.0/lib/zi/America/Argentina/Buenos_Aires jre/1.5.0/lib/zi/America/Argentina/Catamarca jre/1.5.0/lib/zi/America/Argentina/Cordoba jre/1.5.0/lib/zi/America/Argentina/Jujuy jre/1.5.0/lib/zi/America/Argentina/La_Rioja jre/1.5.0/lib/zi/America/Argentina/Mendoza jre/1.5.0/lib/zi/America/Argentina/Rio_Gallegos jre/1.5.0/lib/zi/America/Argentina/San_Juan jre/1.5.0/lib/zi/America/Argentina/Tucuman jre/1.5.0/lib/zi/America/Argentina/Ushuaia jre/1.5.0/lib/zi/America/North_Dakota/Center jre/1.5.0/lib/zi/America/North_Dakota/New_Salem jre/1.5.0/lib/zi/Atlantic/Azores jre/1.5.0/lib/zi/Atlantic/Bermuda jre/1.5.0/lib/zi/Atlantic/Canary jre/1.5.0/lib/zi/Atlantic/Cape_Verde jre/1.5.0/lib/zi/Atlantic/Faroe jre/1.5.0/lib/zi/Atlantic/Madeira jre/1.5.0/lib/zi/Atlantic/Reykjavik jre/1.5.0/lib/zi/Atlantic/South_Georgia jre/1.5.0/lib/zi/Atlantic/St_Helena jre/1.5.0/lib/zi/Atlantic/Stanley jre/1.5.0/lib/zi/Australia/Adelaide jre/1.5.0/lib/zi/Australia/Brisbane jre/1.5.0/lib/zi/Australia/Broken_Hill jre/1.5.0/lib/zi/Australia/Currie jre/1.5.0/lib/zi/Australia/Darwin jre/1.5.0/lib/zi/Australia/Eucla jre/1.5.0/lib/zi/Australia/Hobart jre/1.5.0/lib/zi/Australia/Lindeman jre/1.5.0/lib/zi/Australia/Lord_Howe jre/1.5.0/lib/zi/Australia/Melbourne jre/1.5.0/lib/zi/Australia/Perth jre/1.5.0/lib/zi/Australia/Sydney jre/1.5.0/lib/zi/Antarctica/Casey jre/1.5.0/lib/zi/Antarctica/Davis jre/1.5.0/lib/zi/Antarctica/DumontDUrville
INFO: chmod 555 jre/1.5.0/lib/zi/Antarctica/Mawson jre/1.5.0/lib/zi/Antarctica/McMurdo jre/1.5.0/lib/zi/Antarctica/Palmer jre/1.5.0/lib/zi/Antarctica/Rothera jre/1.5.0/lib/zi/Antarctica/Syowa jre/1.5.0/lib/zi/Antarctica/Vostok jre/1.5.0/lib/im/indicim.jar jre/1.5.0/lib/im/thaiim.jar jre/1.5.0/lib/ext/dnsns.jar jre/1.5.0/lib/ext/localedata.jar jre/1.5.0/lib/ext/sunjce_provider.jar jre/1.5.0/lib/cmm/CIEXYZ.pf jre/1.5.0/lib/cmm/GRAY.pf jre/1.5.0/lib/cmm/LINEAR_RGB.pf jre/1.5.0/lib/cmm/PYCC.pf jre/1.5.0/lib/cmm/sRGB.pf jre/1.5.0/lib/fonts/LucidaBrightDemiBold.ttf jre/1.5.0/lib/fonts/LucidaBrightDemiItalic.ttf jre/1.5.0/lib/fonts/LucidaBrightItalic.ttf jre/1.5.0/lib/fonts/LucidaBrightRegular.ttf jre/1.5.0/lib/fonts/LucidaSansDemiBold.ttf jre/1.5.0/lib/fonts/LucidaSansRegular.ttf jre/1.5.0/lib/fonts/LucidaTypewriterBold.ttf jre/1.5.0/lib/fonts/LucidaTypewriterRegular.ttf jre/1.5.0/lib/fonts/fonts.dir jre/1.5.0/lib/audio/soundbank.gm jre/1.5.0/lib/amd64/awt_robot jre/1.5.0/lib/amd64/gtkhelper jre/1.5.0/lib/amd64/jvm.cfg jre/1.5.0/lib/amd64/libJdbcOdbc.so jre/1.5.0/lib/amd64/libawt.so jre/1.5.0/lib/amd64/libcmm.so jre/1.5.0/lib/amd64/libdcpr.so jre/1.5.0/lib/amd64/libdt_socket.so jre/1.5.0/lib/amd64/libfontmanager.so jre/1.5.0/lib/amd64/libhprof.so jre/1.5.0/lib/amd64/libinstrument.so jre/1.5.0/lib/amd64/libioser12.so jre/1.5.0/lib/amd64/libjaas_unix.so jre/1.5.0/lib/amd64/libjava.so jre/1.5.0/lib/amd64/libjava_crw_demo.so jre/1.5.0/lib/amd64/libjawt.so jre/1.5.0/lib/amd64/libjdwp.so jre/1.5.0/lib/amd64/libjpeg.so jre/1.5.0/lib/amd64/libjsig.so jre/1.5.0/lib/amd64/libjsound.so jre/1.5.0/lib/amd64/libjsoundalsa.so jre/1.5.0/lib/amd64/libmanagement.so jre/1.5.0/lib/amd64/libmlib_image.so jre/1.5.0/lib/amd64/libnative_chmod.so jre/1.5.0/lib/amd64/libnet.so jre/1.5.0/lib/amd64/libnio.so jre/1.5.0/lib/amd64/librmi.so jre/1.5.0/lib/amd64/libunpack.so jre/1.5.0/lib/amd64/libverify.so jre/1.5.0/lib/amd64/libzip.so jre/1.5.0/lib/amd64/xawt/libmawt.so jre/1.5.0/lib/amd64/server/libjsig.so jre/1.5.0/lib/amd64/server/Xusage.txt jre/1.5.0/lib/amd64/server/libjvm.so jre/1.5.0/lib/amd64/motif21/libmawt.so jre/1.5.0/lib/amd64/headless/libmawt.so jre/1.5.0/lib/amd64/native_threads/libhpi.so jre/1.5.0/lib/images/cursors/cursors.properties jre/1.5.0/lib/images/cursors/invalid32x32.gif jre/1.5.0/lib/images/cursors/motif_CopyDrop32x32.gif jre/1.5.0/lib/images/cursors/motif_CopyNoDrop32x32.gif jre/1.5.0/lib/images/cursors/motif_LinkDrop32x32.gif jre/1.5.0/lib/images/cursors/motif_LinkNoDrop32x32.gif jre/1.5.0/lib/images/cursors/motif_MoveDrop32x32.gif jre/1.5.0/lib/images/cursors/motif_MoveNoDrop32x32.gif jre/1.5.0/lib/security/US_export_policy.jar jre/1.5.0/lib/security/cacerts jre/1.5.0/lib/security/java.policy jre/1.5.0/lib/security/java.security jre/1.5.0/lib/security/local_policy.jar jre/1.5.0/lib/management/jmxremote.access jre/1.5.0/lib/management/jmxremote.password.template jre/1.5.0/lib/management/management.properties jre/1.5.0/lib/management/snmp.acl.template jre/1.5.0/lib/oblique-fonts/LucidaSansDemiOblique.ttf jre/1.5.0/lib/oblique-fonts/LucidaSansOblique.ttf jre/1.5.0/lib/oblique-fonts/LucidaTypewriterBoldOblique.ttf jre/1.5.0/lib/oblique-fonts/LucidaTypewriterOblique.ttf jre/1.5.0/lib/oblique-fonts/fonts.dir jre/1.5.0/lib/zi.tzdata2006p/CET jre/1.5.0/lib/zi.tzdata2006p/CST6CDT jre/1.5.0/lib/zi.tzdata2006p/EET jre/1.5.0/lib/zi.tzdata2006p/EST jre/1.5.0/lib/zi.tzdata2006p/EST5EDT jre/1.5.0/lib/zi.tzdata2006p/GMT jre/1.5.0/lib/zi.tzdata2006p/HST jre/1.5.0/lib/zi.tzdata2006p/MET jre/1.5.0/lib/zi.tzdata2006p/MST jre/1.5.0/lib/zi.tzdata2006p/MST7MDT jre/1.5.0/lib/zi.tzdata2006p/PST8PDT jre/1.5.0/lib/zi.tzdata2006p/WET jre/1.5.0/lib/zi.tzdata2006p/ZoneInfoMappings jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+1 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+10 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+11 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+12 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+2 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+3 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+4 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+5 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+6 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+7 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+8 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT+9 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-1 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-10 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-11 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-12 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-13 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-14 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-2 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-3 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-4 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-5 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-6 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-7 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-8 jre/1.5.0/lib/zi.tzdata2006p/Etc/GMT-9 jre/1.5.0/lib/zi.tzdata2006p/Etc/UCT jre/1.5.0/lib/zi.tzdata2006p/Etc/UTC jre/1.5.0/lib/zi.tzdata2006p/Asia/Aden jre/1.5.0/lib/zi.tzdata2006p/Asia/Almaty jre/1.5.0/lib/zi.tzdata2006p/Asia/Amman jre/1.5.0/lib/zi.tzdata2006p/Asia/Anadyr jre/1.5.0/lib/zi.tzdata2006p/Asia/Aqtau jre/1.5.0/lib/zi.tzdata2006p/Asia/Aqtobe jre/1.5.0/lib/zi.tzdata2006p/Asia/Ashgabat jre/1.5.0/lib/zi.tzdata2006p/Asia/Baghdad jre/1.5.0/lib/zi.tzdata2006p/Asia/Bahrain jre/1.5.0/lib/zi.tzdata2006p/Asia/Baku jre/1.5.0/lib/zi.tzdata2006p/Asia/Bangkok jre/1.5.0/lib/zi.tzdata2006p/Asia/Beirut jre/1.5.0/lib/zi.tzdata2006p/Asia/Bishkek jre/1.5.0/lib/zi.tzdata2006p/Asia/Brunei jre/1.5.0/lib/zi.tzdata2006p/Asia/Calcutta jre/1.5.0/lib/zi.tzdata2006p/Asia/Choibalsan jre/1.5.0/lib/zi.tzdata2006p/Asia/Chongqing jre/1.5.0/lib/zi.tzdata2006p/Asia/Colombo jre/1.5.0/lib/zi.tzdata2006p/Asia/Damascus jre/1.5.0/lib/zi.tzdata2006p/Asia/Dhaka jre/1.5.0/lib/zi.tzdata2006p/Asia/Dili jre/1.5.0/lib/zi.tzdata2006p/Asia/Dubai jre/1.5.0/lib/zi.tzdata2006p/Asia/Dushanbe jre/1.5.0/lib/zi.tzdata2006p/Asia/Gaza jre/1.5.0/lib/zi.tzdata2006p/Asia/Harbin jre/1.5.0/lib/zi.tzdata2006p/Asia/Hong_Kong jre/1.5.0/lib/zi.tzdata2006p/Asia/Hovd jre/1.5.0/lib/zi.tzdata2006p/Asia/Irkutsk jre/1.5.0/lib/zi.tzdata2006p/Asia/Jakarta jre/1.5.0/lib/zi.tzdata2006p/Asia/Jayapura jre/1.5.0/lib/zi.tzdata2006p/Asia/Jerusalem jre/1.5.0/lib/zi.tzdata2006p/Asia/Kabul jre/1.5.0/lib/zi.tzdata2006p/Asia/Kamchatka jre/1.5.0/lib/zi.tzdata2006p/Asia/Karachi jre/1.5.0/lib/zi.tzdata2006p/Asia/Kashgar jre/1.5.0/lib/zi.tzdata2006p/Asia/Katmandu jre/1.5.0/lib/zi.tzdata2006p/Asia/Krasnoyarsk jre/1.5.0/lib/zi.tzdata2006p/Asia/Kuala_Lumpur jre/1.5.0/lib/zi.tzdata2006p/Asia/Kuching jre/1.5.0/lib/zi.tzdata2006p/Asia/Kuwait jre/1.5.0/lib/zi.tzdata2006p/Asia/Macau jre/1.5.0/lib/zi.tzdata2006p/Asia/Magadan jre/1.5.0/lib/zi.tzdata2006p/Asia/Makassar jre/1.5.0/lib/zi.tzdata2006p/Asia/Manila jre/1.5.0/lib/zi.tzdata2006p/Asia/Muscat jre/1.5.0/lib/zi.tzdata2006p/Asia/Nicosia jre/1.5.0/lib/zi.tzdata2006p/Asia/Novosibirsk jre/1.5.0/lib/zi.tzdata2006p/Asia/Omsk jre/1.5.0/lib/zi.tzdata2006p/Asia/Oral jre/1.5.0/lib/zi.tzdata2006p/Asia/Phnom_Penh jre/1.5.0/lib/zi.tzdata2006p/Asia/Pontianak jre/1.5.0/lib/zi.tzdata2006p/Asia/Pyongyang jre/1.5.0/lib/zi.tzdata2006p/Asia/Qatar jre/1.5.0/lib/zi.tzdata2006p/Asia/Qyzylorda jre/1.5.0/lib/zi.tzdata2006p/Asia/Rangoon jre/1.5.0/lib/zi.tzdata2006p/Asia/Riyadh jre/1.5.0/lib/zi.tzdata2006p/Asia/Riyadh87 jre/1.5.0/lib/zi.tzdata2006p/Asia/Riyadh88 jre/1.5.0/lib/zi.tzdata2006p/Asia/Riyadh89 jre/1.5.0/lib/zi.tzdata2006p/Asia/Saigon jre/1.5.0/lib/zi.tzdata2006p/Asia/Sakhalin jre/1.5.0/lib/zi.tzdata2006p/Asia/Samarkand jre/1.5.0/lib/zi.tzdata2006p/Asia/Seoul jre/1.5.0/lib/zi.tzdata2006p/Asia/Shanghai jre/1.5.0/lib/zi.tzdata2006p/Asia/Singapore jre/1.5.0/lib/zi.tzdata2006p/Asia/Taipei jre/1.5.0/lib/zi.tzdata2006p/Asia/Tashkent jre/1.5.0/lib/zi.tzdata2006p/Asia/Tbilisi jre/1.5.0/lib/zi.tzdata2006p/Asia/Tehran jre/1.5.0/lib/zi.tzdata2006p/Asia/Thimphu jre/1.5.0/lib/zi.tzdata2006p/Asia/Tokyo jre/1.5.0/lib/zi.tzdata2006p/Asia/Ulaanbaatar jre/1.5.0/lib/zi.tzdata2006p/Asia/Urumqi jre/1.5.0/lib/zi.tzdata2006p/Asia/Vientiane jre/1.5.0/lib/zi.tzdata2006p/Asia/Vladivostok jre/1.5.0/lib/zi.tzdata2006p/Asia/Yakutsk jre/1.5.0/lib/zi.tzdata2006p/Asia/Yekaterinburg jre/1.5.0/lib/zi.tzdata2006p/Asia/Yerevan jre/1.5.0/lib/zi.tzdata2006p/Indian/Antananarivo jre/1.5.0/lib/zi.tzdata2006p/Indian/Chagos jre/1.5.0/lib/zi.tzdata2006p/Indian/Christmas jre/1.5.0/lib/zi.tzdata2006p/Indian/Cocos jre/1.5.0/lib/zi.tzdata2006p/Indian/Comoro jre/1.5.0/lib/zi.tzdata2006p/Indian/Kerguelen jre/1.5.0/lib/zi.tzdata2006p/Indian/Mahe jre/1.5.0/lib/zi.tzdata2006p/Indian/Maldives jre/1.5.0/lib/zi.tzdata2006p/Indian/Mauritius jre/1.5.0/lib/zi.tzdata2006p/Indian/Mayotte jre/1.5.0/lib/zi.tzdata2006p/Indian/Reunion jre/1.5.0/lib/zi.tzdata2006p/Europe/Amsterdam jre/1.5.0/lib/zi.tzdata2006p/Europe/Andorra jre/1.5.0/lib/zi.tzdata2006p/Europe/Athens jre/1.5.0/lib/zi.tzdata2006p/Europe/Belgrade jre/1.5.0/lib/zi.tzdata2006p/Europe/Berlin jre/1.5.0/lib/zi.tzdata2006p/Europe/Brussels jre/1.5.0/lib/zi.tzdata2006p/Europe/Bucharest jre/1.5.0/lib/zi.tzdata2006p/Europe/Budapest jre/1.5.0/lib/zi.tzdata2006p/Europe/Chisinau jre/1.5.0/lib/zi.tzdata2006p/Europe/Copenhagen jre/1.5.0/lib/zi.tzdata2006p/Europe/Dublin jre/1.5.0/lib/zi.tzdata2006p/Europe/Gibraltar jre/1.5.0/lib/zi.tzdata2006p/Europe/Helsinki jre/1.5.0/lib/zi.tzdata2006p/Europe/Istanbul jre/1.5.0/lib/zi.tzdata2006p/Europe/Kaliningrad jre/1.5.0/lib/zi.tzdata2006p/Europe/Kiev jre/1.5.0/lib/zi.tzdata2006p/Europe/Lisbon jre/1.5.0/lib/zi.tzdata2006p/Europe/London jre/1.5.0/lib/zi.tzdata2006p/Europe/Luxembourg jre/1.5.0/lib/zi.tzdata2006p/Europe/Madrid jre/1.5.0/lib/zi.tzdata2006p/Europe/Malta jre/1.5.0/lib/zi.tzdata2006p/Europe/Minsk jre/1.5.0/lib/zi.tzdata2006p/Europe/Monaco jre/1.5.0/lib/zi.tzdata2006p/Europe/Moscow jre/1.5.0/lib/zi.tzdata2006p/Europe/Oslo jre/1.5.0/lib/zi.tzdata2006p/Europe/Paris jre/1.5.0/lib/zi.tzdata2006p/Europe/Prague jre/1.5.0/lib/zi.tzdata2006p/Europe/Riga jre/1.5.0/lib/zi.tzdata2006p/Europe/Rome jre/1.5.0/lib/zi.tzdata2006p/Europe/Samara jre/1.5.0/lib/zi.tzdata2006p/Europe/Simferopol jre/1.5.0/lib/zi.tzdata2006p/Europe/Sofia jre/1.5.0/lib/zi.tzdata2006p/Europe/Stockholm jre/1.5.0/lib/zi.tzdata2006p/Europe/Tallinn jre/1.5.0/lib/zi.tzdata2006p/Europe/Tirane jre/1.5.0/lib/zi.tzdata2006p/Europe/Uzhgorod jre/1.5.0/lib/zi.tzdata2006p/Europe/Vaduz jre/1.5.0/lib/zi.tzdata2006p/Europe/Vienna jre/1.5.0/lib/zi.tzdata2006p/Europe/Vilnius
INFO: chmod 555 jre/1.5.0/lib/zi.tzdata2006p/Europe/Volgograd jre/1.5.0/lib/zi.tzdata2006p/Europe/Warsaw jre/1.5.0/lib/zi.tzdata2006p/Europe/Zaporozhye jre/1.5.0/lib/zi.tzdata2006p/Europe/Zurich jre/1.5.0/lib/zi.tzdata2006p/Africa/Abidjan jre/1.5.0/lib/zi.tzdata2006p/Africa/Accra jre/1.5.0/lib/zi.tzdata2006p/Africa/Addis_Ababa jre/1.5.0/lib/zi.tzdata2006p/Africa/Algiers jre/1.5.0/lib/zi.tzdata2006p/Africa/Asmera jre/1.5.0/lib/zi.tzdata2006p/Africa/Bamako jre/1.5.0/lib/zi.tzdata2006p/Africa/Bangui jre/1.5.0/lib/zi.tzdata2006p/Africa/Banjul jre/1.5.0/lib/zi.tzdata2006p/Africa/Bissau jre/1.5.0/lib/zi.tzdata2006p/Africa/Blantyre jre/1.5.0/lib/zi.tzdata2006p/Africa/Brazzaville jre/1.5.0/lib/zi.tzdata2006p/Africa/Bujumbura jre/1.5.0/lib/zi.tzdata2006p/Africa/Cairo jre/1.5.0/lib/zi.tzdata2006p/Africa/Casablanca jre/1.5.0/lib/zi.tzdata2006p/Africa/Ceuta jre/1.5.0/lib/zi.tzdata2006p/Africa/Conakry jre/1.5.0/lib/zi.tzdata2006p/Africa/Dakar jre/1.5.0/lib/zi.tzdata2006p/Africa/Dar_es_Salaam jre/1.5.0/lib/zi.tzdata2006p/Africa/Djibouti jre/1.5.0/lib/zi.tzdata2006p/Africa/Douala jre/1.5.0/lib/zi.tzdata2006p/Africa/El_Aaiun jre/1.5.0/lib/zi.tzdata2006p/Africa/Freetown jre/1.5.0/lib/zi.tzdata2006p/Africa/Gaborone jre/1.5.0/lib/zi.tzdata2006p/Africa/Harare jre/1.5.0/lib/zi.tzdata2006p/Africa/Johannesburg jre/1.5.0/lib/zi.tzdata2006p/Africa/Kampala jre/1.5.0/lib/zi.tzdata2006p/Africa/Khartoum jre/1.5.0/lib/zi.tzdata2006p/Africa/Kigali jre/1.5.0/lib/zi.tzdata2006p/Africa/Kinshasa jre/1.5.0/lib/zi.tzdata2006p/Africa/Lagos jre/1.5.0/lib/zi.tzdata2006p/Africa/Libreville jre/1.5.0/lib/zi.tzdata2006p/Africa/Lome jre/1.5.0/lib/zi.tzdata2006p/Africa/Luanda jre/1.5.0/lib/zi.tzdata2006p/Africa/Lubumbashi jre/1.5.0/lib/zi.tzdata2006p/Africa/Lusaka jre/1.5.0/lib/zi.tzdata2006p/Africa/Malabo jre/1.5.0/lib/zi.tzdata2006p/Africa/Maputo jre/1.5.0/lib/zi.tzdata2006p/Africa/Maseru jre/1.5.0/lib/zi.tzdata2006p/Africa/Mbabane jre/1.5.0/lib/zi.tzdata2006p/Africa/Mogadishu jre/1.5.0/lib/zi.tzdata2006p/Africa/Monrovia jre/1.5.0/lib/zi.tzdata2006p/Africa/Nairobi jre/1.5.0/lib/zi.tzdata2006p/Africa/Ndjamena jre/1.5.0/lib/zi.tzdata2006p/Africa/Niamey jre/1.5.0/lib/zi.tzdata2006p/Africa/Nouakchott jre/1.5.0/lib/zi.tzdata2006p/Africa/Ouagadougou jre/1.5.0/lib/zi.tzdata2006p/Africa/Porto-Novo jre/1.5.0/lib/zi.tzdata2006p/Africa/Sao_Tome jre/1.5.0/lib/zi.tzdata2006p/Africa/Tripoli jre/1.5.0/lib/zi.tzdata2006p/Africa/Tunis jre/1.5.0/lib/zi.tzdata2006p/Africa/Windhoek jre/1.5.0/lib/zi.tzdata2006p/SystemV/AST4 jre/1.5.0/lib/zi.tzdata2006p/SystemV/AST4ADT jre/1.5.0/lib/zi.tzdata2006p/SystemV/CST6 jre/1.5.0/lib/zi.tzdata2006p/SystemV/CST6CDT jre/1.5.0/lib/zi.tzdata2006p/SystemV/EST5 jre/1.5.0/lib/zi.tzdata2006p/SystemV/EST5EDT jre/1.5.0/lib/zi.tzdata2006p/SystemV/HST10 jre/1.5.0/lib/zi.tzdata2006p/SystemV/MST7 jre/1.5.0/lib/zi.tzdata2006p/SystemV/MST7MDT jre/1.5.0/lib/zi.tzdata2006p/SystemV/PST8 jre/1.5.0/lib/zi.tzdata2006p/SystemV/PST8PDT jre/1.5.0/lib/zi.tzdata2006p/SystemV/YST9 jre/1.5.0/lib/zi.tzdata2006p/SystemV/YST9YDT jre/1.5.0/lib/zi.tzdata2006p/Pacific/Apia jre/1.5.0/lib/zi.tzdata2006p/Pacific/Auckland jre/1.5.0/lib/zi.tzdata2006p/Pacific/Chatham jre/1.5.0/lib/zi.tzdata2006p/Pacific/Easter jre/1.5.0/lib/zi.tzdata2006p/Pacific/Efate jre/1.5.0/lib/zi.tzdata2006p/Pacific/Enderbury jre/1.5.0/lib/zi.tzdata2006p/Pacific/Fakaofo jre/1.5.0/lib/zi.tzdata2006p/Pacific/Fiji jre/1.5.0/lib/zi.tzdata2006p/Pacific/Funafuti jre/1.5.0/lib/zi.tzdata2006p/Pacific/Galapagos jre/1.5.0/lib/zi.tzdata2006p/Pacific/Gambier jre/1.5.0/lib/zi.tzdata2006p/Pacific/Guadalcanal jre/1.5.0/lib/zi.tzdata2006p/Pacific/Guam jre/1.5.0/lib/zi.tzdata2006p/Pacific/Honolulu jre/1.5.0/lib/zi.tzdata2006p/Pacific/Johnston jre/1.5.0/lib/zi.tzdata2006p/Pacific/Kiritimati jre/1.5.0/lib/zi.tzdata2006p/Pacific/Kosrae jre/1.5.0/lib/zi.tzdata2006p/Pacific/Kwajalein jre/1.5.0/lib/zi.tzdata2006p/Pacific/Majuro jre/1.5.0/lib/zi.tzdata2006p/Pacific/Marquesas jre/1.5.0/lib/zi.tzdata2006p/Pacific/Midway jre/1.5.0/lib/zi.tzdata2006p/Pacific/Nauru jre/1.5.0/lib/zi.tzdata2006p/Pacific/Niue jre/1.5.0/lib/zi.tzdata2006p/Pacific/Norfolk jre/1.5.0/lib/zi.tzdata2006p/Pacific/Noumea jre/1.5.0/lib/zi.tzdata2006p/Pacific/Pago_Pago jre/1.5.0/lib/zi.tzdata2006p/Pacific/Palau jre/1.5.0/lib/zi.tzdata2006p/Pacific/Pitcairn jre/1.5.0/lib/zi.tzdata2006p/Pacific/Ponape jre/1.5.0/lib/zi.tzdata2006p/Pacific/Port_Moresby jre/1.5.0/lib/zi.tzdata2006p/Pacific/Rarotonga jre/1.5.0/lib/zi.tzdata2006p/Pacific/Saipan jre/1.5.0/lib/zi.tzdata2006p/Pacific/Tahiti jre/1.5.0/lib/zi.tzdata2006p/Pacific/Tarawa jre/1.5.0/lib/zi.tzdata2006p/Pacific/Tongatapu jre/1.5.0/lib/zi.tzdata2006p/Pacific/Truk jre/1.5.0/lib/zi.tzdata2006p/Pacific/Wake jre/1.5.0/lib/zi.tzdata2006p/Pacific/Wallis jre/1.5.0/lib/zi.tzdata2006p/America/Adak jre/1.5.0/lib/zi.tzdata2006p/America/Anchorage jre/1.5.0/lib/zi.tzdata2006p/America/Anguilla jre/1.5.0/lib/zi.tzdata2006p/America/Antigua jre/1.5.0/lib/zi.tzdata2006p/America/Araguaina jre/1.5.0/lib/zi.tzdata2006p/America/Aruba jre/1.5.0/lib/zi.tzdata2006p/America/Asuncion jre/1.5.0/lib/zi.tzdata2006p/America/Atikokan jre/1.5.0/lib/zi.tzdata2006p/America/Bahia jre/1.5.0/lib/zi.tzdata2006p/America/Barbados jre/1.5.0/lib/zi.tzdata2006p/America/Belem jre/1.5.0/lib/zi.tzdata2006p/America/Belize jre/1.5.0/lib/zi.tzdata2006p/America/Blanc-Sablon jre/1.5.0/lib/zi.tzdata2006p/America/Boa_Vista jre/1.5.0/lib/zi.tzdata2006p/America/Bogota jre/1.5.0/lib/zi.tzdata2006p/America/Boise jre/1.5.0/lib/zi.tzdata2006p/America/Cambridge_Bay jre/1.5.0/lib/zi.tzdata2006p/America/Campo_Grande jre/1.5.0/lib/zi.tzdata2006p/America/Cancun jre/1.5.0/lib/zi.tzdata2006p/America/Caracas jre/1.5.0/lib/zi.tzdata2006p/America/Cayenne jre/1.5.0/lib/zi.tzdata2006p/America/Cayman jre/1.5.0/lib/zi.tzdata2006p/America/Chicago jre/1.5.0/lib/zi.tzdata2006p/America/Chihuahua jre/1.5.0/lib/zi.tzdata2006p/America/Costa_Rica jre/1.5.0/lib/zi.tzdata2006p/America/Cuiaba jre/1.5.0/lib/zi.tzdata2006p/America/Curacao jre/1.5.0/lib/zi.tzdata2006p/America/Danmarkshavn jre/1.5.0/lib/zi.tzdata2006p/America/Dawson jre/1.5.0/lib/zi.tzdata2006p/America/Dawson_Creek jre/1.5.0/lib/zi.tzdata2006p/America/Denver jre/1.5.0/lib/zi.tzdata2006p/America/Detroit jre/1.5.0/lib/zi.tzdata2006p/America/Dominica jre/1.5.0/lib/zi.tzdata2006p/America/Edmonton jre/1.5.0/lib/zi.tzdata2006p/America/Eirunepe jre/1.5.0/lib/zi.tzdata2006p/America/El_Salvador jre/1.5.0/lib/zi.tzdata2006p/America/Fortaleza jre/1.5.0/lib/zi.tzdata2006p/America/Glace_Bay jre/1.5.0/lib/zi.tzdata2006p/America/Godthab jre/1.5.0/lib/zi.tzdata2006p/America/Goose_Bay jre/1.5.0/lib/zi.tzdata2006p/America/Grand_Turk jre/1.5.0/lib/zi.tzdata2006p/America/Grenada jre/1.5.0/lib/zi.tzdata2006p/America/Guadeloupe jre/1.5.0/lib/zi.tzdata2006p/America/Guatemala jre/1.5.0/lib/zi.tzdata2006p/America/Guayaquil jre/1.5.0/lib/zi.tzdata2006p/America/Guyana jre/1.5.0/lib/zi.tzdata2006p/America/Halifax jre/1.5.0/lib/zi.tzdata2006p/America/Havana jre/1.5.0/lib/zi.tzdata2006p/America/Hermosillo jre/1.5.0/lib/zi.tzdata2006p/America/Inuvik jre/1.5.0/lib/zi.tzdata2006p/America/Iqaluit jre/1.5.0/lib/zi.tzdata2006p/America/Jamaica jre/1.5.0/lib/zi.tzdata2006p/America/Juneau jre/1.5.0/lib/zi.tzdata2006p/America/La_Paz jre/1.5.0/lib/zi.tzdata2006p/America/Lima jre/1.5.0/lib/zi.tzdata2006p/America/Los_Angeles jre/1.5.0/lib/zi.tzdata2006p/America/Maceio jre/1.5.0/lib/zi.tzdata2006p/America/Managua jre/1.5.0/lib/zi.tzdata2006p/America/Manaus jre/1.5.0/lib/zi.tzdata2006p/America/Martinique jre/1.5.0/lib/zi.tzdata2006p/America/Mazatlan jre/1.5.0/lib/zi.tzdata2006p/America/Menominee jre/1.5.0/lib/zi.tzdata2006p/America/Merida jre/1.5.0/lib/zi.tzdata2006p/America/Mexico_City jre/1.5.0/lib/zi.tzdata2006p/America/Miquelon jre/1.5.0/lib/zi.tzdata2006p/America/Moncton jre/1.5.0/lib/zi.tzdata2006p/America/Monterrey jre/1.5.0/lib/zi.tzdata2006p/America/Montevideo jre/1.5.0/lib/zi.tzdata2006p/America/Montreal jre/1.5.0/lib/zi.tzdata2006p/America/Montserrat jre/1.5.0/lib/zi.tzdata2006p/America/Nassau jre/1.5.0/lib/zi.tzdata2006p/America/New_York jre/1.5.0/lib/zi.tzdata2006p/America/Nipigon jre/1.5.0/lib/zi.tzdata2006p/America/Nome jre/1.5.0/lib/zi.tzdata2006p/America/Noronha jre/1.5.0/lib/zi.tzdata2006p/America/Panama jre/1.5.0/lib/zi.tzdata2006p/America/Pangnirtung jre/1.5.0/lib/zi.tzdata2006p/America/Paramaribo jre/1.5.0/lib/zi.tzdata2006p/America/Phoenix jre/1.5.0/lib/zi.tzdata2006p/America/Port-au-Prince jre/1.5.0/lib/zi.tzdata2006p/America/Port_of_Spain jre/1.5.0/lib/zi.tzdata2006p/America/Porto_Velho jre/1.5.0/lib/zi.tzdata2006p/America/Puerto_Rico jre/1.5.0/lib/zi.tzdata2006p/America/Rainy_River jre/1.5.0/lib/zi.tzdata2006p/America/Rankin_Inlet jre/1.5.0/lib/zi.tzdata2006p/America/Recife jre/1.5.0/lib/zi.tzdata2006p/America/Regina jre/1.5.0/lib/zi.tzdata2006p/America/Rio_Branco jre/1.5.0/lib/zi.tzdata2006p/America/Santiago jre/1.5.0/lib/zi.tzdata2006p/America/Santo_Domingo jre/1.5.0/lib/zi.tzdata2006p/America/Sao_Paulo jre/1.5.0/lib/zi.tzdata2006p/America/Scoresbysund jre/1.5.0/lib/zi.tzdata2006p/America/St_Johns jre/1.5.0/lib/zi.tzdata2006p/America/St_Kitts jre/1.5.0/lib/zi.tzdata2006p/America/St_Lucia jre/1.5.0/lib/zi.tzdata2006p/America/St_Thomas jre/1.5.0/lib/zi.tzdata2006p/America/St_Vincent jre/1.5.0/lib/zi.tzdata2006p/America/Swift_Current jre/1.5.0/lib/zi.tzdata2006p/America/Tegucigalpa jre/1.5.0/lib/zi.tzdata2006p/America/Thule jre/1.5.0/lib/zi.tzdata2006p/America/Thunder_Bay jre/1.5.0/lib/zi.tzdata2006p/America/Tijuana jre/1.5.0/lib/zi.tzdata2006p/America/Toronto jre/1.5.0/lib/zi.tzdata2006p/America/Tortola jre/1.5.0/lib/zi.tzdata2006p/America/Vancouver jre/1.5.0/lib/zi.tzdata2006p/America/Whitehorse jre/1.5.0/lib/zi.tzdata2006p/America/Winnipeg jre/1.5.0/lib/zi.tzdata2006p/America/Yakutat jre/1.5.0/lib/zi.tzdata2006p/America/Yellowknife jre/1.5.0/lib/zi.tzdata2006p/America/Indiana/Indianapolis jre/1.5.0/lib/zi.tzdata2006p/America/Indiana/Knox jre/1.5.0/lib/zi.tzdata2006p/America/Indiana/Marengo jre/1.5.0/lib/zi.tzdata2006p/America/Indiana/Petersburg jre/1.5.0/lib/zi.tzdata2006p/America/Indiana/Vevay jre/1.5.0/lib/zi.tzdata2006p/America/Indiana/Vincennes jre/1.5.0/lib/zi.tzdata2006p/America/Kentucky/Louisville jre/1.5.0/lib/zi.tzdata2006p/America/Kentucky/Monticello jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Buenos_Aires jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Catamarca jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Cordoba jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Jujuy jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/La_Rioja jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Mendoza jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Rio_Gallegos jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/San_Juan jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Tucuman jre/1.5.0/lib/zi.tzdata2006p/America/Argentina/Ushuaia jre/1.5.0/lib/zi.tzdata2006p/America/North_Dakota/Center jre/1.5.0/lib/zi.tzdata2006p/America/North_Dakota/New_Salem jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Azores jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Bermuda jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Canary jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Cape_Verde jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Faeroe jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Madeira jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Reykjavik jre/1.5.0/lib/zi.tzdata2006p/Atlantic/South_Georgia jre/1.5.0/lib/zi.tzdata2006p/Atlantic/St_Helena jre/1.5.0/lib/zi.tzdata2006p/Atlantic/Stanley jre/1.5.0/lib/zi.tzdata2006p/Australia/Adelaide jre/1.5.0/lib/zi.tzdata2006p/Australia/Brisbane jre/1.5.0/lib/zi.tzdata2006p/Australia/Broken_Hill jre/1.5.0/lib/zi.tzdata2006p/Australia/Currie jre/1.5.0/lib/zi.tzdata2006p/Australia/Darwin jre/1.5.0/lib/zi.tzdata2006p/Australia/Hobart jre/1.5.0/lib/zi.tzdata2006p/Australia/Lindeman jre/1.5.0/lib/zi.tzdata2006p/Australia/Lord_Howe jre/1.5.0/lib/zi.tzdata2006p/Australia/Melbourne jre/1.5.0/lib/zi.tzdata2006p/Australia/Perth
INFO: chmod 555 jre/1.5.0/lib/zi.tzdata2006p/Australia/Sydney jre/1.5.0/lib/zi.tzdata2006p/Antarctica/Casey jre/1.5.0/lib/zi.tzdata2006p/Antarctica/Davis jre/1.5.0/lib/zi.tzdata2006p/Antarctica/DumontDUrville jre/1.5.0/lib/zi.tzdata2006p/Antarctica/Mawson jre/1.5.0/lib/zi.tzdata2006p/Antarctica/McMurdo jre/1.5.0/lib/zi.tzdata2006p/Antarctica/Palmer jre/1.5.0/lib/zi.tzdata2006p/Antarctica/Rothera jre/1.5.0/lib/zi.tzdata2006p/Antarctica/Syowa jre/1.5.0/lib/zi.tzdata2006p/Antarctica/Vostok jre/1.5.0/bin/java jre/1.5.0/bin/keytool jre/1.5.0/bin/kinit jre/1.5.0/bin/klist jre/1.5.0/bin/ktab jre/1.5.0/bin/orbd jre/1.5.0/bin/pack200 jre/1.5.0/bin/policytool jre/1.5.0/bin/rmid jre/1.5.0/bin/rmiregistry jre/1.5.0/bin/servertool jre/1.5.0/bin/tnameserv jre/1.5.0/bin/unpack200 jre/1.5.0/.systemPrefs/.system.lock jre/1.5.0/.systemPrefs/.systemRootModFile
INFO:

INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:

INFO: End output from spawned process.
INFO: ----------------------------------
INFO: DONE Executing permissions file from :/tmp/OraInstall2012-10-04_12-48-35AM/fastcopy/setperms1.sh
INFO: 10/4/12 12:49:21 AM PDT: Starting install Install Phase 1 of component Java Runtime Environment
INFO: Calling Action generalActions10.2.0.9.0  changePermissions
source = /scratch/sandgoya/installations/oui111/jre/1.5.0/bin
permissions = 775

INFO: Calling Action generalActions10.2.0.9.0  changePermissions
source = /scratch/sandgoya/installations/oui111/jre/1.5.0/lib
permissions = 775

INFO: Calling Action generalActions10.2.0.9.0  changePermissions
source = /scratch/sandgoya/installations/oui111/jre/1.5.0/lib/security
permissions = 775

INFO: Calling Query fileQueries10.1.0.3.0  exists

filename = /scratch/sandgoya/installations/oui111/jre/1.5.0/lib/i386
INFO: Query Returned: false
INFO: Calling Query fileQueries10.1.0.3.0  exists

filename = /scratch/sandgoya/installations/oui111/jre/1.5.0/lib/amd64
INFO: Query Returned: true
INFO: Calling Action generalActions10.2.0.9.0  changePermissions
source = /scratch/sandgoya/installations/oui111/jre/1.5.0/lib/amd64
permissions = 775

INFO: Calling Action generalActions10.2.0.9.0  changePermissions
source = /scratch/sandgoya/installations/oui111/jre/1.5.0/lib/amd64/native_threads
permissions = 775

INFO: 10/4/12 12:49:21 AM PDT: Starting install Install Phase 1 of component Installer SDK Component
INFO: 10/4/12 12:49:21 AM PDT: Starting install Install Phase 1 of component Oracle One-Off Patch Installer
INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/OPatch/opatch.ini
destination = /scratch/sandgoya/installations/oui111/OPatch/opatch.ini
variables = null
delimiter = null
encoding = null

INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 1 of component Oracle Universal Installer
INFO: Setting variable 'platDir' to 'linux64'. Received the value from a code block.
INFO: Setting variable 'MSVCREDIST_LOC' to ''. Received the value from a code block.
INFO: Setting variable 'MSVCREDIST_FLAGS' to ''. Received the value from a code block.
INFO: Setting variable 'MSVCREDIST_INSTALL' to ''. Received the value from a code block.
INFO: Calling Query areasQueries10.2.0.1.0  getProductHome

name = oracle.jdk

startVersion = 1.5

endVersion = 1.5

acceptCompatible = null
INFO:
Query Exception: ProductNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException
INFO: Not found
INFO: Setting variable 'JRE_LOCATION' to 'Not found'. Received the value from a code block.
INFO: Calling Query areasQueries10.2.0.1.0  getProductHome

name = oracle.swd.jre

startVersion = 1.3.1

endVersion = 1.4.2

acceptCompatible = null
INFO: Setting the PROD_HOME variable of 'oracle.swd.jre_1.5.0.11.0' to '/scratch/sandgoya/installations/oui111/jre/1.5.0'. Received the value from the variable calculation.
INFO: Query Returned: /scratch/sandgoya/installations/oui111/jre/1.5.0
INFO: Setting variable 'JRE_LOCATION' to '/scratch/sandgoya/installations/oui111/jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'JRE_LOCATION' to '/scratch/sandgoya/installations/oui111/jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'ABSOLUTE_JRE_LOCATION' to '/scratch/sandgoya/installations/oui111/jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'JRE_LOCATION' to '/jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'JRE_LOCATION' to 'jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'JRE_LOCATION' to '../../jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'JRE_LOCATION' to '../../jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'ABSOLUTE_JRE_LOCATION' to '/scratch/sandgoya/installations/oui111/jre/1.5.0'. Received the value from a code block.
INFO: Setting variable 'JRE_MEMORY_OPTIONS' to '" -mx96m"'. Received the value from a code block.
INFO: Calling Action fileActions11.2.0.2.0  moveFile
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/runInstaller.var
destination = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/runInstaller.sh

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/runInstaller.sh
destination = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/runInstaller.sh
variables = null
delimiter = null
encoding = null

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/addNode.sh
destination = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/addNode.sh
variables = null
delimiter = null
encoding = null

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/attachHome.sh
destination = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/attachHome.sh
variables = null
delimiter = null
encoding = null

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/detachHome.sh
destination = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/detachHome.sh
variables = null
delimiter = null
encoding = null

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/addLangs.sh
destination = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/addLangs.sh
variables = null
delimiter = null
encoding = null

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/runConfig.sh
destination = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/runConfig.sh
variables = null
delimiter = null
encoding = null

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/oraparam.ini
destination = /scratch/sandgoya/installations/oui111/oui/oraparam.ini
variables = null
delimiter = null
encoding = null

INFO: Calling Action fileActions11.2.0.2.0  instantiateFileEx
source = /scratch/sandgoya/installations/oui111/oui/clusterparam.ini
destination = /scratch/sandgoya/installations/oui111/oui/clusterparam.ini
variables = null
delimiter = null
encoding = null

INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 1 of component Oracle Installation Libraries
INFO: Calling Action fileActions11.2.0.2.0  copyGroupFromJar
selectedNodes = null
copyGroup = filegroup1
permissions = null
owner = null
group = null
copyAsText = null
JarLoc = /tmp/OraInstall2012-10-04_12-48-35AM/temp1
gpEntries = [[dbActions.jar ->%PROD_HOME%/dbActions.jar 26061 plats=1=>[46] langs=1=>[en]]
, [fileActionLib.jar ->%PROD_HOME%/fileActionLib.jar 233472 plats=1=>[46] langs=1=>[en]]
, [generalActions.jar ->%PROD_HOME%/generalActions.jar 199674 plats=1=>[46] langs=1=>[en]]
, [jarActionLib.jar ->%PROD_HOME%/jarActionLib.jar 24530 plats=1=>[46] langs=1=>[en]]
, [ntServicesActions.jar ->%PROD_HOME%/ntServicesActions.jar 124605 plats=1=>[46] langs=1=>[en]]
, [unixActions.jar ->%PROD_HOME%/unixActions.jar 69460 plats=1=>[46] langs=1=>[en]]
, [w32RegActionLib.jar ->%PROD_HOME%/w32RegActionLib.jar 48979 plats=1=>[46] langs=1=>[en]]
, [WindowsFolders.jar ->%PROD_HOME%/WindowsFolders.jar 118524 plats=1=>[46] langs=1=>[en]]
, [WindowsGeneralQueries.jar ->%PROD_HOME%/WindowsGeneralQueries.jar 64294 plats=1=>[46] langs=1=>[en]]
, [NtServiceQueries.jar ->%PROD_HOME%/NtServiceQueries.jar 84667 plats=1=>[46] langs=1=>[en]]
, [dbQueries.jar ->%PROD_HOME%/dbQueries.jar 14867 plats=1=>[46] langs=1=>[en]]
, [fileQueries.jar ->%PROD_HOME%/fileQueries.jar 27901 plats=1=>[46] langs=1=>[en]]
, [generalQueries.jar ->%PROD_HOME%/generalQueries.jar 86474 plats=1=>[46] langs=1=>[en]]
, [areasQueries.jar ->%PROD_HOME%/areasQueries.jar 64723 plats=1=>[46] langs=1=>[en]]
, [standardDialogs.jar ->%PROD_HOME%/standardDialogs.jar 62126 plats=1=>[46] langs=1=>[en]]
, [unixQueries.jar ->%PROD_HOME%/unixQueries.jar 17517 plats=1=>[46] langs=1=>[en]]
, [w32RegQueryLib.jar ->%PROD_HOME%/w32RegQueryLib.jar 50172 plats=1=>[46] langs=1=>[en]]
, [rgsQueries.jar ->%PROD_HOME%/rgsQueries.jar 53905 plats=1=>[46] langs=1=>[en]]
, [rgsActions.jar ->%PROD_HOME%/rgsActions.jar 36396 plats=1=>[46] langs=1=>[en]]
, [launchpadaction.jar ->%PROD_HOME%/launchpadaction.jar 43914 plats=1=>[46] langs=1=>[en]]
, [w32OcxLib.jar ->%PROD_HOME%/w32OcxLib.jar 57750 plats=1=>[46] langs=1=>[en]]
, [netQueries.jar ->%PROD_HOME%/netQueries.jar 21903 plats=1=>[46] langs=1=>[en]]
, [spawnActions.jar ->%PROD_HOME%/spawnActions.jar 13900 plats=1=>[46] langs=1=>[en]]
, [wingeneralActionLib.jar ->%PROD_HOME%/wingeneralActionLib.jar 32583 plats=1=>[46] langs=1=>[en]]
]
DllGroup = false

INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 1 of component Oracle Installation Products
INFO: Install Phase 1 JRE files in Scratch :1045
INFO: Going to execute the post copy script
INFO: Post copy script loc :
INFO: 10/4/12 12:49:22 AM PDT: Starting install Link Phase of component Java Runtime Environment
INFO: 10/4/12 12:49:22 AM PDT: Starting install Link Phase of component Installer SDK Component
INFO: 10/4/12 12:49:22 AM PDT: Starting install Link Phase of component Oracle One-Off Patch Installer
INFO: 10/4/12 12:49:22 AM PDT: Starting install Link Phase of component Oracle Universal Installer
INFO: 10/4/12 12:49:22 AM PDT: Starting install Link Phase of component Oracle Installation Libraries
INFO: 10/4/12 12:49:22 AM PDT: Starting install Link Phase of component Oracle Installation Products
INFO: Link Phase JRE files in Scratch :1045
INFO: Checkpoint:checkpointfile :/scratch/sandgoya/installations/oui111/inventory/checkpoints/oui/checkpoint_OUIHome1111.xml not found,creating one for this session
INFO: Checkpoint:constructing checkpoint with name:oracle.installer.install in checkpoint factory
INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 2 of component Java Runtime Environment
INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 2 of component Installer SDK Component
INFO: Setting variable 'platDir' to 'linux64'. Received the value from a code block.
INFO: Calling Action fileActions11.2.0.2.0  removeFile
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/oraparam.ini

INFO: Calling Action fileActions11.2.0.2.0  removeFile
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/clusterparam.ini

INFO: Calling Action fileActions11.2.0.2.0  removeFile
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64/unzip

INFO: Calling Action fileActions11.2.0.2.0  copyFilesToDir
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/bin/platform/linux64
destination = /scratch/sandgoya/installations/oui111/oui/bin

INFO: Calling Action fileActions11.2.0.2.0  removeDir
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/bin/platform

INFO: Calling Action fileActions11.2.0.2.0  copyFilesToDir
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/lib/linux64
destination = /scratch/sandgoya/installations/oui111/oui/libplatform

INFO: Calling Action fileActions11.2.0.2.0  removeDir
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/lib

INFO: Calling Action fileActions11.2.0.2.0  copyFilesToDir
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/libplatform
destination = /scratch/sandgoya/installations/oui111/oui/lib/linux64

INFO: Calling Action fileActions11.2.0.2.0  removeDir
selectedNodes = null
source = /scratch/sandgoya/installations/oui111/oui/libplatform

INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 2 of component Oracle One-Off Patch Installer
INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 2 of component Oracle Universal Installer
INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 2 of component Oracle Installation Libraries
INFO: 10/4/12 12:49:22 AM PDT: Starting install Install Phase 2 of component Oracle Installation Products
INFO: Install Phase 2 JRE files in Scratch :1045
INFO: Checkpoint:Failed Checkpoint found returning it for getAllFailedCheckPoints.
INFO: Checkpoint:Failed Checkpoint found returning null for getLastFailedCheckPoint.
INFO: Checkpoint:Index file written and updated
INFO: OiicSaveInvWCCE:Before saving the inventory. This is a install session.
INFO: OiicSaveInvWCCE:Before saving the inventory. The platform is unix.
INFO: OiicSaveInvWCCE:Before saving the inventory. The root.sh location is /scratch/sandgoya/installations/oui111/root.sh
INFO: Initializing OUI save inventory
INFO: Saving global variables for component oracle.swd
INFO: Saving global variables completed
INFO: Saving the install inventory which has the access of 1
INFO:

INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:

INFO:

INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:

INFO: The options set for this home (/scratch/sandgoya/installations/oui111) are:guid|addedToCI
INFO: Updating XML inventory.
INFO: Saving a backup of inventory for home:/scratch/sandgoya/installations/oui111
INFO:

INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:

INFO: Saving comps.xml for /scratch/sandgoya/installations/oui111
INFO: Current Inventory:
Oracle Home: OUIHome1111
Java Runtime Environment 1.5.0.11.0
Installer SDK Component 11.2.0.4.0
Oracle One-Off Patch Installer 11.2.0.1.2
Oracle Universal Installer 11.2.0.4.0
Oracle Installation Libraries 11.2.0.4.0
Oracle Installation Products 11.2.0.4.0

INFO: OiicSaveInvWCCE:After saving the inventory. This is an Install session.
INFO: OiicSaveInvWCCE:After saving the inventory. The platform is unix.
INFO: OiicSaveInvWCCE:After saving the inventory. The location of root.sh is /scratch/sandgoya/installations/oui111/root.sh
INFO:

INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:

INFO: SaveInvWCCE JRE files in Scratch :1045
INFO: oracle.installer.mandatorySetup property is set to false, so skipping the execution of additional tools
INFO: oracle.installer.installUpdates property is set to false, so skipping the checking of updates
INFO: Config Initialize JRE files in Scratch :1045
INFO: no env vars set, no envVars.properties file is generated
INFO: none of the components are configurable
INFO: This is a shared oracle home or remote nodes are null. No copy required.
INFO: Checkpoint:Failed Checkpoint found returning it for getAllFailedCheckPoints.
INFO: Checkpoint:Failed Checkpoint found returning null for getLastFailedCheckPoint.
INFO: Checkpoint:Index file written and updated
INFO: Checkpoint:Transfer of file done from remote node
INFO: no. of sets of tools to be run: 0
INFO: ca page to be shown: false
INFO: exitonly tools to be excuted passed: 0
INFO:
*** End of Installation Page***
The installation of Oracle Installation Products was successful.
WARNING: Do you really want to exit?
INFO: User Selected: Yes/OK

Text files are also written in the temp directory:

<temp>\OraInstall\oraInstall<timestamp>.err
<temp>\OraInstall\oraInstall<timestamp>.out

If a problem occurs during the installation, you should look for messages with the SEVERE keyword and Java exceptions in these files.

A.5.2 Automated Inventory Backups

You can recover from a corrupt inventory or failed installations by using the following types of automated inventory backups:

Central Inventory Backup

The Central Inventory is automatically backed up whenever you execute the Oracle Universal Installer in any of the following modes:

- - install (new home)

- - deinstall (remove home)

- - addNode

- - attachHome

- - detachHome

- - updateNodeList

The backed up directory and file are:

<Central Inventory Location>/ContentsXML

The backup is located here:

<Central Inventory Location>/backup/time stamp/

Oracle Home Inventory Backup

The Oracle Home Inventory is automatically backed up on an existing Oracle home whenever you execute the Oracle Universal Installer in either of the following modes:

- - install (patchsets, upgrades, and one-offs)

- - deinstall components (does not remove the Oracle home)

The backed up directories and files are:

ORACLE_HOME/inventory/ContentsXML
ORACLE_HOME/inventory/Scripts
ORACLE_HOME/inventory/Clone
ORACLE_HOME/inventory/invDetails.properties

The backup is located here:

ORACLE_HOME/inventory//backup/time stamp/

B Understanding OUI Commands

The Oracle Universal Installer is run with various options and command-line arguments. This appendix lists the syntax of Oracle Universal Installer and the various command-line options available in Oracle Universal Installer. The following command shows the syntax for running the Oracle Universal Installer:

./launch or setup.exe <-options> [-command_line_variable=value]

In the preceding command, the following variables are used:

- <option>
The options available in Oracle Universal Installer. They are described in Table B-1.

- <command_line_variable>
The command-line variable for the option. They are described in Table B-2.

Note:
You can pass the command line variable in either of the following three ways:

1. <command_line_variable>={"value1","value2"}

2. "<command_line_variable>={value1,value2}"

3. <command_line_variable>="{value1,value2}"

B.1 Options Available in Oracle Universal Installer

Table B-1 lists the various options available in Oracle Universal Installer.

Table B-1 Options in Oracle Universal Installer

Option

Description

-attachHome

Attaches homes to the Oracle Universal Installer inventory. You must pass the ORACLE_HOME session variable when using this option.

-compatibilityFile <file>

Location of the file that specifies feature set dependency changes.

-debug

Used for getting the debug information from Oracle Universal Installer.

-deinstall

Uninstall the specified distribution.

-detachHome

Detaches homes from the Oracle Universal Installer inventory without deleting the inventory directory inside the Oracle home. You must pass the ORACLE_HOME session variable when using this option.

-distributionName <val>

Name of a distribution installed in this Oracle Home. Used with -deinstall.

-distributionVersion <val>

Version of a distribution installed in this Oracle Home. Used with -deinstall.

-executeSysPrereqs

Executes system prerequisite checks and exits. System prerequisites means OUI prerequisites (checked by the launcher), not product-specific prerequisites.

-help

Lists the syntax and help information.

-ignoreSysPrereqs

Ignore the results of the system prerequisite checks. System prerequisites means OUI prerequisites (checked by the launcher), not product-specific prerequisites.

-install

Perform an installation. This is the default operation.

-invPtrLoc <full path of oraInst.loc>

UNIX only. Use the specified inventory pointer file instead of the default. The inventory pointer file contains:

inventory_loc=<location of central inventory>
inst_group=<UNIX group name>

-logLevel <level>

Omit log messages whose priority level is less than <level>. Valid levels are: severe, warning, info, config, fine, finer, finest.

-noconsole

Do not allocate a console, and suppress the display of messages to the console. Windows only.

-nowait

Do not wait for the user to press Enter on the console after the operation (for example, install) is complete. Windows only.

-paramFile <location of file>

Specifies the location of the oraparam.ini file to be used by Oracle Universal Installer.

-prereqchecker

Performs a set of product-specific prerequisite checks, which depend on the product being installed as well as the platform.

-printdiskusage

Logs debug information about disk usage.

-printmemory

Logs debug information for memory usage.

-printtime

Logs debug information for time usage.

-regenerateLibraries

Allow libraries to be updated after an Oracle home has been modified.

-responseFile <Path>

Location of the response file containing input for OUI.

-silent

Used for silent mode operations. The input can be a response file or a list of command line variable value pairs. You can use the -responsefile option along with this option.

B.2 Command-Line Variables Available in Oracle Universal Installer

Table B-2 lists the command-line variables available in Oracle Universal Installer:

Table B-2 Command-Line Variables in Oracle Universal Installer

Command-Line Variable

Description

ACCEPT_LICENSE_AGREEMENT

Specifies the license agreement status. By setting this variable to true, you are accepting the license agreement.

ANONYMOUS_LOGIN

Specifies an anonymous login.

COMPONENT_LANGUAGES

Specifies the languages in which the components will be installed.

IGNORE_PREREQ

Specifies whether to skip the prerequisite checks or not. Set to true to continue component installation even when the prerequisite check fails.

INSTALL_TYPE

Specifies the installation type of the components.

INVENTORY_LOCATION

Specifies the inventory location.

LOGIN_CATEGORY

Specifies the login category.

LOGIN_NAME

Specifies the login name.

ORACLE_HOME

Specifies the ORACLE_HOME location.

ORACLE_HOME_FOLDER

Specifies the ORACLE HOME folder name. This is used only on Windows platform.

ORACLE_HOME_KEY

Specifies the ORACLE HOME key name. This is used only on Windows platform.

ORACLE_HOME_SERVICE

Specifies the ORACLE HOME service name. This is used only on Windows platform.

ORACLE_HOSTNAME

Specifies the host name of the system.

PASSWORD

Specifies the password.

REGISTRATION_KEYWORD

Specifies the registration keyword value. This can be obtained from the URL specified in the Product Registration Page.

SELECTED_LANGUAGES

Specifies the selected languages.

SELECTED_PLATFORMS

Specifies the selected platforms.

UNIX_GROUP_NAME

Specifies the group name on a UNIX platform.

C Sample Files

This appendix provides the following sample files:

- Sample Components File

- Sample oraparam.ini File

- Sample Components File

C.1 Sample Components File

Response files are of type .rsp and are used by Oracle Universal Installer to run silent installations.

####################################################################
## Copyright (c) 1999, 2012 Oracle. All rights reserved.          ##
##                                                                ##
## Specify values for the variables listed below to customize     ##
## your installation.                                             ##
##                                                                ##
## Each variable is associated with a comment. The comment        ##
## identifies the variable type.                                  ##
##                                                                ##
## Please specify the values in the following format:             ##
##                                                                ##
##         Type         Example                                   ##
##         String       "Sample Value"                            ##
##         Boolean      True or False                             ##
##         Number       1000                                      ##
##         StringList   {"String value 1","String Value 2"}       ##
##                                                                ##
## The values that are given as <Value Required> need to be       ##
## specified for a silent installation to be successful.          ##
##                                                                ##
##                                                                ##
## This response file is generated by Oracle Software             ##
## Packager.                                                      ##
####################################################################

RESPONSEFILE_VERSION=2.2.1.0.0

#-------------------------------------------------------------------------------
#Name       : UNIX_GROUP_NAME
#Datatype   : String
#Description: Unix group to be set for the inventory directory. Valid only in Unix platforms.
#Example: UNIX_GROUP_NAME = "install"
#-------------------------------------------------------------------------------
UNIX_GROUP_NAME=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : FROM_LOCATION
#Datatype   : String
#Description: Complete path to the products.xml.
#Example: FROM_LOCATION = "../stage/products.xml"
#-------------------------------------------------------------------------------
FROM_LOCATION="../stage/products.xml"

#-------------------------------------------------------------------------------
#Name       : FROM_LOCATION_CD_LABEL
#Datatype   : String
#Description: This variable should only be used in multi-CD installations. It includes the label of the compact disk where the file "products.xml" exists. The label can be found in the file "disk.label" in the same directory as products.xml.
#Example: FROM_LOCATION_CD_LABEL = "CD Label"
#-------------------------------------------------------------------------------
FROM_LOCATION_CD_LABEL="LABEL1"

#-------------------------------------------------------------------------------
#Name       : ORACLE_HOME
#Datatype   : String
#Description: Complete path of the Oracle Home.
#Example: ORACLE_HOME = "C:\OHOME1"
#-------------------------------------------------------------------------------
ORACLE_HOME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : ORACLE_BASE
#Datatype   : String
#Description: Complete path of the Oracle Base.
#Example: ORACLE_BASE =
#-------------------------------------------------------------------------------
ORACLE_BASE=<Value Required>

#-------------------------------------------------------------------------------
#Name       : ORACLE_HOME_NAME
#Datatype   : String
#Description: Oracle Home Name. Used in creating folders and services.
#Example: ORACLE_HOME_NAME = "OHOME1"
#-------------------------------------------------------------------------------
ORACLE_HOME_NAME="OHOME1"

#-------------------------------------------------------------------------------
#Name       : SHOW_WELCOME_PAGE
#Datatype   : Boolean
#Description: Set to true if the Welcome page in OUI needs to be shown.
#Example: SHOW_WELCOME_PAGE = false
#-------------------------------------------------------------------------------
SHOW_WELCOME_PAGE=false

#-------------------------------------------------------------------------------
#Name       : SUPPRESS_BUGLIST_WARNING
#Datatype   : Boolean
#Description: Set to true if the Welcome page in OUI needs to be shown.
#Example: SUPPRESS_BUGLIST_WARNING = false
#-------------------------------------------------------------------------------

SUPPRESS_BUGLIST_WARNING=false

#-------------------------------------------------------------------------------
#Name       : SHOW_NODE_SELECTION_PAGE
#Datatype   : Boolean
#Description: Set to true if the node selection page in OUI needs to be shown.
#Example: SHOW_NODE_SELECTION_PAGE = false
#-------------------------------------------------------------------------------
SHOW_NODE_SELECTION_PAGE=false

#-------------------------------------------------------------------------------
#Name       : SHOW_CUSTOM_TREE_PAGE
#Datatype   : Boolean
#Description: Set to true if the custom tree page in OUI needs to be shown.
#Use this page to select or de-select dependencies. This page appears only in a custom install type.
#Example: SHOW_CUSTOM_TREE_PAGE = false
#-------------------------------------------------------------------------------
SHOW_CUSTOM_TREE_PAGE=false

#-------------------------------------------------------------------------------
#Name       : SHOW_COMPONENT_LOCATIONS_PAGE
#Datatype   : Boolean
#Description: Set to true if the component locations page in OUI needs to be shown.
#This page only appears if there are products whose installed directory can be changed.
#If you set this to false you will prevent the user from being able to specify alternate directories.
#Example: SHOW_COMPONENT_LOCATIONS_PAGE = false
#-------------------------------------------------------------------------------
SHOW_COMPONENT_LOCATIONS_PAGE=false

#-------------------------------------------------------------------------------
#Name       : SHOW_SUMMARY_PAGE
#Datatype   : Boolean
#Description: Set to true if the summary page in OUI needs to be shown.
#The summary page shows the list of components that will be installed in this session.
#Example: SHOW_SUMMARY_PAGE = true
#-------------------------------------------------------------------------------
SHOW_SUMMARY_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_INSTALL_PROGRESS_PAGE
#Datatype   : Boolean
#Description: Set to true if the install progress page in OUI needs to be shown.
#This page shows the current status in the installation. The current status includes the product being installed and the file being copied.
#Example: SHOW_INSTALL_PROGRESS_PAGE = true
#-------------------------------------------------------------------------------
SHOW_INSTALL_PROGRESS_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_REQUIRED_CONFIG_TOOL_PAGE
#Datatype   : Boolean
#Description: Set to true if the required config assistants page in OUI needs to be shown.
#This page shows the list of required configuration assistants that are part of this installation.
#It shows the status of each assistant, including any failures with detailed information on why it failed.
#Example: SHOW_REQUIRED_CONFIG_TOOL_PAGE = true
#-------------------------------------------------------------------------------
SHOW_REQUIRED_CONFIG_TOOL_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_CONFIG_TOOL_PAGE
#Datatype   : Boolean
#Description: Set to true if the config assistants page in OUI needs to be shown.
#This page shows the list of configuration assistants that are part of this installation and are configured to launch automatically.
#It shows the status of each assistant, including any failures with detailed information on why it failed.
#Example: SHOW_CONFIG_TOOL_PAGE = true
#-------------------------------------------------------------------------------

SHOW_CONFIG_TOOL_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_RELEASE_NOTES
#Datatype   : Boolean
#Description: Set to true if the release notes of this installation need to be shown at the end of installation.
#This dialog is launchable from the End of Installation page and shows the list of release notes available for the products just installed.
# This also requires the variable SHOW_END_SESSION_PAGE variable to be set to true.
#Example: SHOW_RELEASE_NOTES = true
#-------------------------------------------------------------------------------
SHOW_RELEASE_NOTES=true

#-------------------------------------------------------------------------------
#Name       : SHOW_ROOTSH_CONFIRMATION
#Datatype   : Boolean
#Description: Set to true if the Confirmation dialog asking to run the root.sh script in OUI needs to be shown.
#Valid only for Unix platforms.
#Example: SHOW_ROOTSH_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_ROOTSH_CONFIRMATION=true

#-------------------------------------------------------------------------------
#Name       : SHOW_END_SESSION_PAGE
#Datatype   : Boolean
#Description: Set to true if the end of session page in OUI needs to be shown.
#This page shows if the installation is successful or not.
#Example: SHOW_END_SESSION_PAGE = true
#-------------------------------------------------------------------------------
SHOW_END_SESSION_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_EXIT_CONFIRMATION
#Datatype   : Boolean
#Description: Set to true if the confirmation when exiting OUI needs to be shown.
#Example: SHOW_EXIT_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_EXIT_CONFIRMATION=true

#-------------------------------------------------------------------------------
#Name       : NEXT_SESSION
#Datatype   : Boolean
#Description: Set to true to allow users to go back to the File Locations page for another installation. This option also needs to be set to true in order to process another response file (see NEXT_SESSION_RESPONSE).
#Example: NEXT_SESSION = true
#-------------------------------------------------------------------------------
NEXT_SESSION=true

#-------------------------------------------------------------------------------
#Name       : NEXT_SESSION_ON_FAIL
#Datatype   : Boolean
#Description: Set to true to allow users to invoke another session even if current install session has failed. This option is only relevant if NEXT_SESSION is set to true.
#Example: NEXT_SESSION_ON_FAIL = true
#-------------------------------------------------------------------------------
NEXT_SESSION_ON_FAIL=true

#-------------------------------------------------------------------------------
#Name       : NEXT_SESSION_RESPONSE
#Datatype   : String
#Description: Set to true to allow users to go back to the File Locations page for another installation. This option also needs to be set to true in order to process another response file (see NEXT_SESSION_RESPONSE).
#Example: NEXT_SESSION_RESPONSE = "nextinstall.rsp"
#-------------------------------------------------------------------------------
NEXT_SESSION_RESPONSE=<Value Unspecified>

#-------------------------------------------------------------------------------

#Name       : DEINSTALL_LIST
#Datatype   : StringList
#Description: List of components to be deinstalled during a deinstall session.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
#    oracle.swd, 12.1.0.1.0 : Oracle Installation Products 12.1.0.1.0
#Example: DEINSTALL_LIST = {"oracle.swd","12.1.0.1.0"}
#-------------------------------------------------------------------------------
DEINSTALL_LIST={"oracle.swd","12.1.0.1.0"}

#-------------------------------------------------------------------------------
#Name       : SHOW_DEINSTALL_CONFIRMATION
#Datatype   : Boolean
#Description: Set to true if deinstall confimation is needed during a deinstall session.
#Example: SHOW_DEINSTALL_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_DEINSTALL_CONFIRMATION=true

#-------------------------------------------------------------------------------
#Name       : SHOW_DEINSTALL_PROGRESS
#Datatype   : Boolean
#Description: Set to true if deinstall progress is needed during a deinstall session.
#Example: SHOW_DEINSTALL_PROGRESS = true
#-------------------------------------------------------------------------------
SHOW_DEINSTALL_PROGRESS=true

#-------------------------------------------------------------------------------
#Name       : CLUSTER_NODES
#Datatype   : StringList
#Description: This variable represents the cluster node names selected by the user for installation.
#Example: CLUSTER_NODES = {"node1"}
#-------------------------------------------------------------------------------
CLUSTER_NODES=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : REMOTE_NODES
#Datatype   : StringList
#Description: This variable represents the remote node names on which installation is carried out.
#Example: REMOTE_NODES =
#-------------------------------------------------------------------------------
REMOTE_NODES=<Value Required>

#-------------------------------------------------------------------------------
#Name       : NODES_TO_SET
#Datatype   : StringList
#Description: S_NODES_TO_SET
#Example: NODES_TO_SET =
#-------------------------------------------------------------------------------
NODES_TO_SET=<Value Required>

#-------------------------------------------------------------------------------
#Name       : LOCAL_NODE
#Datatype   : String
#Description: This variable represents the local node.
#Example: LOCAL_NODE =
#-------------------------------------------------------------------------------
LOCAL_NODE=<Value Required>

#-------------------------------------------------------------------------------
#Name       : RESTART_SYSTEM
#Datatype   : Boolean
#Description: Set to true to allow automatic restart of the system, if set to false then installer will exit without restarting, no exit confirmation dialog is shown
#Example: RESTART_SYSTEM = false
#-------------------------------------------------------------------------------
RESTART_SYSTEM=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : RESTART_REMOTE_SYSTEM
#Datatype   : Boolean
#Description: Set to true to allow automatic restart of the remote systems, if set to false then installer will not restart the remote systems, no exit confirmation dialog is shown
#Example: RESTART_REMOTE_SYSTEM = false
#-------------------------------------------------------------------------------
RESTART_REMOTE_SYSTEM=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : ORACLE_HOSTNAME
#Datatype   : String
#Description: This variable holds the hostname of the system as set by the user.
#Example: ORACLE_HOSTNAME =
#-------------------------------------------------------------------------------
ORACLE_HOSTNAME=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : REMOVE_HOMES
#Datatype   : StringList
#Description: List of the homes to be removed during a deinstall session. Each home is represented by its full path.
#Example: REMOVE_HOMES = {<full_path_of_home1>,<full_path_of_home2>, ...}
#-------------------------------------------------------------------------------
REMOVE_HOMES=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : SHOW_XML_PREREQ_PAGE
#Datatype   : Boolean
#Description: This variable determines whether or not to show the prereq page.
#Example: SHOW_XML_PREREQ_PAGE = true
#-------------------------------------------------------------------------------

SHOW_XML_PREREQ_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_END_OF_INSTALL_MSGS
#Datatype   : Boolean
#Description: Set to true if the text on end of install screen is to be shown. The text is always available under <Oracle Home>/install/readme.txt.
#Example: SHOW_END_OF_INSTALL_MSGS = true
#-------------------------------------------------------------------------------
SHOW_END_OF_INSTALL_MSGS=true

#-------------------------------------------------------------------------------
#Name       : ACCEPT_LICENSE_AGREEMENT
#Datatype   : Boolean
#Description: By setting this variable to true, you are accepting the license agreement. This variable is used only for silent installations.
#Example: ACCEPT_LICENSE_AGREEMENT = true
#-------------------------------------------------------------------------------
ACCEPT_LICENSE_AGREEMENT=true

#-------------------------------------------------------------------------------
#Name       : METALINK_LOCATION
#Datatype   : String
#Description: This variable represents the Oracle metalink location.
#Example: METALINK_LOCATION =
#-------------------------------------------------------------------------------
METALINK_LOCATION=<Value Required>

#-------------------------------------------------------------------------------
#Name       : METALINK_USERNAME
#Datatype   : String
#Description: This variable represents the Oracle metalink user name.
#Example: METALINK_USERNAME =
#-------------------------------------------------------------------------------
METALINK_USERNAME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : MYORACLESUPPORT_USERNAME
#Datatype   : String
#Description: This variable represents the Oracle metalink user name.
#Example: MYORACLESUPPORT_USERNAME =
#-------------------------------------------------------------------------------
MYORACLESUPPORT_USERNAME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : METALINK_PASSWORD
#Datatype   : String
#Description: This variable represents the corresponding Oracle metalink password.
#Example: METALINK_PASSWORD =
#-------------------------------------------------------------------------------
METALINK_PASSWORD=<Value Required>

#-------------------------------------------------------------------------------
#Name       : MYORACLESUPPORT_PASSWORD
#Datatype   : String
#Description: This variable represents the corresponding Oracle metalink password.
#Example: MYORACLESUPPORT_PASSWORD =
#-------------------------------------------------------------------------------
MYORACLESUPPORT_PASSWORD=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_HOST
#Datatype   : String
#Description: The proxy host  used to connect to Oracle metalink.
#Example: PROXY_HOST =
#-------------------------------------------------------------------------------
PROXY_HOST=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_PORT
#Datatype   : String
#Description: The proxy port used to connect to Oracle metalink.
#Example: PROXY_PORT =
#-------------------------------------------------------------------------------
PROXY_PORT=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_REALM
#Datatype   : String
#Description: The realm for the proxy used to connect to Oracle metalink.
#Example: PROXY_REALM =
#-------------------------------------------------------------------------------

PROXY_REALM=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_USER
#Datatype   : String
#Description: The username for the proxy  used to connect to Oracle metalink.
#Example: PROXY_USER =
#-------------------------------------------------------------------------------
PROXY_USER=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_PWD
#Datatype   : String
#Description: The password for the proxy  used to connect to Oracle metalink.
#Example: PROXY_PWD =
#-------------------------------------------------------------------------------
PROXY_PWD=<Value Required>

#-------------------------------------------------------------------------------
#Name       : DONT_PROXY_FOR
#Datatype   : String
#Description: The dont proxy for list.
#Example: DONT_PROXY_FOR =
#-------------------------------------------------------------------------------
DONT_PROXY_FOR=<Value Required>

#-------------------------------------------------------------------------------
#Name       : DECLINE_SECURITY_UPDATES
#Datatype   : Boolean
#Description: OUI Session variable set to decline from receiving the security updates
#Example: DECLINE_SECURITY_UPDATES =
#-------------------------------------------------------------------------------
DECLINE_SECURITY_UPDATES=<Value Required>

#-------------------------------------------------------------------------------
#Name       : COLLECTOR_RESPONSE_FILE
#Datatype   : String
#Description: OUI Session variable used to provide the OCM response file location
#Example: COLLECTOR_RESPONSE_FILE =
#-------------------------------------------------------------------------------
COLLECTOR_RESPONSE_FILE=<Value Required>

#-------------------------------------------------------------------------------
#Name       : SECURITY_UPDATES_VIA_METALINK
#Datatype   : Boolean
#Description: OUI Session variable used to set if the security updates should be received via Metalink details
#Example: SECURITY_UPDATES_VIA_METALINK =
#-------------------------------------------------------------------------------
SECURITY_UPDATES_VIA_METALINK=<Value Required>

#-------------------------------------------------------------------------------
#Name       : SECURITY_UPDATES_VIA_MYORACLESUPPORT
#Datatype   : Boolean
#Description: OUI Session variable used to set if the security updates should be received via Metalink details
#Example: SECURITY_UPDATES_VIA_MYORACLESUPPORT =
#-------------------------------------------------------------------------------
SECURITY_UPDATES_VIA_MYORACLESUPPORT=<Value Required>

#-------------------------------------------------------------------------------
#Name       : COLLECTOR_SUPPORTHUB_URL
#Datatype   : String
#Description: S_COLLECTOR_SUPPORTHUB_URL_DESC
#Example: COLLECTOR_SUPPORTHUB_URL =
#-------------------------------------------------------------------------------
COLLECTOR_SUPPORTHUB_URL=<Value Required>

#-------------------------------------------------------------------------------
#Name       : HOME_DEPENDENCY_LIST
#Datatype   : StringList
#Description: Set the cross home dependency relation
#Example: HOME_DEPENDENCY_LIST =
#-------------------------------------------------------------------------------

HOME_DEPENDENCY_LIST=<Value Required>

#-------------------------------------------------------------------------------
#Name       : COMPOSITE_HOME
#Datatype   : String
#Description: Complete path of the Composite Home.
#Example: COMPOSITE_HOME =
#-------------------------------------------------------------------------------
COMPOSITE_HOME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : COMPOSITE_HOME_TYPE
#Datatype   : String
#Description: Composite Home Type. Product type installed.
#Example: COMPOSITE_HOME_TYPE =
#-------------------------------------------------------------------------------
COMPOSITE_HOME_TYPE=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : SUITE_NAME
#Datatype   : String
#Description: S_SUITE_NAME_DESC
#Example: SUITE_NAME =
#-------------------------------------------------------------------------------
SUITE_NAME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : UMASK
#Datatype   : String
#Description: S_UMASK
#Example: UMASK = "install"
#-------------------------------------------------------------------------------
UMASK=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : COMPOSITE_HOME
#Datatype   : String
#Description: Composite Home
#Example: COMPOSITE_HOME = "install"
#-------------------------------------------------------------------------------
COMPOSITE_HOME=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : DEPENDEE_HOME
#Datatype   : String
#Description: S_DEPENDEE_HOME
#Example: DEPENDEE_HOME = "install"
#-------------------------------------------------------------------------------
DEPENDEE_HOME=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : UNZIP_LOCATION
#Datatype   : String
#Description: S_UNZIP_LOCATION
#Example: UNZIP_LOCATION = "install"
#-------------------------------------------------------------------------------
UNZIP_LOCATION=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : TOPLEVEL_COMPONENT
#Datatype   : StringList
#Description: The top level component to be installed in the current session.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
#    oracle.swd, 12.1.0.1.0 : Oracle Installation Products 12.1.0.1.0
#Example: TOPLEVEL_COMPONENT = {"oracle.swd","12.1.0.1.0"}
#-------------------------------------------------------------------------------
TOPLEVEL_COMPONENT={"oracle.swd","12.1.0.1.0"}

#-------------------------------------------------------------------------------
#Name       : SHOW_SPLASH_SCREEN
#Datatype   : Boolean
#Description: Set to true if the initial splash screen in OUI needs to be shown.
#Example: SHOW_SPLASH_SCREEN =
#-------------------------------------------------------------------------------

SHOW_SPLASH_SCREEN=true

#-------------------------------------------------------------------------------
#Name       : SELECTED_LANGUAGES
#Datatype   : StringList
#Description: Languages in which the components will be installed.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
#    en,   : English
#    fr,   : French
#    ar,   : Arabic
#    bn,   : Bengali
#    pt_BR,   : Brazilian Portuguese
#    bg,   : Bulgarian
#    fr_CA,   : Canadian French
#    ca,   : Catalan
#    hr,   : Croatian
#    cs,   : Czech
#    da,   : Danish
#    nl,   : Dutch
#    ar_EG,   : Egyptian
#    en_GB,   : English (United Kingdom)
#    et,   : Estonian
#    fi,   : Finnish
#    de,   : German
#    el,   : Greek
#    iw,   : Hebrew
#    hu,   : Hungarian
#    is,   : Icelandic
#    in,   : Indonesian
#    it,   : Italian
#    ja,   : Japanese
#    ko,   : Korean
#    es,   : Latin American Spanish
#    lv,   : Latvian
#    lt,   : Lithuanian
#    ms,   : Malay
#    es_MX,   : Mexican Spanish
#    no,   : Norwegian
#    pl,   : Polish
#    pt,   : Portuguese
#    ro,   : Romanian
#    ru,   : Russian
#    zh_CN,   : Simplified Chinese
#    sk,   : Slovak
#    sl,   : Slovenian
#    es_ES,   : Spanish
#    sv,   : Swedish
#    th,   : Thai
#    zh_TW,   : Traditional Chinese
#    tr,   : Turkish
#    uk,   : Ukrainian
#    vi,   : Vietnamese
#Example: SELECTED_LANGUAGES = {"en"}
#-------------------------------------------------------------------------------
#SELECTED_LANGUAGES={"en"}

#-------------------------------------------------------------------------------

#Name       : COMPONENT_LANGUAGES
#Datatype   : StringList
#Description: Languages in which the components will be installed.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
#    en,   : English
#    fr,   : French
#    ar,   : Arabic
#    bn,   : Bengali
#    pt_BR,   : Brazilian Portuguese
#    bg,   : Bulgarian
#    fr_CA,   : Canadian French
#    ca,   : Catalan
#    hr,   : Croatian
#    cs,   : Czech
#    da,   : Danish
#    nl,   : Dutch
#    ar_EG,   : Egyptian
#    en_GB,   : English (United Kingdom)
#    et,   : Estonian
#    fi,   : Finnish
#    de,   : German
#    el,   : Greek
#    iw,   : Hebrew
#    hu,   : Hungarian
#    is,   : Icelandic
#    in,   : Indonesian
#    it,   : Italian
#    ja,   : Japanese
#    ko,   : Korean
#    es,   : Latin American Spanish
#    lv,   : Latvian
#    lt,   : Lithuanian
#    ms,   : Malay
#    es_MX,   : Mexican Spanish
#    no,   : Norwegian
#    pl,   : Polish
#    pt,   : Portuguese
#    ro,   : Romanian
#    ru,   : Russian
#    zh_CN,   : Simplified Chinese
#    sk,   : Slovak
#    sl,   : Slovenian
#    es_ES,   : Spanish
#    sv,   : Swedish
#    th,   : Thai
#    zh_TW,   : Traditional Chinese
#    tr,   : Turkish
#    uk,   : Ukrainian
#    vi,   : Vietnamese
#Example: COMPONENT_LANGUAGES = {"en"}
#Component  : oracle.swd
#-------------------------------------------------------------------------------

COMPONENT_LANGUAGES={"en"}

#-------------------------------------------------------------------------------
#Name       : INSTALL_TYPE
#Datatype   : String
#Description: Installation type of the component.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
#    Complete,   : Complete
#    Typical,   : Minimum
#    Custom,   : Custom
#Example: INSTALL_TYPE = "Complete"
#Component  : oracle.swd
#-------------------------------------------------------------------------------

INSTALL_TYPE="Complete"

C.2 Sample oraparam.ini File

The oraparam.ini file is Oracle Universal Installer's initialization file. It should be located in the same directory as the Oracle Universal Installer executable file (setup.exe or runInstaller.sh).

[Oracle]
DISTRIBUTION=TRUE
SOURCE=../../stage/products.xml
BOOTSTRAP_COMPS="oracle.swd.oui,oracle.swd.oui.core"
JRE_MEMORY_OPTIONS=" -Xverify:none"
DEFAULT_HOME_LOCATION=as
DEFAULT_HOME_NAME=as_home
NO_BROWSE=/net
NLS_ENABLED=TRUE
BOOTSTRAP=TRUE
PREREQ_CONFIG_LOCATION=../../stage/prereq
OUI_VERSION=11.1.0.7.0
SHOW_HOSTNAME=NEVER_SHOW
THIN_JDBC_FILENAME=classes12.jar
#PLATFORM_PREREQS=TRUE

INSTALL_CLASS=oracle.sysman.oio.oioc.OiocOneClickInstaller
EXT_JLIB=../../stage/ext/jlib

UMASK=027

[Generic Prereqs]
CPU=300
TEMP_SPACE=150
SWAP_SPACE=512
MIN_DISPLAY_COLORS=256

[IMAGES]

[Updates]
UPDATE_BUGID=9636109
UPDATE_VERSION=10.1.0.3

C.3 Sample Components File

The components file contains details of all the components as well as patchsets or interim patches installed in the Oracle home.

<?xml version="1.0" standalone="yes" ?>
<!-- Copyright (c) 1999, 2009, Oracle. All rights reserved. -->
<!-- Do not modify the contents of this file by hand. -->
<PRD_LIST>
<TL_LIST>
<COMP NAME="oracle.server" VER="11.2.0.1.0" BUILD_NUMBER="0" REP_VER="0.0.0.0.0" RELEASE="Production" INV_LOC="Components/oracle.server/11.2.0.1.0/1/" LANGS="en" XML_INV_LOC="Components21/oracle.server/11.2.0.1.0/" ACT_INST_VER="11.2.0.1.0" DEINST_VER="11.2.0.0.0" INSTALL_TIME="2009.Jul.21 11:00:34 PDT" INST_LOC="/scratch/rv/dbbase/dbhome_1/oracle.server">
<EXT_NAME>Oracle Database 11g</EXT_NAME>
<DESC>Installs an optional preconfigured starter database, product options, management tools, networking services, utilities, and basic client software for an Oracle Database server. This option also supports Automatic Storage Management database configuration.</DESC>
<DESCID>COMPONENT_DESC</DESCID>
<STG_INFO OSP_VER="10.2.0.0.0"/>
<CMP_JAR_INFO>
<INFO NAME="filemapObj" VAL="Components/oracle/server/v11_2_0_1_0/filemap.xml"/>
<INFO NAME="helpDir" VAL="Components/oracle/server/v11_2_0_1_0/help/"/>
<INFO NAME="actionsClass" VAL="Components.oracle.server.v11_2_0_1_0.CompActions"/>
<INFO NAME="resourceClass" VAL="Components.oracle.server.v11_2_0_1_0.resources.CompRes"/>
<INFO NAME="identifiersXML" VAL="Components/oracle/server/v11_2_0_1_0/identifiers.xml"/>
<INFO NAME="contextClass" VAL="Components.oracle.server.v11_2_0_1_0.CompContext"/>
<INFO NAME="fastCopyLogXML" VAL="Components/oracle/server/v11_2_0_1_0/fastCopyLog.xml"/>
</CMP_JAR_INFO>
<LOC_INFO INST_DFN_LOC="../Scripts" JAR_NAME="install2.jar"/>
<BOOK NAME="oracle.server.hs"/>
<PRE_REQ DEF="F"/>
<PROD_HOME DEF="F"/>
<DEP_GRP_LIST>
<DEP_GRP NAME="Optional" EXT_NAME="Optional" TYPE="O">
<DEP_LIST>
<DEP NAME="oracle.rdbms" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.options" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.network" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.rdbms.oci" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.precomp" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.xdk" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.winprod" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.odbc" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.sysman.ccr" VER="10.2.4.0.0" PLAT="Linux"/>
</DEP_LIST>
</DEP_GRP>
<DEP_GRP NAME="Required" EXT_NAME="Required" TYPE="R">
<DEP_LIST>
<DEP NAME="oracle.rdbms.install.common" VER="11.2.0.1.0" PLAT="Linux"/>
<DEP NAME="oracle.install.deinstalltool" VER="11.2.0.1.0" PLAT="Linux"/>
</DEP_LIST>
</DEP_GRP>
<DEP_GRP NAME="OptionalDecideNow" EXT_NAME="OptionalDecideNow" TYPE="O">
<DEP_LIST>
<DEP NAME="oracle.swd.oui" VER="10.1.0.2.0" PLAT="Linux"/>
<DEP NAME="oracle.swd.opatch" VER="10.1.0.2.0" PLAT="Linux"/>
<DEP NAME="oracle.dbjava.jdbc" VER="11.2.0.1.0" PLAT="Linux"/>
</DEP_LIST>
</DEP_GRP>
</DEP_GRP_LIST>
<DEP_LIST>
<DEP NAME="oracle.rdbms" VER="11.2.0.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.options" VER="11.2.0.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.network" VER="11.2.0.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.rdbms.oci" VER="11.2.0.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.precomp" VER="11.2.0.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.xdk" VER="11.2.0.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.odbc" VER="11.2.0.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.sysman.ccr" VER="10.3.1.1.0" DEP_GRP_NAME="Optional" HOME_IDX="2"/>
<DEP NAME="oracle.rdbms.install.common" VER="11.2.0.1.0" DEP_GRP_NAME="Required" HOME_IDX="2"/>
<DEP NAME="oracle.install.deinstalltool" VER="11.2.0.1.0" DEP_GRP_NAME="Required" HOME_IDX="2"/>
<DEP NAME="oracle.swd.oui" VER="11.2.0.1.0" DEP_GRP_NAME="OptionalDecideNow" HOME_IDX="2"/>
<DEP NAME="oracle.swd.opatch" VER="11.2.0.0.2" DEP_GRP_NAME="OptionalDecideNow" HOME_IDX="2"/>
<DEP NAME="oracle.dbjava.jdbc" VER="11.2.0.1.0" DEP_GRP_NAME="OptionalDecideNow" HOME_IDX="2"/>
</DEP_LIST>
<REF_LIST>
<REF NAME="oracle.server" VER="11.2.0.1.0" HOME_IDX="2"/>
</REF_LIST>
<INST_TYPE_LIST>
<INST_TYPE NAME="EE" NAME_ID="EE" DESC_ID=""/>
</INST_TYPE_LIST>
<FILESIZEINFO>
<DEST VOLUME="%ORACLE_HOME%" SPACE_REQ="81045"/>
<DEST VOLUME="%INVENTORY_LOCATION%" SPACE_REQ="2000"/>
<DEST VOLUME="%s_TMPDIR_LOC%" SPACE_REQ="0"/>
<DEST VOLUME="%s_TEMP_LOC%" SPACE_REQ="0"/>
</FILESIZEINFO>
</COMP>
</TL_LIST>
<ONEOFF_LIST>
</ONEOFF_LIST>
<PATCHSET_UPDATE_LIST>
</PATCHSET_UPDATE_LIST>
</PRD_LIST>

D Error Messages and Solutions

This appendix provides potential cause and possible solution information for all OUI errors. The information is arranged in numerical order according to the OUI error message numbers.

D.1 OUI - 10001

Message

OUI cannot determine the platform of this system. This may occur if OUI is running on a system that is not supported or there is a bug in OUI. Please confirm that the system is a supported configuration; if it is supported, please contact Oracle Support.

Potential Causes

OUI determines the platform from the file
<ORACLE_HOME>/inventory/ContentsXML/oraclehomeproperties.xml

This message can occur from one of the following causes:

- OUI cannot detect the platform from the
<ORACLE_HOME>/inventory/ContentsXML/oraclehomeproperties.xml file.

- OUI is running on an unsupported system.

- There is an OUI bug.

Possible Solutions

- Check the Certifications tab in My Oracle Support to confirm that the system is a supported configuration:

https://support.oracle.com

- Contact Oracle Support.

D.2 OUI - 10004

Message

The target area <location_of_oraInventory> is being written to by another session. Please close all the other(write) sessions for accessing inventory.

Potential Causes

For any write operations in the inventory, OUI acquires a lock. The writer.lock file is created under the <oraInventory>/locks directory. The error message appears if a lock exists in <oraInventory>/locks that another OUI has already acquired.

Possible Solutions

- Check if a writer.lock file already exists in the <oraInventory>/locks directory.

- Check if another OUI is running in the system that can hold a lock on the oraInventory.
For UNIX, you can use this command:

% ps -ef | grep runInstaller

For Windows, you can use one of these commands:

> tasklist | findstr /R "setup.exe"

> tasklist | findstr /R "oui.exe"

> tasklist | findstr /R "javaw.exe"
(Make sure that this is the Java process related to OUI.)

- Stop the process, then try to start OUI again.

D.3 OUI - 10005

Message

You do not have sufficient permissions to access the inventory
<location_of_oraInventory>, unable to remove an existing inactive writer lock file in the inventory. Make sure you have enough permission to the ''locks'' directory to create/remove the writer.lock file.

Potential Causes

For any write operations in the inventory, OUI acquires a lock. The writer.lock file is created under the <oraInventory>/locks directory. The global inventory (oraInventory) was locked by another process and the writer.lock file still exists even after the process exited. The current OUI (process) is not able to remove the writer.lock file, because the permission for the current user does not allow this. Possibly, the current user is neither the owner nor the member of the group that owns the <oraInventory>/locks directory.

Possible Solutions

- Make sure you have write permission on the <oraInventory>/locks directory.

- Either change the ownership of <oraInventory>/ to the current user, or include the current user in the group that owns the <oraInventory> directory, provided that the group has write permission to the <oraInventory> directory.

D.4 OUI - 10020

Message

The target area <location_of_oraInventory> is being used as a source by another session. A write lock cannot be obtained.

Potential Causes

For any write operations in the inventory, OUI acquires a lock. The writer.lock file is created under the <oraInventory>/locks directory. This error message appears if the <oraInventory> directory is accessed by another process (may be third party tools also) so that OUI cannot create a writer.lock file in the <oraInventory>/locks directory.

Possible Solutions

Check if any process is accessing <oraInventory>. If so, kill/stop the process. For UNIX, you can use this command:

/sbin/fuser <path_to_oraInventory>

D.5 OUI - 10021

Message

The target area <location_of_oraInventory> is being written to by another session. A read lock cannot be obtained.

Potential Causes

Another process has locked the global inventory (oraInventory). For any reading operation or when OUI is started, OUI creates a reader.lock file in the <oraInventory>/locks directory. Since a writer.lock file already exists in the <oraInventory>/locks directory, OUI cannot create a reader.lock file.

Possible Solutions

- Check if a writer.lock file already exists in the <oraInventory>/locks directory.

- Check if another OUI is running in the system that can hold a lock on the oraInventory.
For UNIX, you can use this command:

% ps -ef | grep runInstaller

For Windows, you can use one of these commands:

> tasklist | findstr /R "setup.exe"

> tasklist | findstr /R "oui.exe"

> tasklist | findstr /R "javaw.exe"
(Make sure that this is the Java process related to OUI.)

- Stop the process, then try to start OUI again.

D.6 OUI - 10022

Message

The target area {0} cannot be used because it is in an invalid state.

Potential Causes

This error can occur for many reasons. The cause is usually global inventory (oraInventory) corruption.

Possible Solutions

- Make sure you have write permission on the <oraInventory> directory.

- Check the health of the inventory using this OPatch command:

% OPatch lsinventory

Verify that the command is able to list the details.

If the central inventory is corrupted, you can recreate it. For information about this, see Note 556834.1 - "Steps To Recreate Central Inventory (oraInventory) In RDBMS Homes" accessible through your My Oracle Support account.

D.7 OUI - 10024

Message

The DISPLAY environment variable is not set. The DISPLAY environment variable should be set to <hostname or IP address>:<screen>, where the <screen> is usually :0.0.

Potential Causes

The DISPLAY environment variable is not set, which OUI requires.

Possible Solutions

1. Check if the DISPLAY environment variable is set. Use the following command to view the current DISPLAY environment variable setting:

echo $DISPLAY

2. If the DISPLAY environment variable is not set, use the following command to see what shell is being used:

% echo $SHELL

3. Use one of the following commands for your UNIX shell as an example to set the variable:
For the csh shell:

% setenv DISPLAY 192.168.1.128:0.0

For sh, ksh, and bash shells:

$ DISPLAY=192.168.1.128:0.0
$ export DISPLAY

D.8 OUI - 10025

Message

Unable to start an interactive install session because of the following error:{0} The DISPLAY environment variable should be set to <hostname or IP address>:<screen>, where the <screen> is usually ''0.0".

Potential Causes

The DISPLAY environment variable is not set properly, or client users are not authorized to connect to the X Server.

Possible Solutions

1. Check if the DISPLAY environment variable is set. Use the following command to view the current DISPLAY environment variable setting:

echo $DISPLAY

2. If the DISPLAY environment variable is not set, use the following command to see what shell is being used:

% echo $SHELL

3. Use one of the following commands for your Unix shell as an example to set the variable:
For the csh shell:

% setenv DISPLAY 192.168.1.128:0.0

For sh, ksh, and bash shells:

$ DISPLAY=192.168.1.128:0.0
$ export DISPLAY

4. Make sure that client users are authorized to connect to the X Server. To enable client users to access the X Server, open an xterm, dtterm, or xconsole as the user that started the session and type the following command:

% xhost +

5. To test that the DISPLAY environment variable is set correctly, run an X11 based program that comes with the native operating system, such as xclock.
If you are unable to successfully run xclock, refer to your PC-X Server or OS vendor for further assistance.

D.9 OUI - 10028

Message

The directory location you have specified ( <location> ) is not registered as an Oracle Home in the central inventory. Do you want to continue installation in this Oracle Home?

Potential Causes

OUI is not able to retrieve the Oracle Home details from the Central inventory (oraInventory).

Possible Solutions

- Check whether the Oracle home is present in the central inventory. Use the following command to determine this:

% OPatch lsinventory -all

- If the Oracle home is not present in the central inventory, use one of the following applicable commands to register the Oracle home with the central inventory:
For Unix, use these commands:

% cd $ORACLE_HOME/oui/bin     % ./launch -attachHome ORACLE_HOME="<Oracle_Home Path>"

For Windows, use these commands:

> cd %ORACLE_HOME%/oui/bin     > setup.exe -attachHome ORACLE_HOME="<Oracle_Home Path>"

D.10 OUI - 10029

Message

You have specified a non-empty directory to install this product. It is recommended to specify either an empty or a non-existent directory. You may, however, choose to ignore this message if the directory contains Operating System generated files or subdirectories like 'lost+found'.

Potential Causes

The Oracle Home path (directory) specified for the installation already exists, and the directory contains files or subdirectories.

Possible Solutions

Select one of the following choices:

- Check if any directory/files exist inside the Oracle Home directory specified. Remove the directories/files if they are not required, then continue the installation. You can ignore directories like "lost+found".

- Specify another non-existent directory as the Oracle home. OUI creates it during installation.

- Specify a directory that is empty.

Note:
Use the -force option to continue past this error for a silent installation.

D.11 OUI - 10030

Message

You have specified a non-empty directory to install this product. It is recommended to specify either an empty or a non-existent directory. You may, however, choose to ignore this message if the directory contains Operating System generated files or subdirectories like 'lost+found'. Do you want to proceed with installation in this Oracle Home?

Potential Causes

The Oracle home path (directory) specified for the installation already exists, and the directory contains files or subdirectories.

Possible Solutions

Select one of the following choices:

- Check if any directory/files exist inside the Oracle home directory specified. Remove the directories/files if they are not required, then continue the installation. You can ignore directories like "lost+found".

- Specify another non-existent directory as the Oracle home. OUI creates it during installation.

- Specify a directory that is empty.

Note:
Use the -force option to continue past this error for a silent installation.

D.12 OUI - 10031

Message

Inventory location cannot be empty.

Potential Causes

This message appears only if you used the -invPtrLoc argument, as in the runInstaller -invPtlLoc command.

Possible Solutions

Specify the location for the Central Inventory and continue with the installation.

D.13 OUI - 10033

Message

The inventory location <location> set by the previous installation session is no longer accessible. Do you still want to continue by creating a new inventory? Note that you may lose the products installed in the earlier session.

Potential Causes

There can be multiple causes for this error. Generally, most of the problems will be related to:

- Incorrect inventory location specified in the oraInst.loc file.

- Improper permissions on the inventory location specified in the oraInst.loc file.

Possible Solutions

Make sure that the inventory location specified in the oraInst.loc file is correct and also you have proper permissions on the specified location.

D.14 OUI - 10034

Message

Inventory location is invalid.

Potential Causes and Possible Solutions

There are several reasons this message can appear:

- The inventory location is truly invalid:

- The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc file or /etc/oraInst.loc file or inst_loc in the registry is a non-existent location or has extra characters in the directory path listed.
Fix — Search for the oraInventory directory on the system and change the location in oraInst.loc or inst_loc to point to the correct location, or if the path listed is incorrect, correct it.

- The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc file or /etc/oraInst.loc file or inst_loc in the registry is not the directory oraInventory.
Fix — The directory pointed to needs to end with oraInventory
(/usr/opt/oracle/oraInventory). Modify inventory_loc in oraInst.loc to point to the valid oraInventory directory or the inst_loc in the registry.

- The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc file or /etc/oraInst.loc file or inst_loc in the registry is oraInventory, but has no subdirectories.
Fix — If the location has no subdirectories, it has been cleaned out accidentally. If you have an up-to-date backup of this area, try restoring the oraInventory; otherwise, you will need to reinstall all software versions that are on the host to repopulate the oraInventory.

- The user attempting to perform the installation cannot access the inventory location.
The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc file or /etc/oraInst.loc file or inst_loc in the registry has permissions that restrict the user running the OUI from writing to oraInventory.

Fix — Ensure that you are the correct user to perform the installation. If so, then you will need to do a recursive chmod to enable access to the oraInventory:

$ chmod -R 770 <full path>/oraInventory

... and 660 for files under that.

Permissions might not be one of the causes, but the default permissions OUI creates are 770 for directories and 660 for files.

- The group listed for group= in the /var/opt/oracle/oraInst.loc file or /etc/oraInst.loc file is different than the group of the user running the OUI, and cannot access or write to oraInventory.
Fix — Ensure that you are in the correct group to perform the installation. If so, you will need to do a recursive chgrp to specify the correct group ownership of the oraInventory:

$ chgrp -R <correct group> <full path>/oraInventory

Note:
"inst_loc" on Windows should always point to %SYSTEMDRIVE%\Program Files\Oracle\Inventory. Manually changing this to point to another directory is unsupported.

D.15 OUI - 10035

Message

You do not have permission to write to the inventory location.

Potential Causes

The inventory location is not accessible by the user attempting to perform the installation. The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc file or /etc/oraInst.loc file or inst_loc in registry has permissions that restrict the user running the OUI from writing to the oraInventory.

Possible Solutions

Ensure that you are the correct user to perform the installation. If so, you will need to do a recursive chmod to enable access to the oraInventory:

$ chmod -R 770 <full path>/oraInventory

D.16 OUI - 10036

Message

Could not create the inventory location. You may not have permission to write to this location.

Potential Causes

The Oracle user does not have proper permission for the inventory location specified during installation.

Possible Solutions

Ensure that you are the correct user to perform the installation, and that you have proper permissions in the specified directory. Check this using the following command:

% ls -l <location>

If you do not have proper permissions, provide them as shown:

% chmod -R 755 <full path>

D.17 OUI - 10038

Message

You do not have the necessary permissions to write to the inventory at <LOCATION>. Please make sure that you have the appropriate permissions to perform the installation.

Potential Causes

You do not have write permission for the inventory location specified during installation.

Possible Solutions

Ensure that you are the correct user to perform the installation, and that you have proper permissions in the specified directory. Check this using the following command:

% ls -l <location>

If you do not have proper permissions, provide them as shown:

% chmod -R 755 <full path>

D.18 OUI - 10039

Message

Unable to read install inventory <Location> on this system. Please check if you have the proper permissions to read/write to the inventory.

Potential Causes

You do not have read permission for the inventory location specified during installation.

Possible Solutions

Ensure that you are the correct user to perform the installation, and that you have proper permissions in the specified directory. Check this using the following command:

% ls -l <location>

If you do not have proper permissions, provide them as shown:

% chmod -R 755 <full path>

D.19 OUI - 10040

Message

Unable to read inventory pointer file: Check if you have the proper permissions.

Potential Causes

The inventory pointer (oraInst.loc) is owned by root and other users have read permission for it. For example:

[oracle@oracle ~]$ ls -l /etc/oraInst.loc
-rw-r--r-- 1 root root 65 Oct 3 18:42 /etc/oraInst.loc

But in this case, there is no read permission for the Oracle user on the inventory pointer.

Possible Solutions

Ensure that you are the correct user to perform the inventory actions, and that you have proper permissions in the inventory pointer (oraInst.loc). Check this using the following command:

% ls -l <location>

If you do not have proper permissions, provide them as shown:

% chmod -R 644 <location>

D.20 OUI - 10041

Message

Unable to read inventory location registry entry. Check if the registry entry exists and if you have the proper permissions.

Potential Causes

Accessing the inventory pointer (orainst_loc) key requires administrator privileges; other users will have read permission.

Possible Solutions

The following command displays the central inventory pointer (orainst_loc) key and value:

C:\>reg query HKLM\SOFTWARE\ORACLE /v inst_loc

Make sure that you have administrator privileges to read the registry HKLM\SOFTWARE\ORACLE\inst_loc.

D.21 OUI - 10044

Message

The selected location already contains an Oracle Home or APPL_TOP created while running a different OS.

Potential Causes

This error can occur for the following reasons:

- The software/patchset you are trying to install is intended for a different platform.

- The <Central_inventory>/install.platform file is corrupted.

Possible Solutions

Make sure that the software/patchset you are trying install is intended for the same platform, and make sure that the <Central_inventory>/install.platform file is not corrupted.

The install.platform file is written to only during inventory creation and does not become corrupted unless someone manually changes it.

D.22 OUI - 10053

Message

Unable to generate temporary script: Unable to continue install.

Potential Causes

This error usually occurs when generating the orainstRoot.sh script in the /tmp directory. You may not have proper permissions in the /tmp directory, or /tmp is full.

Possible Solutions

- Check the permissions of the /tmp directory:

% ls -l /tmp

- Make sure that the /tmp directory has the proper write permissions. Run this command:

% chmod 0777 /tmp ( as root )

- Check if the /tmp directory has enough space for creating the file.

D.23 OUI - 10054

Message

Unable to modify the group ownership of the OUI inventory to the requested group name. Either the specified group doesn't exist, or the current userid does not belong to that group. If the group exists, you may run the shell script as root to change the group name after installation is complete.

Potential Causes

This error usually occurs when the root.sh script attempts to modify the Central inventory group ownership.

Possible Solutions

- Make sure that the group specified at the start of the installation is an existing group.

- Make sure that you are a part of the particular group specified at the start of installation. Check the group dba as shown in the following example:

%cat /etc/group | grep dba
dba:x:502:oracle

In this example, the group is dba, the group ID is 502, and the user oracle is a part of the dba group.

D.24 OUI - 10055

Message

Error in accessing the registry.

Potential Causes

This error usually occurs when you do not have administrator rights/permissions on the registry.

Possible Solutions

- Make sure that you have administrator privileges to access/modify the registry.

- Check the permissions in regedit —> hkey_local_machine —> software —> oracle (Permissions - advanced tab).

D.25 OUI - 10056

Message

Error in updating the registry.

Potential Causes

This error usually occurs when you do not have administrator rights/permissions on the registry.

Possible Solutions

- Make sure that you have administrator privileges to access/modify the registry.

- Check the permissions in regedit —> hkey_local_machine —> software —> oracle (Permissions - advanced tab).

D.26 OUI - 10058

Message

The OUI Inventory on this system does not exist or is not writable. The possible POTENTIAL/POSSIBLE CAUSES are:1. The script <path>/orainstRoot.sh was not executed with root privileges, or an error occurred during execution.2. You are not a member of the specified installer group.

Potential Causes

One of the following situations may apply:

- The permissions for the orainstRoot.sh script are not set correctly for execution as root user.

- You are not part of the particular group specified at the start of installation.

Possible Solutions

- Make sure that the script is run as user "root."

- Make sure that you are a part of the particular group specified at the start of installation. Check the group dba as shown in the following example:

%cat /etc/group | grep dba
dba:x:502:oracle

In this example, the group is dba, the group ID is 502, and the user oracle is a part of the dba group.

D.27 OUI - 10059

Message

English cannot be removed from the selected languages. English files are always installed.

Potential Causes

This message appear when you try to deselect English. If multiple languages are defined for the installed products, Oracle Universal Installer enables language selection for all installation types through the "Languages" button.

If you click on the Product Languages, the screen with a selection/deselection list appears. In this situation, English is selected by default and you cannot deselect it, because English files are always installed.

Possible Solutions

Do not attempt to deselect English from the language list, as English files are always installed.

D.28 OUI - 10070

Message

The patch, which is part of patch set, has not been selected for installation.

Potential Causes

You may be trying to install the binaries on top of an incorrect Oracle home, such as installing 11.1.0.7.0 on top of 10.2.0.4.0.

Possible Solutions

Install the base software (11.1.0.6.0 in this example) in a separate Oracle home and the upgrade the database.

D.29 OUI - 10082

Message

The staging area needs Oracle Universal Installer version <version> or later.

Potential Causes

The OUI you are trying to use is an older version, so the installation cannot continue. For instance, you may encounter this error when trying to install Oracle RDBMS 11.2 or later with an 11.1.0.6 OUI.

Possible Solutions

Use the OUI version specific to the version of the Oracle software. For instance, installation of Oracle RDBMS 11.2 requires OUI 11.2 or later.

D.30 OUI - 10083

Message

Some of the components you selected cannot be deinstalled because they were installed using Oracle Universal Installer version {0}. Please use Oracle Universal Installer version {0} or higher to deinstall these products.

Potential Causes

The OUI you are trying to use is an older version, so the de-installation cannot continue. For instance, you may encounter this error when trying to de-install Oracle RDBMS 10.2 or later with a 10.1 OUI.

Possible Solutions

Use the OUI version specific to the version of the Oracle software for de-installation. For example, de-installation of Oracle RDBMS 11.2 requires OUI 11.2 or later.

D.31 OUI - 10088

Message

This is a required component. You cannot de-select a required component.

Potential Causes

This error can occur when you attempt to de-select a required component. There may be dependencies with the component you are trying to de-select. For example, this message appears when you are doing a custom installation of Oracle RDBMS and are trying to de-select a required component that is required for the functioning of the Oracle RDBMS kernel.

Possible Solutions

It is not possible to de-select a required component.

D.32 OUI - 10091

Message

There are no patches that need to be applied from the patchset Oracle <version> Patchset "x.x.x.x.x."

Potential Causes

- Oracle Software might already be installed on x.x.x.x.x.

- You might be applying the patchset x.x.x.x.x on an incorrect Oracle home.

- The local inventory may be corrupted.

Possible Solutions

- Start SQL*Plus and check the banner for the version to make sure that the version of the software is correct.

- Make sure that you are applying the patchset on top of the correct Oracle home.

- Make sure that the inventory is healthy. Check if OPatch lists all of the products:

% OPatch lsinventory -detail

- If the local inventory is corrupted, you need to reinstall the software, then continue with the installation.

D.33 OUI - 10092

Message

The selected patches cannot be applied in this Oracle Home. Please try installing them in a different Oracle Home.

Potential Causes

- The patch/patchset you are trying to install is not suited for the particular Oracle home.

- The patchset may be a different version; for instance, when you are trying to install a 11.1.0.7.0 Oracle home on top of a 10.2.0.4.0 Oracle home.

- The patchset you are trying to install is a lower version, such as installing an 11.1.0.7.0 patchset on top of an 11.2 Oracle home.

Possible Solutions

- Check the version of the Oracle home:

% <ORACLE_HOME>/OPatch/OPatch lsinventory -detail

- Make sure that the patchset is suited for the version of the Oracle home.

D.34 OUI - 10094

Message

Problem in saving inventory. Installation cannot continue.

Potential Causes

This error message can occur because you do not have proper permissions on the inventory, or there is an OUI bug.

Possible Solutions

Before you install the 11.2 software, make sure you have sufficient write permissions on the central inventory and the local inventories of all existing Oracle home directories listed in the Central inventory.

D.35 OUI - 10095

Message

You may not have enough space to write to the inventory. Do you still want to continue?

Potential Causes

This error occurs when the space is full in the disk where the inventory resides.

Possible Solutions

Make sure that you have sufficient space in the disk before you continue with the installation. Otherwise, continuing may lead to inventory corruption.

D.36 OUI - 10096

Message

You may not have enough space to write to <location>. Please create more space at this location and try again.

Potential Causes

The disk is full where the Oracle home is being installed or already installed. The base software/patchset installation can therefore not continue.

Possible Solutions

Add more space to the disk and try the installation again.

D.37 OUI - 10104

Message

Some of the configuration assistants failed. It is strongly recommended that you retry the configuration assistants at this time. Not successfully running any recommended assistants means your system will not be correctly configured. Select the failed assistants and click the 'Retry' button to retry them.

Potential Causes

Some of the recommended Configuration Assistants failed during installation.

Possible Solutions

Retry the failed Configuration Assistants.

D.38 OUI - 10105

Message

Some of the configuration assistants failed. However, these are optional assistants, so they are not required for the correct configuration of your system. If you want to try to run those assistants again, select the failed assistants and click the 'Retry' button.

Potential Causes

Some of the optional Configuration Assistants failed during installation.

Possible Solutions

Retry the failed Configuration Assistants or invoke the Configuration Assistant after the installation. For example, for DBCA:

<ORACLE_HOME>/bin/dbca

D.39 OUI - 10116

Message

Unable to synchronize home. Not enough permission to write to directory.

Potential Causes

OUI attempts to synchronize all the Oracle homes at the end of the installation. This message can occur when the user installing Oracle does not have sufficient permissions on the other Oracle home.

Possible Solutions

Make sure that you have sufficient permissions for the Oracle homes, or you are from the group specific to all the installations.

D.40 OUI - 10122

Message

There was a problem in accessing the staging area. File not found.

Potential Causes

OUI expects certain files to be present in the staging area, but OUI could not find them because the staging area may be corrupted.

Possible Solutions

Make sure that the downloaded software (staging area) is not corrupted.

D.41 OUI - 10135

Message

This inventory requires Oracle Universal Installer version {0} or higher.

Potential Causes

The OUI you are trying to use is an older version, so the inventory operations cannot continue. For example, you may encounter this error when trying to update the inventory of Oracle RDBMS 11.2 or later with an 11.1.0.6 OUI.

Possible Solutions

Use the OUI specific to the version of the Oracle software for de-installation.

D.42 OUI - 10136

Message

An <OH_Name> with name <NAME> already exists at location. Please specify another location for <path>.

Potential Causes

An Oracle home already exists in the path selected for the installation.

Possible Solutions

Select another path for the installation, or de-install the Oracle home already installed in the particular path (if no longer required) and perform the new installation.

D.43 OUI - 10137

Message

An Oracle home with name <Name> already exists at location. Please specify another name.

Potential Causes

An Oracle home with the specified name already exists in the inventory.

Possible Solutions

Specify another name for the Oracle home and continue with the installation.

D.44 OUI - 10153

Message

The Oracle home is not valid for cloning. Install-time information cannot be retrieved for component.

Potential Causes

This error can occur because some of the components are not properly installed or the inventory is not properly updated.

Possible Solutions

Either correctly install the missing components in the source ORACLE_HOME or remove them prior to cloning.

E Oracle Universal Installer API Inventory

Oracle Universal Installer (OUI) contains the following APIs (Application Programming Interfaces):

- Package

- Class/Interface

- Annotation Type

- Enum

- Use

- Tree (Class Hierarchy)'

- Deprecated API

- Index

- Prev/Next

- Frames/No Frames

- All Classes

- Serialized Form

- Constant Field Values

E.1 Package

Each package has a page that contains a list of its classes and interfaces, with a summary for each. This page can contain six categories:

- Interfaces (italic)

- Classes

- Enums

- Exceptions

- Errors

- Annotation Types

E.2 Class/Interface

Each class, interface, nested class and nested interface has its own separate page. Each of these pages has three sections consisting of a class/interface description, summary tables, and detailed member descriptions:

- Class inheritance diagram

- Direct Subclasses

- All Known Implementing Classes

- Class/interface declaration

- Class/interface description

- Nested Class Summary

- Field Summary

- Constructor Summary

- Method Summary

- Field Detail

- Constructor Detail

- Method Detail

Each summary entry contains the first sentence from the detailed description for that item. The summary entries are alphabetical, while the detailed descriptions are in the order they appear in the source code. This preserves the logical groupings established by the programmer.

E.3 Annotation Type

Each annotation type has its own separate page with the following sections:

- Annotation Type declaration

- Annotation Type description

- Required Element Summary

- Optional Element Summary

- Element Detail

E.4 Enum

Each enum has its own separate page with the following sections:

- Enum declaration

- Enum description

- Enum Constant Summary

- Enum Constant Detail

E.5 Use

Each documented package, class and interface has its own Use page. This page describes what packages, classes, methods, constructors and fields use any part of the given class or package. Given a class or interface A, its Use page includes subclasses of A, fields declared as A, methods that return A, and methods and constructors with parameters of type A. You can access this page by first going to the package, class or interface, then clicking on the "Use" link in the navigation bar.

E.6 Tree (Class Hierarchy)'

There is a Class Hierarchy page for all packages, plus a hierarchy for each package. Each hierarchy page contains a list of classes and a list of interfaces. The classes are organized by inheritance structure starting with java.lang.Object. The interfaces do not inherit from java.lang.Object.

- When viewing the Overview page, clicking on "Tree" displays the hierarchy for all packages.

- When viewing a particular package, class or interface page, clicking "Tree" displays the hierarchy for only that package.

E.7 Deprecated API

The Deprecated API page lists all of the API that have been deprecated. A deprecated API is not recommended for use, generally due to improvements, and a replacement API is usually given. Deprecated APIs may be removed in future implementations.

E.8 Index

The Index contains an alphabetic list of all classes, interfaces, constructors, methods, and fields.

E.9 Prev/Next

These links take you to the next or previous class, interface, package, or related page.

E.10 Frames/No Frames

These links show and hide the HTML frames. All pages are available with or without frames.

E.11 All Classes

The All Classes link shows all classes and interfaces except non-static nested types.

E.12 Serialized Form

Each serializable or externalizable class has a description of its serialization fields and methods. This information is of interest to re-implementors, not to developers using the API. While there is no link in the navigation bar, you can get to this information by going to any serialized class and clicking "Serialized Form" in the "See also" section of the class description.

E.13 Constant Field Values

The Constant Field Values page lists the static final fields and their values.

Glossary

name (attribute)

Component name.

version (attribute)

Component version.

type (attribute)

Component category that qualifies component to enable customized processing by type. For example, a JDK component.

replicable (attribute)

Defines whether a component can be installed under multiple directories (fan-out) based on the directory mapping.

file-map (element)

Container element holding elements and attributes that describe file characteristics including source/target mapping.

file-perms (element)

Container element holding elements and attributes that define file permissions for artifacts.

libraries (element)

Container element holding elements and attributes that define library types and associated content used to generate libraries during installation.

stringsubs (element)

Container element holding elements and attributes that define string substitution operations applicable to specific artifacts.

platform (element)

Defines operating system and architecture.

locale (element)

Defines specific language and geographic region.

symbol (attribute)

A unique string used as a reference by a distribution to define the high-level directory for this file-group.

bootstrap (attribute)

Defines a component that must be loaded into the launch process during installation.

include (element)

Container element defining artifacts to include from the set of selected files.

exclude (element)

Container element defining artifacts to exclude from the set of selected files.

directory (element)

Container element defining a directory used to select a set of artifacts via include and exclude definitions.

regex (attribute)

Specifies a group of files based on a regular expression.

wildcard (attribute)

Specifies a group of files using a more simplistic expression (globbing).

name (attribute)

Specifies a simple file name.

match-dirs (attribute)

Specifies if an expression should be applied to directories for matching purpose (default="false").

match-files (attribute)

Specifies if an expression should be applied to files for matching purpose (default="true").

source (attribute)

Identifies the current location of the directory to evaluate for packaging in this component.

dest (attribute)

Identifies the target location in the Oracle Home for the specified directory contents.

recurse (attribute)

Specifies whether to recurse subdirectories for the indicated directory (default="true").

deinstall (attribute)

Specifies whether the directory is eligible for standard de-install (default="true").

include-empty-dirs (attribute)

Indicates whether empty directories should be considered for packaging.

mode (attribute)

Defines permissions to set for the indicated file or directory.

preserve-symlinks (attribute)

Defines whether to preserve symlinks when packaging and installing (default="false").

file (element)

Container element defining a file or files.

rule (element)

Container element defining rules for processing a file. For example, including or excluding a file based on the state of a variable.

os-family (attribute)

Constrains installation of the file by matching on os-family (enumeration of windows and unix), allowing a more flexible/generic constraint.

symlink (attribute)

Specifies the creation of a symbolic link based on a file in the destination location.

manifest (element)

Defines manifest creation for the generated library and specifies a set of attributes to include in the manifest.

entry (element)

Specifies artifacts to include in the generated library.

name (attribute)

Specifies the library name.

type

Specifies the library type (none, runtime, manifest, interface, client, mergedJar).

version

Specifies the version of the library to be used in both generation as well as identification for inclusion at the feature-set level.

location

Identifies the location for the generated library. Library types are the primary driver for location of generated libraries and use of the location attribute should be reserved for exceptional use cases.

visibility

Determines whether a library is intended for direct customer consumption and whether the library is generated at the component level or designed solely for consumption at the featureset level. Valid values are public, internal, and none.

fileResolver

For mergedJar library types, this specifies the set of algorithms used to merge artifacts.

manifestResolver

Similar to fileResolver, this specifies the set of algorithms used to merge manifests in jars.

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

A

ACCEPT_LICENSE_AGREEMENT parameter, 3.4.4

ARU_IDs for platforms, 2.4.1.3

C

Central Inventory, 2.4.1.2

consolidate multiple Central Inventories, 2.4.4

creating, 2.4.2

inventory file, 2.4.1.2

logs directory, 2.4.1.2

pointer file, 2.4.1.1

recovering from corruption, 2.4.9

removing from Unix, 2.4.3.2

Central Invetory

removing from Windows platforms, 2.4.3.2

cloning, 4.4.4, 5

cloning phase, 5.3.2

features and benefits, 5.1

prepare source Oracle home, 5.3.1

CLUSTER_NODES parameter, 3.4.4 command line arguments, 4.4.2 components file, 2.4.1.3

sample, C.3

creating the Central Inventory, 2.4.2

D

debugging, A.5

automated inventory backups, A.5.2

DECLINE_SECURITY_UPDATES, 3.4.4 Deinstall

tool, 2.7

utility, 2.7

DEINSTALL_LIST parameter, 3.4.4 deinstallation, 1.5.2 DEPENDENCY_LIST parameter, 3.4.4 directory structure

for Windows, 2.5.3

disk space requirements, 1.2 dloning, 1.5.3

E

errors

exceptions from action libraries, A.1

failed to connect to server error, 4.2.6

incomplete stage and missing files in file groups, A.1

out of "temp" space, A.1

UNCAUGHT_RUNTIME exception, A.1

Exceed tool, A.3.1 exit codes, 4.4.3

F

failed to connect to server error, 4.2.6

features, 1.1

FROM_LOCATION response file parameter, 3.4.4

FROM_LOCATION_CD_LABEL parameter, 3.4.4

H

home properties file, 2.4.1.3

ARU_IDs for platforms, 2.4.1.3

home property file

example, 2.4.1.3

Home Selector

how it works, 2.5.2

overview, 2.5.1

I

INCLUDE response file parameter, 3.4.4

INSTALL_TYPE response file parameter, 3.4.4

installation, 1.5.1

from staged HTTP location, 4.2.5.3

from the Web, 4.2.5.3

multiple CD-ROMs, 4.2.5.2

single CD-ROM, 4.2.5.1

special UNIX instructions, 4.2.6

umounting a CD, 4.2.5.2

installation media, 4.2.5 installation modes, 4.2.5

interactive, 4.2.3

silent, 4.2.3

suppressed, 4.2.3

internationalization

installation dialogs language, 6.1

language add-on, 6.3

inventory compare

command options, 7.2.4

console output, 7.2.1

.csv file output, 7.2.2

.xml file output, 7.2.3

inventory utilities, 7

inventory compare, 7.2

inventory view, 7.1

inventory view

command options, 7.1.4

console output, 7.1.1

.csv file output, 7.1.2

.xml file output, 7.1.3

J

Java Runtime Environment (JRE), 1.2

JRE, 1.2

L

LOCAL_NODE parameter, 3.4.4

LOCATION_FOR_DISK2 parameter, 3.4.4

log files, 4.5

M

memory requirements, 1.2

modes of installation

interactive, 4.2.3

silent, 4.2.3

suppressed, 4.2.3

multi-CD support, response file, 3.4.4 multiple Oracle homes, 2.3 MYORACLESUPPORT_PASSWORD, 3.4.4 MYORACLESUPPORT_USERNAME, 3.4.4

N

NEXT_SESSION response file parameter, 3.4.4

NEXT_SESSION_ON_FAIL parameter, 3.4.4

NEXT_SESSION_RESPONSE parameter, 3.4.4

NLS_ENABLED variable, 6.1

O

online help, 4.2.1

Optimal Flexible Architecture (OFA), 2

ORACLE_BASE directory, 2.5.4.1

OPTIONAL_CONFIG_TOOLS parameter, 3.4.4 Oracle Base, 2 Oracle Home, 2

determing default Oracle home, 2.2

multiple Oracle homes, 2.3

path, 2.2

remove, 2.7

Oracle home inventory

ARU_IDs for platforms, 2.4.1.3

Oracle homes

directory structure

Windows, 2.5.3

Oracle Universal Installer

inventory

description, 1.6.1

operations, 1.5.6

Oracle Universal Installer inventory, 2.4 ORACLE_BASE directory, 2.5.4.1 ORACLE_BASE response file parameter, 3.4.4 ORACLE_HOME response file parameter, 3.4.4 oraInst.loc file, 2.4.1.1 oraparam.ini file

BOOTSTRAP_CLASSPATH parameter, 4.2.2

BOOTSTRAP_SIZE parameter, 4.2.2

BUNDLE, 4.2.2

BUNDLE_FAILURE_MESSAGE, 4.2.2, 4.2.2, 4.2.2

CERTIFIED_VERSION_LOCATION, 4.2.2

CERTIFIED_VERSION_WARN, 4.2.2

COPY_THREADS parameter, 4.2.2

DEFAULT_HOME_NAME parameter, 4.2.2

DISPLAY_VERSION parameter, 4.2.2

EXT_CLASSPATH parameter, 4.2.2

FILESET parameter, 4.2.2

FILESET_FAILURE_MESSAGE, 4.2.2

GLIBC parameter, 4.2.2

GLIBC_FAILURE_MESSAGE, 4.2.2

GMAKE parameter, 4.2.2

HOTSPOT_JAVA_OPTIONS parameter, 4.2.2

IBM_JAVA_OPTIONS parameter, 4.2.2

INSTALL_CLASS parameter, 4.2.2

INSTALL_ONECLICK_CLASS parameter, 4.2.2

JAVA_OPTIONS parameter, 4.2.2

JAVA_USE_64BIT, 4.2.2

JAVA_VERSION parameter, 4.2.2

JROCKIT_JAVA_OPTIONS parameter, 4.2.2

KERNEL, 4.2.2

KERNEL_FAILURE_MESSAGE, 4.2.2

LOG_PATCHES_TO_CONSOLE, 4.2.2

MIN_DISPLAY_COLORS, 4.2.2

MIN_DISPLAY_COLORS_FAILURE_MESSAGE, 4.2.2

NLS_ENABLED parameter, 4.2.2

PACKAGES, 4.2.2

PACKAGES_FAILURE_MESSAGE, 4.2.2

PATCH, 4.2.2

PATCHES_FAILURE_MESSAGE, 4.2.2

PERL, 4.2.2

PLATFORM_PREREQS parameter, 4.2.2

PROCESSOR, 4.2.2

PROCESSOR_FAILURE_MESSAGE, 4.2.2

SERVICE_PACK, 4.2.2

SERVICE_PACK_FAILURE_MESSAGE, 4.2.2

SOURCE parameter, 4.2.2

SWAP_SPACE, 4.2.2

SWAP_SPACE_FAILURE_MESSAGE, 4.2.2

TEMP_SPACE, 4.2.2

TEMP_SPACE_FAILURE_MESSAGE, 4.2.2

USEJDKONLY parameter, 4.2.2

USEJREONLY parameter, 4.2.2

VM_TYPES parameter, 4.2.2

OUI cloning considerations, 4.4.4 OUI errors, A.1 OUI exit codes, 4.4.3 OUI log files, 4.5 OUI prerequisites, 4.1 out of "temp" space error, A.1

P

prerequisites before installation, 4.1

PROXY_HOST, 3.4.4

PROXY_PORT, 3.4.4

PROXY_PWD, 3.4.4

PROXY_USER, 3.4.4

R

Reflection X, troubleshooting, A.3.1

REMOTE_NODES parameter, 3.4.4

REMOVE_HOMES parameter, 3.4.4

requirements

disk space, 1.2

JRE, 1.2

memory, 1.2

response file, 3.1

ACCEPT_LICENSE_AGREEMENT parameter, 3.4.4

CLUSTER_NODES parameter, 3.4.4

comments, 3.4.2

DECLINE_SECURITY_UPDATES, 3.4.4

definition, 3.1.2

DEINSTALL_LIST parameter, 3.4.4

DEPENDENCY_LIST parameter, 3.4.4

entry order, 3.4.1.2

FROM_LOCATION response file parameter, 3.4.4

FROM_LOCATION_CD_LABEL parameter, 3.4.4

header, 3.4.3

INCLUDE parameter, 3.4.4

INSTALL_TYPE parameter, 3.4.4

installing using a response file, 3.5

LOCAL_NODE parameter, 3.4.4

location, 3.1.2

LOCATION_FOR_DISK2 parameter, 3.4.4

modifying, 3.2

MYORACLESUPPORT_PASSWORD, 3.4.4

MYORACLESUPPORT_USERNAME, 3.4.4

NEXT_SESSION parameter, 3.4.4

NEXT_SESSION_ON_FAIL parameter, 3.4.4

NEXT_SESSION_RESPONSE parameter, 3.4.4

optional parameters, 3.5.2

OPTIONAL_CONFIG_TOOLS parameter, 3.4.4

ORACLE_BASE parameter, 3.4.4

ORACLE_HOME parameter, 3.4.4

parameters, 3.4.4

PROXY_HOST, 3.4.4

PROXY_PORT, 3.4.4

PROXY_PWD, 3.4.4

PROXY_USER, 3.4.4

REMOTE_NODES parameter, 3.4.4

REMOVE_HOMES parameter, 3.4.4

RESPONSEFILE_VERSION parameter, 3.4.4

RESTART_SYSTEM parameter, 3.4.4

SECURITY_UPDATES_VIA_MYORACLESUPPORT, 3.4.4

SELECTED_LANGUAGES, 3.4.4

setting variables from command line, 3.5.3

specifying, 3.5.1

TOPLEVEL_COMPONENT parameter, 3.4.4

UNIX_GROUP_NAME parameter, 3.4.4

variable lookup order, 3.4.1.1

variable values, 3.4.1.3

RESPONSEFILE_VERSION parameter, 3.4.4 RESTART_SYSTEM parameter, 3.4.4

S

SECURITY_UPDATES_VIA_MYORACLESUPPORT, 3.4.4

SELECTED_LANGUAGES, 3.4.4

SELECTED_LANGUAGES variable, 6.2

setting response file variables, 3.5.3

silent installation, 3.1.1

reasons for performing, 3.1.3

staged HTTP location, installing from, 4.2.5.3 starting OUI, 4.4.1 system requirements, 1.2

disk space, 1.2

JRE, 1.2

memory, 1.2

T

Tarantella, troubleshooting, A.3.1

target home, 2.3.1

TOPLEVEL_COMPONENT parameter, 3.4.4

translation

installation dialogs language, 6.1

language add-on, 6.3

troubleshooting

automated inventory backups, A.5.2

debugging mechanisms, A.5

Exceed, A.3.1

Reflection X, A.3.1

Tarantella, A.3.1

U

UNIX installation

special instructions, 4.2.6

UNIX_GROUP_NAME parameter, 3.4.4 unmounting a CD, 4.2.5.2

V

variable

values for response file, 3.4.1.3

variable lookup order, 3.4.1.1 variable NLS_ENABLED, 6.1 variable SELECTED_LANGUAGES, 6.2

W

Web installation, 4.2.5.3

Windows, directory structure for, 2.5.3

Oracle Legal Notices

Copyright Notice

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

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

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.

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction 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.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

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 that have purchased support 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.