Skip Headers
Oracle® Enterprise Manager Grid Control Advanced Installation and Configuration Guide
11g Release 1 (11.1.0.1.0)

E16847-15
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

17 Cloning Oracle Management Agent on Clusters Using ZIP File

This chapter explains how you can clone an existing Oracle Management Agent 11g Release 1 (11.1.0.1.0) to additional nodes of a cluster using a ZIP file. In particular, this chapter covers the following:

Note:

If you have a cluster-based environment, then Oracle strongly recommends you to install the Management Agent using the Agent Deployment Wizard as described in Chapter 9, "Installing Oracle Management Agent on a Cluster Using Agent Deployment Wizard".

Overview

The Management Agents installed on the nodes of a cluster are different from the Management Agents installed on standalone hosts. While the Management Agent installed on a standalone host is called a standalone Management Agent, the Management Agent installed on a node of the cluster is called a cluster-based Management Agent.

You can install a cluster-based Management Agent on a cluster using the compressed format (ZIP) of an existing Management Agent.

Before You Begin

Before you begin, keep in mind the points described in Before You Begin.

Prerequisites

Before you clone a Management Agent, ensure that you meet the prerequisites described in Prerequisites.

Cloning Procedure

To clone a Management Agent on a cluster, follow these steps:

  1. Use the ZIP utility to zip the Oracle home of the Management Agent you want to clone. For example, agent.zip

  2. Use a file transfer utility (for example, FTP) to transfer the ZIP file to the destination host. For example, ftp agent.zip

  3. On each of the target nodes of the cluster, extract the contents of the ZIP file. Oracle recommends that you maintain the same installation location on all the nodes of the cluster.

  4. On each of the target nodes, navigate to $<ORACLE_HOME>/oui/bin/ directory and run the following command:

    • If you are cloning a Management Agent that was installed along with an OMS, then run the following command:

      ./runInstaller -clone -forceClone ORACLE_HOME=<full path of Oracle home> ORACLE_HOME_NAME=<Oracle home name> -noconfig -silent b_chainedInstall=false oracle.sysman.top.agent:s_installType=AGENT OMS_HOST=<oms_host> OMS_PORT=<oms_port>

      For Microsoft Windows platforms, run the setup.exe file.

    • If you are cloning a Management Agent that was installed as a standalone Management Agent, then run the following command:

      ./runInstaller -clone -forceClone ORACLE_HOME=<full path of Oracle home> ORACLE_HOME_NAME=<Oracle home name> -noconfig -silent OMS_HOST=<oms_host> OMS_PORT=<oms_port>

      For Microsoft Windows platforms, run the setup.exe file.

  5. On each of the target nodes, configure the Management Agents by running the following script:

    $<ORACLE_HOME>/bin/agentca -f -c "node1, node2, node3...."

Note:

If the installation fails, then review the log files described in Appendix L, "Installation and Configuration Log Files".

After You Clone

After you clone, follow the steps described in After You Install.