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

14 Installing Oracle Management Agent on a Cluster Using Response File or agentDownload Script

This chapter describes how you can install Oracle Management Agent (Management Agent) on a cluster using either the response file (additional_agent.rsp) or the agentDownload script. 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 either the response file, that is, additional_agent.rsp, or the agentDownload script.

The following are the use cases that are supported:

Use Case Description Your Requirement
Installing a Management Agent on All the Nodes of a Cluster You might have a cluster containing many nodes, and none of the nodes might have a Management Agent installed.

For example, let's say you have a cluster crs1 with nodes n1, n2, n3, n4, and n5, and none of the nodes have a Management Agent installed.

You want to install a Management Agent on each of the nodes.
Installing a Management Agent Only on Some Nodes of a Cluster You might have a cluster containing many nodes, and only a few of the nodes might have a Management Agent installed.

For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. Let's assume that a Management Agent is installed only on n1 and n2.

You want to install a Management Agent on some of the nodes, not all, though.
Installing a Management Agent on Additional Nodes that Extends the Cluster You might have a cluster containing some nodes, and you might extend the cluster by adding one or more new nodes to it.

For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. Let's assume that a Management Agent is installed on each of the nodes. You now introduce two new nodes n6 and n7 to the cluster.

You want to install a Management Agent on the additional nodes that extend the cluster.
Installing a Management Agent on Two Clusters of the Same Name, but with Different Nodes You might have two clusters with the same name, but each cluster having different nodes.

For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. Let's say you have another cluster named crs2 with nodes n6, n7, n8, n9, and n10.

You want to install a Management Agent on the nodes of each of the clusters.

Before You Begin

Before you begin, keep in mind the following points:

  • You CANNOT use addnode.sh script to extend Management Agents to a cluster.

  • If the CLUSTER_NAME environment variable is not set or passed, the Management Agent uses the cluster name that was specified during the Oracle Clusterware installation.

  • The installation is done only on those cluster nodes that you specify, regardless of the number of hosts that make up that cluster.

Prerequisites

Before installing the Management Agent, ensure that you meet the following prerequisites:

  • If you are installing using the response file, then meet the prerequisites described in Prerequisites.

  • If you are installing using the agentDownload script, then meet the prerequisites described in Prerequisites.

Installation Procedure

This section describes the installation procedures for installing a Management Agent on a cluster using either the response file, that is, additional_agent.rsp, or the agentDownload script. In particular, this section covers the following:

Installing Using Response File

To install a Management Agent using the response file, follow these steps:

  1. Navigate to the location where the Management Agent software is available.

    For example, oms11g/sysman/agent_download/11.1.0.1.0/linux if the Management Agent software is available in the Oracle home of the OMS.

    Alternatively, /private/temp/11.1.0.1.0/linux if you have downloaded the Management Agent software to /private/temp on your local system.

  2. Compress the files from the <platform> directory using the WinZIP utility, and transfer the compressed file to the node where you want to install the Management Agent. For example, linux.zip.

    Note:

    If you are installing on one of the new nodes that are extending the cluster, then transfer the ZIP file to one of the new nodes.
  3. On the node where you want to install the Management Agent, do the following:

    1. Extract the contents of the compressed file you just transferred.

    2. Navigate to the following location and edit the additional_agent.rsp file as described in Table 14-1.

      <Software_Extracted_Location>/<platform>/response/ additional_agent.rsp

      For example:

      /scratch/john/linux/response/ additional_agent.rsp

    3. Navigate to the following location and invoke the installer:

      If this is the first Oracle product you are installing on the host, then run the following command:

      <Software_Extracted_Location>/<platform>/agent/runInstaller -silent -responseFile <absolute_path_to_location>/additional_agent.rsp [-invPtrLoc <absolute_path_to_inventory_directory>]

      For example,

      /scratch/john/linux/agent/runInstaller -silent -responseFile /scratch/john/linux/response/additional_agent.rsp -invPtrLoc /scratch/OracleHomes/oraInst.loc

      Otherwise, run the following command:

      <Software_Extracted_Location>/<platform>/agent/runInstaller -silent -responseFile <absolute_path_to_Location>/additional_agent.rsp

      For example,

      /scratch/john/linux/agent/runInstaller -silent -responseFile /scratch/john/linux/response/additional_agent.rsp


    Note:

    • For Microsoft Windows platforms, run setup.exe instead of runInstaller.

    • After the installation ends successfully, the Management Agent starts automatically. If you do not want it to start automatically, then invoke the installer with the b_startAgent=false argument.

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

  4. Update the node list of the cluster as described in Table 14-2.

