Oracle® Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching 10g Release 5 (10.2.0.5.0) Part Number E14500-04 |
|
|
PDF · Mobi · ePub |
For using the RAC-related procedures, you must have cluster-compatible Oracle Management Agents (Management Agents) on the cluster nodes, and not standalone Management Agents. However, if the Management Agents on the cluster nodes are indeed standalone Management Agents, then you must convert them to cluster-compatible Management Agents.
This appendix explains how you can convert a standalone Management Agent to a cluster-compatible Management Agent. In particular, this chapter covers the following:
To convert a standalone Management Agent to a cluster-compatible Management Agent in a graphical mode, follow these steps:
Meet the prerequisites for installing a Management Agent as described in the Oracle Enterprise Manager Grid Control Installation and Configuration Guide available at:
In Grid Control, click Deployments.
On the Deployments page, from the Agent Installation section, click Install Agent.
On the following page, click Fresh Install.
On the Installation Details page, do the following:
In the Source Software section, retain the default selection, that is, Default, from Management Server location.
In the Version section, select the appropriate version of the already-installed standalone Management Agents. Note that to use Deployment Procedures, the Management Agents must be at least 10g Release 2 (10.2.0.2).
In the Host section, select the required platform, provide a list of hosts that are part of the cluster, check Cluster Install, click Populate Defaults to automatically specify a list of cluster nodes, and then specify a cluster name.
In the OS Credentials section, provide the host credentials.
In the Destination section, specify the installation base directory on the nodes that form the cluster.
In the Additional Parameters section, supply any other optional parameters you want to run.
Click Continue.
To convert a standalone Management Agent to a cluster-compatible Management Agent in a silent mode, follow these steps:
Invoke the agentca utility using the -f and -c option from the <Agent Oracle home>/bin directory of the standalone Management Agent on each cluster node. Also use the -n option to specify the name of the cluster.
For example:
<Agent Oracle Home>/bin/agentca -f -n <cluster name> -c "{<comma separated cluster node list like node1, node 2…>}"
Update the node list by running the following command:
In case SSH connection is set up between the cluster nodes, then run the following command from <Agent Oracle Home>/oui/bin directory on one of the nodes:
./runInstaller -updateNodelist ORACLE_HOME=<Agent Oracle Home> "CLUSTER_NODES={<comma separated list of nodes in the cluster>}"
In case SSH connection is not setup between the nodes then run the following command from <Agent Oracle Home>/oui/bin directory on each node:
./runInstaller -updateNodelist ORACLE_HOME=< Agent Oracle Home > "CLUSTER_NODES={< comma separated list of nodes in the cluster >}" -local
Resynchronize the Management Agent by following these steps:
In Grid Control, click Targets, and then All Targets.
On the All Targets page, from the Search list, select Agent and click Go.
Click the name of the Management Agent you clusterized.
On the Agent Home page, from the Related Links section, click Agent Resynchronization.
On the Agent Resynchronization page, click Continue.