| Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 2 (10.2) B16228-05 |
|
 Previous |
 Next |
| Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 2 (10.2) B16228-05 |
|
Previous |
Next |
In Enterprise Manager Grid Control 10g Release 2 (10.2.0.2), the agent installation is supported both on Oracle Clusterware as well as 9.2 clusters. The Management Agent can be installed as a standalone agent on each node of a cluster individually, or can be installed on multiple nodes in one single installation by choosing the cluster option.
|
Caution: The agent Oracle home cannot be installed in an Oracle Cluster Shared File System (OCFS) drive, but is supported on a NAS (Network Attached Storage) drive. |
You can choose to either install a standalone agent on each node individually, or perform a cluster installation of the agent. The following sections discuss the various deployment methods for both options.
You can perform a standalone agent installation using the following deployment methods:
The agent can be installed by executing the agentDownload script on one node at a time using the correct arguments. If you want to discover the cluster targets, then you must set the CLUSTER_NAME environment variable prior to executing the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -n <clustername>.
agentDownload -b <Oracle Base Directory location> -n <clustername>
|
Note: If theCLUSTER_NAME environment variable is not set, the agent cannot discover any cluster targets. |
To perform a standalone agent installation on a cluster node, you must select the appropriate node of that cluster. If you want to discover the cluster targets, you must specify the correct cluster name in the Cluster Name text box. See Chapter6, "Fresh Installation of the Management Agent" for detailed instructions.
|
Note: Ensure the nodes that you select for the agent installation are part of the cluster that you have specified in the Cluster Name text box. Otherwise, the targets are not discovered. |
You can perform this installation by invoking the installer using Oracle Universal Installer (OUI). The Interactive type is typically a one-node installation.
If the agent is installed as a standalone agent on a release 9.2 cluster, then you can set the CLUSTER_NAME environment variable to the name of the cluster that you want to use for the cluster targets before invoking the runInstaller script. If this variable is not set, the agent cannot discover any cluster targets.
You can perform a cluster agent installation using the following deployment methods:
You can perform a cluster agent installation through this script by using the -c option (for example, -c "node1,node2,..."). This option helps install the cluster agent on all the nodes that you specify here.
If you want to override the cluster name that appears in targets.xml, then you must set the CLUSTER_NAME environment variable prior to executing the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -b <Oracle Base Directory location> -n <clustername> -c "node1,node2,node3".
To perform a cluster agent installation using the Agent Deploy application, you must select the Cluster Install option and specify all the nodes of that cluster. If you want to discover the cluster targets, you must specify the correct cluster name in the Cluster Name text box. See Chapter6, "Fresh Installation of the Management Agent" for detailed instructions.
To install an agent on a release 9.2 cluster that is on multiple nodes at a time, you must pass the CLUSTER_NODES variable when starting executing the runinstaller script as:
./runInstaller CLUSTER_NODES="{node1,node2}"
If the CLUSTER_NODES variable is not passed, the installer cannot detect the nodes and cannot perform the cluster install.
If you want to set the cluster name that appears in the targets.xml file, you must set the CLUSTER_NAME environment variable before invoking the runInstaller. If this variable is not set, the agent uses the first node as the cluster name.
You can choose to either install a standalone agent on each Oracle Clusterware node individually, or perform a cluster installation of the agent. The following sections discuss the various deployment methods for both options.
You can perform a standalone agent installation on Oracle Clusterware using the following deployment methods:
The agent can be installed by executing the agentDownload script on one node at a time using the correct arguments. If you want to override the cluster name to be used in targets.xml file, you must set the CLUSTER_NAME environment variable prior to executing the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -n <clustername>.
agentDownload -b <Oracle Base Directory location> -n <clustername>
|
Note: If theCLUSTER_NAME environment variable is not set or passed, the agent uses the cluster name that was specified during the Oracle Clusterware installation. |
To perform a standalone agent installation on a cluster node, you must select the Cluster Install option, and specify the appropriate cluster node names. The cluster name that you specify here overrides the corresponding value in the targets.xml file. See Chapter6, "Fresh Installation of the Management Agent" for detailed instructions.
You can perform this installation by invoking the installer using Oracle Universal Installer (OUI).
If you want to set the cluster name that will appear in targets.xml file, then you must set the CLUSTER_NAME environment variable before invoking the runInstaller. If this variable is not set, the agent uses the cluster name that was specified during the Oracle Clusterware installation.
You can perform a cluster agent installation using the following deployment methods:
You can perform a cluster agent installation through this script by using the -c option (for example, -c "node1,node2,..."). This option helps install the cluster agent on all the nodes that you specify here.
If you want to override the cluster name that appears in targets.xml file, then you must set the CLUSTER_NAME environment variable prior to executing the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -b <Oracle Base Directory location> -n <clustername> -c "node1,node2,node3".
|
Note: If theCLUSTER_NAME variable is not set or passed, the agent uses the cluster name that was specified during the Oracle Clusterware installation. |
To perform a cluster agent installation using the Agent Deploy application, you must select the Cluster Install option and specify all the nodes of that cluster. If you want to override the cluster name that appears in targets.xml file, you must specify the appropriate cluster name in the application. See Chapter6, "Fresh Installation of the Management Agent" for detailed instructions.
When you execute the runInstaller script, it automatically detects all the cluster nodes. You can then choose the nodes on which you want to perform the cluster agent installation.
If you want to override the Cluster name that appears in targets.xml, you must set the CLUSTER_NAME environment variable before invoking the runInstaller. If this variable is not set, the agent uses the cluster name that was specified during the Oracle Clusterware installation.
When you are performing an Oracle RAC agent installation on the Microsoft Windows platform, only the host and cluster targets will be discovered during the installation.
To discover all other targets, you must execute the following on each node of that cluster:
Agent Home>/bin/agentca -d -n <Cluster Name> -c <node name>