Editing Parameters for Installing Oracle Management Agent on a Cluster

Table 14-1 shows the parameters you must edit in the additional_agent.rsp file for installing Management Agent on a cluster.

Table 14-1 Response File Parameters for Installing Oracle Management Agent on a Cluster

Parameter Description

SECURITY_UPDATES_VIA_MYORACLESUPPORT

  • Specify TRUE if you want to download and install security updates. Then, specify the credentials for the following parameters:

    MYORACLESUPPORT_USERNAME

    MYORACLESUPPORT_PASSWORD

  • Specify FALSE if you do not want to download and install security updates:

DECLINE_SECURITY_UPDATES

  • Specify TRUE if you want to decline the security updates. In this case, you should have specified False for SECURITY_UPDATES_VIA_MYORACLESUPPORT.

  • Specify FALSE if you do not want to decline the security updates. In this case, you should have specified TRUE for SECURITY_UPDATES_VIA_MYORACLESUPPORT.

ORACLE_AGENT_HOME_LOCATION

Specify the full path to the installation base directory where you want to install the Management Agent. The Oracle home of the Management Agent is created inside this installation base directory.

For example, if you specify the installation base directory as /home/john/, then the Oracle home is created as /home/john/agent11g.

For information about installation base directory, see What Is Installation Base Directory?.

Important: The installation base directory must be the same across the nodes of the cluster.

OMS_HOST

Specify the name of the host on which the OMS is running.

OMS_PORT

Specify the port used by the OMS.

AGENT_REGISTRATION_PASSWORD

To secure the communication between the OMS andthe Management Agents, specify a password. Note that you have to provide the same registration password for securing your Management Agents.

CLUSTER_NODES

Specify the nodes of the cluster, including the node from where you are invoking the installer.

For information about what you must specify for the use cases described in Overview, see Table 14-2.


Updating the Node List After Installing the Management Agent

Table 14-2 shows the command you must run after installing the Management Agents to update the node list of the cluster based on the use cases described in Overview.

Table 14-2 Updating the Node List After Installing Oracle Management Agent

Use Case CLUSTER_NODES Parameter Value Command to Update the Inventory

Installing a Management Agent on All the Nodes of a Cluster

For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. If you want to install a Management Agent on each of the nodes, then specify the following in the CLUSTER_NODES parameter of the response file:

CLUSTER_NODES={"n1","n2","n3","n4","n5"}

This installs a Management Agent on n1, n2, n3, n4, and n5, and updates the inventory of n1, n2, n3, n4, and n5 with details of n1, n2, n3, n4, and n5.

-

Installing a Management Agent Only on Some Nodes of a Cluster

For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. Let's assume that a Management Agent is installed only on n1 and n2. If you want to install a Management Agent on n3, n4, and n5, then specify the following in the CLUSTER_NODES parameter of the response file:

CLUSTER_NODES={"n3","n4","n5"}

This installs a Management Agent on n3, n4, and n5, and updates the inventory of n3, n4, and n5 with details of n3, n4, and n5 only.

To update the inventory of n1, n2, n3, n4, and n5 with details of all the nodes, run the following command from the Oracle home of the Management Agent from each of the nodes:

