Fusion Middleware Documentation
Advanced Search


Installing with the Oracle Universal Installer
Close Window

Table of Contents

Show All | Collapse

1 Using the Oracle Universal Installer

This chapter introduces the Oracle Universal Installer for Oracle Fusion Middleware 12c (12.1.2).

This chapter contains the following sections:

1.1 Verifying System Requirements

See "Verifying Requirements for Oracle Universal Installer" in Oracle Fusion Middleware System Requirements and Specifications to verify and prepare to run the Oracle Universal Installer on your system.

1.2 Understanding the Oracle Central Inventory

Each time the Oracle Universal Installer is run, it checks your system for a central inventory location. The Oracle central inventory stores information about all Oracle software products installed in all Oracle homes on your system, provided the products were installed using the 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.

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.

All Oracle homes in the source environment must be registered in the same Oracle inventory. If you have installed multiple components under the same Oracle home, but used different Oracle inventory locations, the scripts are not able to detect all of the Oracle homes.

1.2.1 Finding the Oracle Inventory on UNIX Operating Systems

To find the Oracle Inventory on UNIX operating systems, look for the oraInst.loc file in the following directories (default locations):

  • Linux: /etc/oraInst.loc

  • HP-UX and Solaris: /var/opt/oracle/oraInst.loc

1.2.2 Finding the Oracle Inventory on Windows Operating Systems

On Windows operating systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory. If you are using a 32-bit installer on a 64-bit Windows machine, the inventory directory is C:\Program Files (x86)\Oracle\Inventory.

1.3 Viewing the Contents of an Oracle Home

After your Oracle Fusion Middleware product is installed, you can use the viewInventory.sh (on UNIX operating systems) or viewInventory.cmd (on Windows operating systems) script to view the contents of any Oracle home directory. The following information is provided in the output:

  • Name and version of installed distributions.

  • Name and version of installed feature sets.

  • Name and version of installed components.

  • Patch ID and unique ID of installed patches.

Note:

For more information about distributions and feature sets, see "Understanding Product Distributions" in Planning an Installation of Oracle Fusion Middleware.

The script output can be sent to the console window, an XML file, or a CSV file which can be imported into spreadsheets.

The script is located in the ORACLE_HOME/oui/bin directory.

To run the script on UNIX operating systems, use the following syntax:

./viewInventory.sh
   [-jreLoc jre_location]
   [-oracle_home oracle_home_location]
   [-output_format [report|xml|csv]]
   [-output_file output_file_location_and_name]

to run the script on Windows operating systems, use the following syntax:

viewInventory.cmd
   [-jreLoc jre_location]
   [-oracle_home oracle_home_location]
   [-output_format [report|xml|csv]]
   [-output_file output_file_location_and_name]

All of the parameters for this command are optional, and are described in Table 1-1:

Table 1-1 Parameters for the viewInventory Script

Parameter Description

-jreLoc

Before running the script, you must set the JAVA_HOME environment variable on your system to point to a certified JDK (up to but not including the /bin directory). For example:

setenv JAVA_HOME /home/Java/jdk7_version

If you do not set the JAVA_HOME, you must provide the location using the -jreLoc parameter from the command line. For example:

viewInventory.cmd -jreLoc /home/Java/jdk7_version

-oracle_home

The Oracle home for which you want to view inventory information. If no Oracle home is specified, the default is the Oracle home from where the script is run.

-output_format

The format for which you want the output to be recorded. Valid values are:

If no output format is specified, the default will be detected based on whatever is specified for -output_file.

-output_file

The name and format of the output file. This parameter is only required if you want to save your output to XML or CSV format; if no output file is specified, the script will default to the console window.


1.4 Comparing the Contents of Two Oracle Homes

After your Oracle Fusion Middleware product is installed, you can use the compareInventory.sh (on UNIX operating systems) or compareInventory.cmd (on Windows operating systems) script to compare the contents of any two Oracle home locations. If any differences are found, the following information is provided in the output:

  • Location of the Oracle home

  • Name and version of the distribution.

  • Name and version of the feature set.

  • Name and version of the component.

  • Patch ID and unique ID of patch.

Note:

For more information about distributions and feature sets, see "Understanding Product Distributions" in Planning an Installation of Oracle Fusion Middleware.

The script output can be sent to the console window, an XML file, or a CSV file which can be imported into spreadsheets.

The script is located in the ORACLE_HOME/oui/bin directory.

To run the script on UNIX operating systems, use the following syntax:

./compareInventory.sh
   -oracle_home1 oracle_home1_location
   -oracle_home2 oracle_home2_location
   [-jreLoc jre_location]
   [-input_type1 [dir|xml]]
   [-input_type2 [dir|xml]]
   [-output_file output_file_location_and_name]

To run the script on Windows operating systems, use the following syntax:

