| Oracle® Universal Installer and OPatch User's Guide 10g Release 2 (10.2) for Windows and UNIX Part Number B16227-01 |
|
|
View PDF |
| Oracle® Universal Installer and OPatch User's Guide 10g Release 2 (10.2) for Windows and UNIX Part Number B16227-01 |
|
|
View PDF |
This chapter is designed to aid the developers, administrators, and all other users who install Oracle software, to understand the key concepts involved in Oracle Universal Installer.
This chapter includes the following sections:
Oracle offers two utilities for software deployment:
Oracle Universal Installer to install Oracle products
OPatch to apply interim patches
Oracle Universal Installer 10g Release 2 (10.2) is a Java-based installer that enables you to install Oracle components from CDs or from a staged HTTP location. It performs component-based installs as well as complex installs, such as integrated bundle and suite installs, and installs over the Web.
OPatch is an Oracle supplied utility to assist you with the process of applying interim patches to Oracle's software. OPatch 10.2 is a Java-based utility that needs Oracle Universal Installer. It works on all operating systems for which Oracle releases software. For more information on OPatch, refer to Chapter 8, "Oracle Software Patching Using OPatch".
Oracle Universal Installer and OPatch performs the following activities:
Installation is the process of choosing products from a release or stage area and deploying them in the target directory. There are four modes of installation, which are explained in the section "Modes of Installation".
De-installation is the process of removing an installed product from the installation area. A de-installation can be cancelled, resumed or rolled back. It can be executed either interactively or silently.
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 will replay 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 will run the actions in the clone mode. Each action will decide how to behave during clone time. For more information on cloning refer to Chapter 7, "Oracle Software Cloning Using Oracle Universal Installer".
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, refer to Chapter 8, "Oracle Software Patching Using OPatch".
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. For example, you may want to convert your Oracle9i Database to Oracle 10gR2 (10.2) Database, which is called an upgrade.
A group of patches form a patchset. For example, You may want to convert your Oracle 10gR1 (10.1) Database from version 10.1.1 to version 10.1.2, then it is called applying a patchset.
An Oracle home may be installed on multiple nodes in a cluster. You can extend the cluster for a particular Oracle home using the -addNode flag of Oracle Universal Installer. More than one node may be added to the Oracle home. The Oracle Universal Installer with the -addNode flag is always run on the local node and not on the node(s) to be added. You can add nodes to an Oracle Clusterware node or a Real Application Clusters node depending upon whether the node addition is being performed at the Oracle Clusterware layer or the Real Application Clusters database layer. For more information on adding nodes, refer to section "Adding Additional Nodes to the Cluster for Mass Deployment".
Oracle Universal Installer supports the following inventory operations:
Oracle Universal Installer uses the -attachHome flag to attach an Oracle home to the inventory to set up the Central Inventory or to register an existing Oracle home with the Central Inventory.
For more information, refer to section "Creating the Central Inventory".
Oracle Universal Installer uses the -detachHome flag to remove an Oracle home from the Central Inventory.
For more information, refer to section "Detaching Oracle Homes from the Central Inventory".
Oracle Universal Installer uses the -updateNodeList flag to get the list of nodes and update the inventory.xml file. If the CRS flag is set to TRUE, then the oraclehomeproperties.xml file is updated with the Oracle Clusterware home information.
For more information, refer to section "Updating the Nodes of a Cluster".
The following are the major entities created when you run Oracle Universal Installer.
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, refer to section "About the Oracle Universal Installer Inventory".
An Oracle home is the system context in which the Oracle products run. This context consists of the following:
The directory location where the products are installed.
The corresponding system path setup.
The program groups associated with the products installed in that home (where applicable).
The services running from that home.
For more information on Oracle homes, refer to Chapter 3, "Managing Oracle Homes".
You can run the Oracle Universal Installer in the following modes:
You can use the graphical user interface (GUI) 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.
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 most 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 by hand.
You can use this mode to bypass the GUI 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 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 refer to Chapter 4, "Customizing and Creating Response Files".
A cluster installation uses Oracle Universal Installer to install software on the nodes of a cluster that are network reachable and bound together by Oracle Clusterware. You can use Oracle Universal Installer to extend the Oracle home of a product installation to include additional nodes on the cluster. You need to install Oracle Clusterware for a Cluster Install.
For more information on cluster installs refer to Chapter 6, "Cluster Environment Installations".