<ORACLE_HOME>/oui/bin/runInstaller ORACLE_HOME=<absolute_path_to_agent_home> -updateNodeList "CLUSTER_NODES={n1,n2,n3,n4,n5}" -local -invPtrLoc <absolute_path_to_OraInst.loc_File>

Installing a Management Agent on Additional Nodes that Extend the Cluster

For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. Let's assume that a Management Agent is installed on each of the nodes. You now introduce two new nodes n6 and n7 to the cluster. If you want to install a Management Agent on this new nodes, then specify the following in the CLUSTER_NODES parameter of the response file:

CLUSTER_NODES={"n6"}

This installs a Management Agent on n6, and updates the inventory of n6 with details of n6 only.

Run the same command on n7. Ensure that you specify only n7 in the cluster node list. This installs a Management Agent on n7, and updates the inventory of n7 with details of n7 only.

To update the inventory of n1, n2, n3, n4, n5, n6, and n7 with details of all the nodes, run the following command from the Oracle home of the Management Agent from each of the nodes:

$<ORACLE_HOME>/oui/bin/runInstaller ORACLE_HOME=<absolute_path_to_agent_home> -updateNodeList "CLUSTER_NODES={n1,n2,n3,n4,n5,n6,n7}" -local -invPtrLoc <absolute_path_to_OraInst.loc_File>

Installing a Management Agent on Two Clusters of the Same Name, but with Different Nodes

For example, let's say you have a cluster crs1 with nodes n1, n2, n3, n4, and n5. If you want to install a Management Agent on each of the nodes, then specify the following in the CLUSTER_NODES parameter of the response file:

CLUSTER_NODES={"n1","n2","n3","n4","n5"}

This installs a Management Agent on n1, n2, n3, n4, and n5, and updates the inventory of n1, n2, n3, n4, and n5 with details of n1, n2, n3, n4, and n5.

Then, run the response file on one of the nodes of the second cluster, and specify the nodes that belong to that cluster, separated by a comma.

-


Installing Using agentDownload Script

