For information on how to run the Oracle Universal Installer from the command line, see the following topics:
Silent installation eliminates the need to monitor your product installation because no graphical output is displayed and no input by the user is required.
Silent installation of your Oracle Fusion Middleware product is accomplished by using the -silent
flag on the command line when you start the installer. In most cases, you will need to supply the location and name of a file containing certain input values (for example, installation location). These are the values that would be asked for during a typical installation using the graphical user interface.
For Oracle Fusion Middleware products, this file is called a response file. For more information, see About Response Files.
Note that silent installation doesn’t include configuration. That is, you can’t configure your product silently using the same silent installation commands and response file. Configuration is a separate process, unlike in Oracle Fusion Middleware 11g. Refer to the installation guide for your product for complete information about configuring your product.
Note:
For UNIX users, if this is a first time installation of any Oracle product, you must create the oraInst.loc
file before starting. Refer to UNIX Users: Creating the Central Inventory for more information.
Following installation of your product, you need to run the root.sh
script as the root
user. The root.sh
script detects settings of environment variables and enables you to enter the full path of the local bin
directory.
Before doing a silent installation, you must provide information specific to your installation in a response file (for example, the installation directory). The installer will fail if you attempt an installation using a response file that is not configured correctly.
Response files are text files that you can create or edit in a text editor.
Oracle recommends using your product’s graphical installer or deinstaller to create a response file that you can use to silently install or deinstall your product.
The provided sample response files show you the parameters that can be included in a response file for a silent installation or deinstallation.
To see some sample response files that can be used for silent installation, see Sample Response Files for Silent Installation and Deinstallation.
The parameters that can be included in the response files are described in Oracle Universal Installer Response File Parameters.
These parameters can be included in a valid response file for the Oracle Universal Installer.
See Sample Response Files for Silent Installation and Deinstallation for some sample response files.
Table 2-1 Oracle Universal Installer Response File Parameters
Corresponding Screen | Parameter | Description |
---|---|---|
|
Set this parameter to |
|
|
Provide your My Oracle Support user name and password if you want the installer to automatically search My Oracle Support for software updates that apply to the software products you are about to install. |
|
|
Enter the path for the local directory where your updates are located. Use this parameter if you already downloaded the latest software updates and you want the installer to search a local directory for updates applicable to the products you are about to install. |
|
SOFTWARE_UPDATES_PROXY_PASSWORD |
Provide the proxy server information if a proxy server is required for connections to the Internet and for accessing My Oracle Support. |
|
|
Location of the Oracle home directory. |
|
|
Provide your My Oracle Support user name and password if you want to receive the latest product information and security updates. |
|
|
Set this parameter to |
|
|
If you specify values for |
|
|
Provide the proxy server information if you use a proxy server in your environment. |
|
|
The URL of the Oracle Configuration Manager Repeater. The format is: http://repeater_host:repeater_port or https://repeater_host:repeater_port |
|
|
Specify the type of install you want to perform. This value will differ depending on your product distribution. For example, for the Fusion Middleware Infrastructure distribution, the following install types are valid:
|
Your response files contain certain passwords required by the installer. Follow these guidelines to minimize security issues regarding these passwords in the response file.
Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent installation.
If possible, remove the response files from the system after the silent installation is completed.
Follow these instructions to run the Oracle Universal Installer in silent mode and to set up your Oracle central inventory for the first time.
To run the product installer from the command line, make sure you understand the syntax and various command line options you can use for your installation.
The full syntax for running the product installer from the command line is shown below:
java -jar distribution_name.jar [-options] [(<CommandLinevariable=Value>)*]
To run the product installer in silent mode, use -silent
mode and specify a response file:
java -jar distribution_name.jar -silent -responseFile file [-options] [(<CommandLinevariable=Value>)*]
The following table lists the valid command line options for silent installation and graphical installation.
Table 2-2 Installer Command Line Options for Silent Installation and Graphical Installation
Option | Description |
---|---|
|
Launches the installer. This is the default operation. Only one operation can be specified. |
|
Performs the designated operation (such as |
|
Displays the usage options for the installer. |
|
UNIX only - pointer to the central inventory location file. Replace file with the full path and name of the |
|
Pointer to the response file. Replace file with the full path and name of the response file. See About Response Files for information about creating the response files. |
|
Specify the level of logging performed by the installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:
|
|
Obtain debug information from the installer. |
|
Log debugging information pertaining to disk usage. |
|
Log debugging information pertaining to memory usage. |
|
Log debugging information pertaining to time usage. |
|
Messages will not be displayed to the console window. |
|
Ignore the results of the system prerequisite checks and continue with the installation. |
|
Execute the system prerequisite checks only, then exit. |
|
The The |
|
Location of the file that specifies feature set dependency changes. |
|
Windows only - the installer does not wait for the user to press Enter on the console after the operation (such as |
Installer Variables |
Installer variables are specified using |
The first time you run the installer in silent mode on your UNIX operating system, you will need to create a central inventory directory.
As a result, you will see a prompt similar to the following example:
You are starting your first installation on this host or you do not have sufficient permission to access current inventory. As part of this install, you need to specify a directory for installer files. This is called the "inventory directory". Within the inventory directory, the installer automatically sets up subdirectories for each product to contain inventory data and will consume typically 150 Kilobytes per product. It is recommended that this file (oraInst.loc) be created in /etc directory. You need root privileges to do so. You can exit the installer and run the script located in /tmp/createCentralInventory1371119669507.sh to set up the central inventory location.
Follow the instructions described in the prompt to run the /tmp/createCentralInventory.sh
script as root
to create the oraInst.loc
file and your central inventory directory. This must be done before you can continue with your product installation. For more information, see Setting the Oracle Central Inventory Location Using Silent Installation on UNIX Operating Systems.
This example shows sample output from a silent Oracle WebLogic Server and Coherence installation.
java -jar fmw_12.2.1.2.0_wls_generic.jar -silent -responseFile /home/exampleuser/response/wls.rsp Launcher log file is /tmp/OraInstall2016-06-30_07-32-16AM/launcher2016-06-30_07-32-16AM.log Extracting the installer................... Done Checking if CPU speed is above 300 MHz. Actual 2526.998 MHz Passed Checking swap space: must be greater than 512 MB. Actual 10288440 MB Passed Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required) Checking temp space: must be greater than 300 MB. Actual 44752 MB Passed Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2016-06-30_07-32-16AM Log: /tmp/OraInstall2016-06-30_07-32-16AM/install2016-06-30_07-32-16AM.log Copyright (c) 1996, 2016, Oracle and/or its affiliates. All rights reserved. Reading response file.. Skipping Software Updates Starting check : CertifiedVersions Expected result: One of oracle-6,oracle-7,redhat-7,redhat-6,SuSE-11,SuSE-12 Actual Result: oracle-6.6 Check complete. The overall result of this check is: Passed CertifiedVersions Check: Success. Starting check : CheckJDKVersion Expected result: 1.8.0_101 Actual Result: 1.8.0_101 Check complete. The overall result of this check is: Passed CheckJDKVersion Check: Success. Validations are enabled for this session. Verifying data Copying Files Percent Complete : 10 Percent Complete : 20 Percent Complete : 30 Percent Complete : 40 Percent Complete : 50 Percent Complete : 60 Percent Complete : 70 Percent Complete : 80 Percent Complete : 90 Visit http://www.oracle.com/support/policies.html for Oracle Technical Support policies. Percent Complete : 100 The installation of Oracle Fusion Middleware 12c WebLogic Server and Coherence 12.2.1.2.0 completed successfully. Logs successfully copied to /home/exampleuser/oraInventory/logs.
Follow these instructions to run the Oracle Universal Installer to deinstall your Oracle Fusion Middleware products in silent mode.
To run the product deinstaller from the command line, make sure you understand the syntax and various command line options you can use for deinstallation.
To deinstall your Oracle Fusion Middleware product in silent mode, use the -silent
option from the command line.
The full syntax for running the deinstaller from the command line is shown below:
ORACLE_HOME/oui/bin/deinstall.sh -silent [-options] [(<CommandLinevariable=Value>)*]
The following table lists the valid command line options for silent deinstallation and graphical deinstallation.
Table 2-3 Deinstaller Command Line Options for Silent Deinstallation and Graphical Deinstallation
Options | Description |
---|---|
|
Displays the usage options for the deinstaller. |
|
Launches the deinstaller in GUI mode. This is the default mode and is used if no mode is specified on the command line. |
|
Specify the name of the distribution you want to remove from the Oracle home. This is necessary in the event that your Oracle home contains multiple distributions (for example, Oracle Fusion Middleware Infrastructure and Oracle SOA Suite). |
|
Specify the version of a particular distribution you want to remove from the Oracle home. This is necessary in the event that your Oracle home contains multiple distributions (for example, Oracle Fusion Middleware Infrastructure and Oracle SOA Suite). |
|
Pointer to the response file. Replace file with the full path and name of the response file. See About Response Files for information about creating the response files. |
|
Specify the level of logging performed by the installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:
|
|
Obtain debug information from the installer. |
|
Log debugging information pertaining to disk usage. |
|
Log debugging information pertaining to memory usage. |
|
Log debugging information pertaining to time usage. |
|
Messages will not be displayed to the console window. |
|
Ignore the results of the system prerequisite checks and continue with the installation. |
|
Execute the system prerequisite checks only, then exit. |
|
The The |
|
Windows only - the installer does not wait for the user to press Enter on the console after the operation (such as |
Installer Variables |
Installer variables are specified using |
These commands show how you can deinstall your product in silent mode.
Below is an example silent deinstall command:
ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/wls_deinstall.rsp
You can include the -logLevel
option to create a verbose installation log. See Summary of the Silent Deinstallation Syntax and Commands, for more details about this option.
Below is an example silent deinstall command specifying a response file and FINE
as the logging level.
ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/wls_deinstall.rsp -logLevel FINE
Below is an example silent deinstall command with multiple products in a single Oracle home:
ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/deinstall.rsp -distributionVersion 12.2.1.2.0 -distributionName "Oracle Data Integrator"
For silent deinstall, you have to specify -distributionName
and -distributionVersion
from command line in case multiple distributions are installed.
This example shows sample output from a silent Oracle WebLogic Server and Coherence deinstallation.
ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/wls_deinstall.rsp
Launcher log file is /tmp/OraInstall2016-06-30_07-50-01AM/launcher2016-06-30_07-50-01AM.log.
Checking if CPU speed is above 300 MHz. Actual 2526.998 MHz Passed
Checking swap space: must be greater than 512 MB. Actual 10288440 MB Passed
Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required)
Checking temp space: must be greater than 300 MB. Actual 44752 MB Passed
Log: /tmp/OraInstall2016-06-30_07-50-01AM/deinstall2016-06-30_07-50-01AM.log
Setting ORACLE_HOME to /home/Oracle/products/Oracle_Home
Copyright (c) 1996, 2016, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Starting silent deinstallation...
Percent Complete : 10
Percent Complete : 20
Percent Complete : 30
Percent Complete : 40
Percent Complete : 50
Percent Complete : 60
Percent Complete : 70
Percent Complete : 80
Percent Complete : 90
100%
The uninstall of WebLogic Server 12.2.1.2.0 completed successfully.
Logs successfully copied to /home/exampleuser/oraInventory/logs.