Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 3 (10.2.0.3.0) Part Number B40103-01 |
|
|
View PDF |
The additional parameters that you specify during the agent installation using the Agent Deploy application depend on the software source location that you have selected.
If you select the default source software location, you must specify additional parameters that are supported by the agent Down Load
script. See Table D-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 D-2 for a list of parameters supported by OUI.
Note:
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.
Table D-1 lists the possible parameters that you can specify if you select the default (Management Service) location.
Table D-1 Parameters Supported by agentDownload Script
Parameters | Description |
---|---|
-t |
No value required. Do not start the agent after installation or upgrade. |
-c |
Cluster node list. Used during installation only. Nodes should be specified in double-quotation marks, separated by commas. For example, |
-b |
Installation base directory location. For example, - |
-d |
No value required. Do not initiate automatic target discovery. |
-i |
Inventory pointer location file. For example, |
-n |
Cluster name. For example, |
-p |
File location for static port for agent. For example, The template file for the # 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 |
-z |
Timezone environment variable value ( |
Note:
Use the-z
option to specify the time zone, 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 if 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'
The <user name>
argument 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 nondefault software location, you must specify the timezone environment variable using the following command:
s_timeZone=<timezone> For example, s_timezone=PST8PDT
Table D-2 lists the possible parameters that you can specify if you select an alternative software source (nondefault) location:
Table D-2 Parameters Supported by Oracle Universal Installer
Parameter | Description |
---|---|
-clusterware oracle.crs, <crs version> |
Version of the installed Oracle Clusterware. |
-crslocation <path> |
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 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> |
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> |
Location of |
-responseFile <Path> |
Response file and path to use. |
-sourceLoc <location of products.xml> |
Software source location. |
-cfs |
Oracle home specified is on the cluster file system (shared). This is mandatory when ' |
-debug |
Get debug information from OUI. |
-executeSysPrereqs |
Execute system prerequisite checks and exits. |
-force |
Allow silent mode installation into a non-empty directory. |
-help |
Display the usage of all preceding options. |
-ignoreSysPrereqs |
Ignore the results of the system prerequisite checks. |
-local |
Perform the operation on the local node irrespective of the cluster nodes specified. |
-printmemory |
Log debug information for memory usage. |
-printtime |
Log debug information for time usage. |
-updateNodeList |
Update the node list for this home in the OUI inventory. |
The command-line variables are specified using the <name=value>
format.
For example, [ session: | compName: | compName:version: ]variableName=" valueOfVariable"]
Session or installer variables are specified using the [session:]varName=value
format.
For example: session:ORACLE_HOME_NAME="OraHome" ORACLE_HOME_NAME="OraHome"
Note:
The lookup order issession:varName
, and then just the varName
. The session prefix is used to avoid ambiguity.Component variables are specified using [compInternalName:[Version:]]varName
For example: oracle.comp1:1.0.1:varName="VarValue" oracle.comp1:varName="VarValue"
Note:
The lookup order iscompInternalName:Version:varName
, the compInternalName:varName
, and then just the varName
.See Chapter4, "Silent Installation of an Additional Management Agent" for more information.