I Reconfiguring Oracle Management Agent and Discovering New Targets

This appendix describes the commands you must run to reconfigure Oracle Management Agent and discover new targets that were installed after the installation of the Management Agent.

In particular, this appendix covers the following:

Note:

The -t argument mentioned in the commands of this appendix indicate that you do not want the Management Agent to start after the operation (reconfiguration or discovery) ends.

Discovering New Targets with Standalone Management Agents

By default, the targets that were already installed on the host before installing the Management Agent are automatically discovered in Enterprise Manager Grid Control. However, the new targets installed after installing the Management Agent are not automatically discovered.

Therefore, if you install any new target, and if you want to discover and monitor it in Enterprise Manager Grid Control, run the following command from the Oracle home of the Management Agent that is installed on the host:

$<ORACLE_HOME>/bin/agentca -d [ -t -i <absolute_path_to_oraInst.loc_file>]

Converting Standalone Management Agents to Cluster-Based Management Agents

After installing standalone Management Agents on multiple hosts, if you create a cluster of those hosts, you must ideally convert those standalone Management Agents to cluster-compatible Management Agents. This section describes how you can convert in graphical and silent mode.

Convering in Graphical Mode

To convert a standalone Management Agent to a cluster-compatible Management Agent in a graphical mode, follow these steps:

  1. In Grid Control, click Deployments.

  2. On the Deployments page, from the Agent Installation section, click Install Agent.

  3. On the following page, click Fresh Install.

  4. 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.

    Note:

    If you see the following error messages on the Prerequisite Details page, ignore them and click Continue to proceed with the installation: 
    Some or all Agent home locations(Install base dir/agent10g or Install Base Dir/agent11g) provided are not empty directories

The Agent Oracle Home ( InstallBaseDir/agent10g or InstallBaseDir/agent11g), is already registered with the inventory

An agent home exists in the hosts

Converting in Silent Mode

To convert a standalone Management Agent to a cluster-compatible Management Agent in a silent mode, follow these steps:

$<ORACLE_HOME>/bin/agentca -f -c "{<comma_separated_cluster_node_list>}" [ -t -i <absolute_path_to_oraInst.loc_file> -n <cluster_name>]

Discovering New Targets with Cluster-Based Management Agents

By default, the targets that were already installed on the nodes of a cluster before converting a standalone Management Agent to a cluster-compatible Management Agent are automatically discovered in Enterprise Manager Grid Control. However, the new targets installed on a node after converting a standalone Management Agent to a cluster-compatible Management Agent are not automatically discovered.

Therefore, if you install any new target on a node of a cluster, and if you want to discover and monitor it in Enterprise Manager Grid Control, run the following command from the Oracle home of the Management Agent on that node:

$<ORACLE_HOME>/bin/agentca -d -c "{<comma_separated_cluster_node_list>}" [ -t -i <absolute_path_to_oraInst.loc_file> -n <cluster_name>]

Reconfiguring Cluster-Based Management Agents

If you add new nodes to an existing cluster, you must reconfigure the cluster-based Management Agent to update the centry inventory with the information of those new nodes, and discover all the targets installed on those new nodes. To do so, run the following command from the Oracle home of the Management Agent on every node of the cluster:

$<ORACLE_HOME>/bin/agentca -f -c "{<comma_separated_cluster_node_list_including_new_nodes>}" [ -t -i <absolute_path_to_oraInst.loc_file> -n <Cluster_Name>]

Note:

When the agentca script runs, it takes a backup of the EMSTATE directory on the local node, and creates a new EMSTATE directory.