This chapter contains the following sections:
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.
Each time the Oracle Universal Installer is run, it checks your system for a central inventory location. If no central inventory location is found (for example, this is the first time you are installing an Oracle product on your system), you will be prompted to create one (Specifying the Oracle Central Inventory Location on UNIX Operating Systems).
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 central 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 any Oracle home, Domain home or Application home location.
All installations installed into the same Oracle home must be associated with the same Oracle central inventory.
This section describes how you can set the Oracle Central Inventory location.
If no existing Oracle central inventory is detected on your UNIX operating system when installing Oracle products using the Oracle Universal Installer graphical interface, you will see the Installation Inventory Setup screen.
Follow the instructions on the Installation Inventory Setup screen to setup your Oracle central inventory. This must be done before you can continue with your product installation.
This does the following:
Creates the Oracle central inventory directory (default is USER_HOME
/oraInventory
). This directory is owned by the user performing the installation.
Creates the createCentralInventory.sh
script inside the Oracle central inventory location (for example, USER_HOME
/oraInventory/createCentralInventory.sh
).
This script must be run as root
to register your Oracle central inventory location to a standard file on your system (for example, /etc/oraInst.loc
). See Oracle Central Inventory Location on UNIX Operating Systems).
On UNIX operating systems, for silent installation, the Oracle central inventory must be setup on your system before you run the installation. To do this, you must run the /tmp/createCentralInventory.sh
script as root
to create the central inventory.
Note that after doing so, all of directories that are created on your system by running the script are owned by root
instead of the user performing the installation. For more information on creating the Oracle central inventory using silent installation, see UNIX Users: Creating the Central Inventory
To find the Oracle central inventory on UNIX operating systems, look for the oraInst.loc
file in the following directories (default locations):
Linux: /etc/oraInst.loc
HP-UX, IBM AIX, Mac OS X, and Solaris: /var/opt/oracle/oraInst.loc
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 options for this command are optional and are described in the following table.
Table 1-1 Options for the viewInventory Script
Options | Description |
---|---|
|
The |
|
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. |
|
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 |
|
The name and format of the output file. This option 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. |
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 Oracle Fusion Middleware 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
options are required. All of the options for this command are optional and are described in the following table.
Table 1-2 Options for the compareInventory Script
Option | Description |
---|---|
|
Full path to one of the two Oracle home locations you want to compare. |
|
Full path to the second Oracle home location you want to compare. |
|
The |
|
Specify whether or not the data from
If no value is specified the script will automatically detect the source format. |
|
Specify whether or not the data from
If no value is specified the script will automatically detect the source format. |
|
The name and format of the output file. This option 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.
|
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 Using the Oracle Universal Installer in Silent Mode . For sample response files, see Sample Response Files for Silent Installation and Deinstallation.
The Oracle Universal Installer can be started in various ways, depending on how the product distribution is packaged.
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.2.1) on the Oracle Fusion Middleware Supported System Configurations page.
To start the installer without setting any environment variables:
Go to the directory where you downloaded the product distribution.
Invoke the java -jar
command located within your JDK home. For example:
On UNIX operating systems:
/home/Oracle/jdk8_51/jdk1.8.0_51/bin/java -jar distribution_name.jar
On Windows operating systems:
C:\Program Files\Java\jdk8_51\bin\java -jar distribution_name.jar
You can also set the JAVA_HOME
and PATH
environment variables to run the installer:
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:
To start the Oracle Universal Installer in a.exe
distribution, use Windows Explorer to navigate to the directory containing the distribution, and double-click on the distribution_name
.exe
file.
During an Oracle Fusion Middleware installation, you will be asked whether or not you want to configure your system to automatically check for security updates on the Specify Security Updates screen. If you choose to do so, Oracle Configuration Manager is installed and configured through the product installer.
If Oracle Configuration Manager is not configured from the installer (Specify Security Updates screen), then you can manually configure Oracle Configuration Manager after an Oracle Fusion Middleware installation. You can run the following command from the ORACLE_HOME
/oracle_common/ccr/bin
directory (on UNIX operating systems) or from the ORACLE_HOME
\oracle_common\ccr\bin
directory (on Windows operating systems) to set up and configure Oracle Configuration Manager:
On UNIX operating systems:
configCCR -a
On Windows operating systems:
setupCCR.exe -a
For more information, refer to "Installing Oracle Configuration Manager" in the Oracle Configuration Manager Installation and Administration Guide.