Skip Headers
Oracle® Enterprise Manager Installation and Basic Configuration
10g Release 2 (10.2) for Linux x86

Part Number B16228-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page

Go to previous page
Go to next page
View PDF

F Additional Parameters for Agent Deploy

The additional parameters that you specify during the agent installation using Agent deploy depend on the source software location that you have selected.

Figure F-1 Additional Parameters Section of the Installation Details Page

The Additional Parameters section.

If you select the default software source location, you must specify additional parameters that are supported by the agent Down Load script. See Table F-1 for a list of parameters supported by this script.

If you select an alternative location, you must specify additional parameters that are supported by Oracle Universal Installer (OUI). See Table F-2 for a list of parameters supported by OUI.


If the same parameters that you specify here are also specified independently (from the command-line option), the value of the parameters that you specify here take precedence over the other.

For example, if the installation base directory is specified independently, and -b option is specified here, the latter value (-b) is used in the installation.

Additional Parameters Supported by agentDownload Script

The following table lists the possible parameters that you can specify if you select the default (Management Service) location:

Table F-1 Parameters Supported by agentDownload Script

Parameters Description


Do not start the agent after installation/upgrade. No value required.


Cluster node list. Used during installation only. Nodes should be specified in double-quotes, separated by commas. For example, -c "node1,node2,node3"


Installation base directory location. For example, -b /home/OracleHomes/agent/


Do not initiate automatic target discovery. No value required.


Inventory pointer location file, for example, -i/etc/oraInst.loc


Cluster name, for example, -n CLUSTER1


File location for static port for agent. For example, -p /home/config/staticports.ini

The template file for the -p option is given below:

# staticports.ini Template File
# This file is a template for specifying port numbers at installation time.
# To specify a port number, uncomment the appropriate line (remove #) and
# replace "port_num" with the desired port number.
# You can then launch Oracle Universal Installer with special options to use this file.
# Please refer to Enterprise Manager Grid Control 10gR2 Installation Guide for instructions.
# Enterprise Manager
#Enterprise Manager Central Agent Port=port_num


Specify the timezone environment variable value (-z <timezone>). For example, -z PST8PDT.


If you use the -z option to specify the timezone, but the Agent Deploy application discovers a TZ environment variable already set on the remote host, this TZ value will take precedence over the -z value that you specify.

You can verify whether the TZ environment variable has been set on the remote host by executing the following command:

ssh -l <user_name> -n <remote_node> 'echo $TZ'

where, <user name > is the ID that you are using for the agent installation, and <remote host> is the host on which you want to install the agent.

If you are installing the agent from a non-default software location, you must specify the timezone environment variable using the following command:

For example, s_timezone=PST8PDT

Additional Parameters Supported by Oracle Universal Installer

The following table lists the possible parameters that you can specify if you select an alternative software source (non-default) location:

Table F-2 Parameters Supported by Oracle Universal Installer

Parameter Description

-clusterware, <crs version>

Version of the installed Oracle Clusterware.

-crslocation <path>

Used only for cluster installs, specifies the path to the CRS home location. Specifying this overrides CRS information obtained from the central inventory.

-invPtrLoc <full path of oraInst.loc>

Linux only. To point to a different inventory location. The orainst.loc file contains:

inventory_loc=<location of central inventory>
inst_group=<group of the user that is installing the agent>

-jreLoc <location>

Path where the Java Runtime Environment is installed. OUI cannot be run without this.

-logLevel <level>

To filter log messages that have a lesser priority level than <level>. Valid options are: severe, warning, info, config, fine, finer, finest, basic, general, detailed, trace. The use of basic, general, detailed, and trace is deprecated.

-paramFile <location of file

Specify location of oraparam.ini file to be used by the Oracle Universal Installer.

-responseFile <Path>

Specifies the response file and path to use.

-sourceLoc <location of products.xml>

Specifies the software source location.


Indicates that the Oracle home specified is on the cluster file system (shared). This is mandatory when '-local' is specified so that the Oracle Universal Installer can register the home appropriately into the inventory.


Gets the debug information from OUI.


Executes system pre-requisite checks and exits.


Allows silent mode installation into a non-empty directory.


Displays the usage of all the above options.


Ignores the results of the system pre-requisite checks.


Performs the operation on the local node irrespective of the cluster nodes specified.


Logs debug information for memory usage.


Logs debug information for time usage.


Updates the node list for this home in the OUI inventory.

Command Line Variable Usage During Silent Installation

The command line variables are specified using the <name=value> format.

For example,
[ session: | compName: | compName:version: ]variableName=" valueOfVariable"]

Session/Installer variables are specified using the [session:]varName=value format.

For example:


The lookup order is session:varName, and then just the varName. The session prefix is used to avoid ambiguity.

Component variables are specified using [compInternalName:[Version:]]varName

For example:


The lookup order is compInternalName:Version:varName, the compInternalName:varName, and then just the varName.

See Chapter4, "Silent Installation of an Additional Management Agent" for more information.