Oracle® Universal Installer and OPatch User's Guide 11g Release 2 (11.2) for Windows and UNIX Part Number E12255-05 |
|
|
View PDF |
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:
This section answers the following questions:
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.
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.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 theoraInstRoot.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. Note that 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.
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:
Make a copy of the product's response file and open it in a text editor.
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.
Get familiar with the organization and content of the response file using the information in the section "Response File Format".
Modify the response file to meet the needs of your organization and save the modified version.
See the section "Installing with a Response File" for information on starting Oracle Universal Installer using your modified response file.
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.
The following sections describe the organization and content of an Oracle Universal Installer response file.
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 theoraparam.ini
file is present.This section contains information on how variables are populated with values.
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.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.
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.
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"}
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>
The following are parameters for Oracle Universal Installer. All products installed using Oracle Universal Installer have these parameters in addition to product-specific variables.
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
.
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}"
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.
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"}
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:
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
file oraparam.ini
. 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.
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.
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).
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 forINSTALL_TYPE
.This parameter specifies the current node on which the installation occurs.
LOCAL_NODE={}
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:
Oracle Universal Installer looks for the Location_For_Disk{DiskNumber}
variable in the response file and uses that location.
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
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
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
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"
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.
This parameter indicates the My Oracle Support username/email 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 email 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 email 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.
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:
TheOPTIONAL_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"}
The location of the Oracle Base where all Oracle software and configuration-related files are stored.
The location where products are to be installed. You must enter a value for ORACLE_HOME for a complete silent installation.
This proxy connection server is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.
This proxy connection port is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.
This proxy connection password is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.
This proxy connection user name is used only if the direct connection is not available and DECLINE_SECURITY_UPDATES=false.
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}"
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"}
This parameter specifies the version number of the response file.
RESPONSEFILE_VERSION = <version_number>
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.
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.
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 "Product Language Selections".
Note:
TheSELECTED_LANGUAGES
variable is only generated when more than one language is available.The location page, which appears in a custom installation type, can be suppressed by setting this value to FALSE
. If you set the value to FALSE
, the user is prevented from specifying alternate directories. If there are products with installed directories which can be changed, you may want to set the value to TRUE
.
Set SHOW_CUSTOM_TREE_PAGE
to TRUE
if the custom tree page in the installer must be shown. In the Custom Tree page, dependencies can be selected or deselected. This page appears only in a custom installation type.
Set this parameter to FALSE
if you want to hide the deinstall confirmation dialog box during a silent deinstallation.
Set this parameter to FALSE
if you want to hide the deinstallation progress dialog box during a silent deinstallation.
The DEPENDENCY_LIST
variable is only generated when dependencies are present and if the dependency is not a required one.
You cannot list components to appear as deselected items in a dialog.
Specifying required dependents is redundant since they will be selected anyway. The dependents selection can have the other two types of dependents: optional and one-or-more.
The list of components is specified by an internal name and version number.
A typical example is listed here:
DEPENDENCY_LIST={"oracle.netclt","9.2.0.4.0","oracle.netmgr","9.2.0.4.0"}
The installation success/failure page, which appears at the end of an installation, can be suppressed by setting this value to FALSE
.
Set to TRUE
if you need to show the confirmation when exiting the installer.
SHOW_EXIT_CONFIRMATION = TRUE
The installation progress page, which appears during the installation phase, can be suppressed by setting the value to FALSE
.
Set to TRUE
if you must show the Optional Configuration Tools page in the installer. The Optional Configuration Tools page shows the list of optional configuration tools that are part of this installation and the status of each tool, including detailed information on why the tool has failed.
Set this parameter to TRUE
if you want the release notes for this installation to be shown at the end of the installation. A dialog box lists the available release notes. Note that the SHOW_END_SESSION
parameter must be set to TRUE
before you can use this parameter.
Set to TRUE
if you need to show the Confirmation dialog asking to run the root.sh
script in the installer. This variable is valid only on UNIX platforms.
SHOW_ROOTSH_CONFIRMATION = TRUE
Set to TRUE
if the initial splash screen in the installer needs to be shown.
SHOW_SPLASH_SCREEN = TRUE
The Summary page can be suppressed by setting this value to FALSE
.
Set to TRUE
if you need to show the Welcome page in the installer.
SHOW_WELCOME_PAGE = FALSE
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"}
.
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.
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 scriptoraInstRoot.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 "Oracle Universal Installer Inventory" for more information on the Central Inventory.
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) ./runInstaller -responseFile <filename> <optional_parameters> (on UNIX)
Note:
You must specify the completeresponseFile
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) ./runInstaller -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.
Optional parameters you can use with the -responseFile
flag are:
-nowelcome — Use the -nowelcome
flag with the -responseFile
flag to suppress the Welcome dialog that appears during installation.
-silent — Use the -silent
flag with the -responseFile
flag to run Oracle Universal Installer in complete silent mode. Note that the Welcome dialog is suppressed automatically.
-formCluster — Use the -formCluster
flag for Oracle Clusterware installations to specify the cluster.
Note that when you specify the -silent
flag, 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 flag 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.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.
To specify the value of a session variable, use the following command syntax:
./runInstaller session:<variable_name>=<value> (on UNIX) setup.exe session:<variable_name>=<value> (on Windows)
For example, to prevent the Universal Welcome page from displaying:
./runInstaller session:SHOW_WELCOME_PAGE=false (on UNIX) setup.exe session:SHOW_WELCOME_PAGE=false (on Windows)
Note that the "session:" tag is optional and is used mainly to remove any possible ambiguity.
To specify the value of a component variable, use the following command syntax:
./runInstaller <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
:
./runInstaller 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.