compareInventory.cmd
   -oracle_home1 oracle_home1_location
   -oracle_home2 oracle_home2_location
   [-jreLoc jre_location]
   [-input_type1 [dir|xml]]
   [-input_type2 [dir|xml]]
   [-output_file output_file_location_and_name]

Only the -oracle_home1 and -oracle_home2 parameters are required. All of the parameters for this command are optional, and are described in Table 1-2:

Table 1-2 Parameters for the compareInventory Script

Parameter Description

-oracle_home1

Full path to one of the two Oracle home locations you want to compare.

-oracle_home2

Full path to the second Oracle home location you want to compare.

-jreLoc

Before running the script, you must set the JAVA_HOME environment variable on your system to point to a certified JDK (up to but not including the /bin directory). For example:

setenv JAVA_HOME /home/Java/jdk7_version

If you do not set the JAVA_HOME, you must provide the location using the -jreLoc parameter from the command line. For example:

compareInventory.cmd -jreLoc /home/Java/jdk7_version

-input_type1

Specify whether or not the data from -oracle_home1 is provided as an XML file, or as a directory location. Valid values are:

  • dir (for directory location)

  • xml (for XML file)

If no value is specified the script will automatically detect the source format.

-input_type2

Specify whether or not the data from -oracle_home2 is provided as an XML file, or as a directory location. Valid values are:

  • dir (for directory location)

  • xml (for XML file)

If no value is specified the script will automatically detect the source format.

-output_file

The name and format of the output file. This parameter is only required if you want to save your output to XML or CSV format; if no output file is specified, the script will default to the console window.


1.5 Understanding Available Modes of Installation

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

  • Graphical mode

    Graphical-mode installation is an interactive, GUI-based method for installing your software. It can be run on both Windows and UNIX systems.

    In order to run the installation program in graphical mode on UNIX operating systems, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do.

    Additionally on UNIX operating systems, the DISPLAY environment variable must be set to the monitor where you want the installer GUI to appear, and the user performing the installation must have permissions to access the machine to which DISPLAY is set. Refer to your operating system documentation for specific instructions on how to do this, as procedures vary depending on your exact operating system.

  • Silent mode

    Silent-mode installation is a non-interactive method of installing your software. You use a properties file (called a response file) to specify the installation options. You can run silent-mode installation from either a script or from the command line. Silent-mode installation allows you to define the installation configuration only once, and then use that configuration to duplicate the installation on many machines.

    For more information about silent mode installation and how to create a response file, see Chapter 2. For sample response files, see Appendix C.

1.6 Starting the Oracle Universal Installer

The Oracle Universal Installer can be started in various ways, depending on how the product distribution is packaged.

1.6.1 Starting the Oracle Universal Installer in a Generic (.jar) Distribution

To start the Oracle Universal Installer that is packaged in a .jar distribution, make sure that you have a certified JDK already installed on your system. See the appropriate certification document for 12c (12.1.2) on the Oracle Fusion Middleware Supported System Configurations page.

To start the installer without setting any environment variables:

  1. Go to the directory where you downloaded the product distribution.

  2. Invoke the java -jar command from your JDK directory. For example:

    On UNIX operating systems:

    /home/Oracle/jdk7_15/jdk1.7.0_15/bin/java -jar distribution_name.jar
    

    On Windows operating systems:

    C:\Program Files\Java\jdk7_15\bin\java -jar distribution_name.jar
    

You can also set the JAVA_HOME and PATH environment variables to run the installer:

  1. Set the JAVA_HOME environment variable on your system to the JDK directory. For example:

    On UNIX operating systems

    JAVA_HOME=/home/Oracle/jdk7_15/jdk1.7.0_15; export $JAVA_HOME
    

    On Windows operating systems

    set JAVA_HOME=C:\Program Files\Java\jdk1.7.0_15
    
  2. Add the directory of the appropriate JDK to the PATH variable definition on the target system. For example:

    On UNIX operating systems:

    PATH=$JAVA_HOME/bin:$PATH; export PATH
    

    On Windows operating systems:

    set PATH=%JAVA_HOME%\bin:%PATH%
    
  3. Go to the directory where you downloaded the installation program.

  4. Launch the installation program by entering the following command:

    java -jar distribution_name.jar
    

1.6.2 Starting the Oracle Universal Installer in a Platform-Specific Distribution

Some products (for example, Oracle HTTP Server) may be available in a product-specific distribution; on UNIX operating systems, the distribution is available as a .bin file, and on Windows operating systems, as a .exe file.

To start the Oracle Universal Installer in a .bin distribution:

  1. Change the permissions of the .bin file:

    chmod a+x distribution_name.bin
    
  2. Execute the .bin file:

    ./distribution_name.bin
    

To start the Oracle Universal Installer in a .exe distribution, use a Windows folder to navigate to the directory containing the distribution, and double-click on the distribution_name.exe file.