To install a Management Agent using the agentDownload script, follow these steps:

  1. On one of the nodes of the cluster where you want to install a Management Agent, open a browser to access the OMS URL and download the agentDownload script.

    UNIX Platform Microsoft Windows Platforms
    Using Browser
    http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.<platform>
    

    For example:

    http://host1.servers.com:4889/agent_download/11.1.0.0.0/linux/agentDownload.linux
    

    Using Command Line

    wget http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.<platform>
    

    For example:

    wget http://host1.servers.com:4889/agent_download/11.1.0.0.0/linux/agentDownload.linux
    
    Using Browser
    http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.vbs
    

    For example:

    http://host1.servers.com:4889/agent_download/11.1.0.0.0/win32/agentDownload.vbs
    

    Using Command Line

    wget http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.vbs
    

    For example:

    wget http://host1.servers.com:4889/agent_download/11.1.0.0.0/win32/agentDownload.vbs
    

  2. Run the agentDownload script as outlined in this step for the use case that matches your requirement:

    Use Case Installation Procedure
    Installing a Management Agent on All the Nodes of a Cluster Invoke the agentDownload script on one of the nodes of the cluster, and specify all the nodes separated by a comma.

    For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. If you want to install a Management Agent on each of the nodes, then run the following command on one of the nodes:

    • For UNIX

      ./agentDownload.<platform> -b <absolute_path_to_installation_base_directory> -n <cluster_name> -c "n1,n2,n3,n4,n5"

    • For Microsoft Windows

      cscript.exe agentDownload.vbs b <absolute_path_to_installation_base_directory> n <cluster_name> c "n1,n2,n3,n4,n5"

    Important: Ensure that the installation base directory is the same across the nodes of the cluster.

    This installs a Management Agent on n1, n2, n3, n4, and n5, and updates the inventory of n1, n2, n3, n4, and n5 with details of n1, n2, n3, n4, and n5.

    Installing a Management Agent Only on Some Nodes of a Cluster Invoke the agentDownload script on one of the nodes on which you want to install the Management Agent, and specify all the nodes (separated by a comma) on which you want to install the Management Agent.

    For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. Let's assume that a Management Agent is installed only on n1 and n2. If you want to install a Management Agent on n3, n4, and n5, then run the following command on n3:

    • For UNIX

      ./agentDownload.<platform> -b <absolute_path_to_installation_base_directory> -n <cluster_name> -c "n3,n4,n5"

    • For Microsoft Windows

      cscript.exe agentDownload.vbs b <absolute_path_to_installation_base_directory> n <cluster_name> c "n3,n4,n5"

    Important: Ensure that the installation base directory is the same across the nodes of the cluster.

    This installs a Management Agent on n3, n4, and n5, and updates the inventory of n3, n4, and n5 with details of n3, n4, and n5 only.

    To update the inventory of n1, n2, n3, n4, and n5 with details of all the nodes, run the following command from the Oracle home of the Management Agent from each of the nodes:

    <ORACLE_HOME>/oui/bin/runInstaller ORACLE_HOME=<absolute_path_to_agent_home> -updateNodeList "CLUSTER_NODES={n1,n2,n3,n4,n5}" -local -invPtrLoc <absolute_path_to_OraInst.loc_File>

    Installing a Management Agent on Additional Nodes that Extend the Cluster Invoke the agentDownload script on the new node, and specify all the nodes (separated by a comma) that are part of the cluster.

    For example, let's say you have a cluster named crs1 with nodes n1, n2, n3, n4, and n5. Let's assume that a Management Agent is installed on each of the nodes. You now introduce two new nodes n6 and n7 to the cluster. If you want to install a Management Agent on this new nodes, then run the following command on n6:

    • For UNIX

      ./agentDownload.<platform> -b <absolute_path_to_installation_base_directory> -n <cluster_name> -c "n6"

    • For Microsoft Windows

      cscript.exe agentDownload.vbs b <absolute_path_to_installation_base_directory> n <cluster_name> c "n6"

    Important: Ensure that the installation base directory is the same across the nodes of the cluster.

    This installs a Management Agent on n6, and updates the inventory of n6 with details of n6 only.

    Run the same command on n7. Ensure that you specify only n7 in the cluster node list. This installs a Management Agent on n7, and updates the inventory of n7 with details of n7 only.

    To update the inventory of n1, n2, n3, n4, n5, n6, and n7 with details of all the nodes, run the following command from the Oracle home of the Management Agent from each of the nodes:

    $<ORACLE_HOME>/oui/bin/runInstaller ORACLE_HOME=<absolute_path_to_agent_home> -updateNodeList "CLUSTER_NODES={n1,n2,n3,n4,n5,n6,n7}" -local -invPtrLoc <absolute_path_to_OraInst.loc_file>

    Installing a Management Agent on Two Clusters of the Same Name, but with Different Nodes Invoke the agentDownload script on one of the nodes of the first cluster, and specify all the nodes separated by a comma.

    For example, let's say you have a cluster crs1 with nodes n1, n2, n3, n4, and n5. If you want to install a Management Agent on each of the nodes, then run the following command on one of the nodes:

    • For UNIX

      ./agentDownload.<platform> -b <absolute_path_to_installation_base_directory> -n <cluster_name> -c "n1,n2,n3,n4,n5"

    • For Microsoft Windows

      cscript.exe agentDownload.vbs b <absolute_path_to_installation_base_directory> n <cluster_name> c "n1,n2,n3,n4,n5"

    Important: Ensure that the installation base directory is the same across the nodes of the cluster.

    This installs a Management Agent on n1, n2, n3, n4, and n5, and updates the inventory of n1, n2, n3, n4, and n5 with details of n1, n2, n3, n4, and n5.

    Then, run the same command from one of the nodes of the second cluster, and specify the nodes that belong to that cluster, separated by a comma.


Note:

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

After You Install

After you install the Management Agent, follow these steps outlined in After You Install.