28 Upgrading Oracle Management Agent with Add-Ons

This chapter describes how you can upgrade an existing Oracle Management Agent 10g Release 4 (10.2.0.4.0) or higher that has add-ons to Oracle Management Agent 11g Release 1 (11.1.0.1.0).

In particular, this chapter covers the following:

Overview

When you upgrade Oracle Management Agent (Management Agent), the add-ons that have been installed on it are NOT carried over to the upgraded version of the Management Agent. The upgrade process is an out-of-place upgrade, that is, it creates a new Oracle home for the upgraded version of the Management Agent (agent11g).

Due to this reason, the add-ons that were installed on the older release of the Management Agent are NOT automatically reinstalled on the upgraded version.

If you want to continue to use them, then you must first upgrade the software binaries of the existing Management Agent, then install the add-ons, and then finally configure the upgraded software binaries of the Management Agent.

Note:

If you are upgrading a Management Agent whose software binaries were used for installing additional Management Agents, either using the Shared Agent Deployment Wizard or the nfsagentinstall script, then before proceeding any further, read Chapter 27, "Upgrading Shared Oracle Management Agent".

Before You Begin

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

Prerequisites

Before upgrading a Management Agent that has add-ons, ensure that you meet the prerequisites described in Prerequisites.

Upgrade Management Agent

To upgrade an existing Management Agent that has add-ons, follow these steps:

  1. Stop the Management Agent you want to upgrade.

  2. On the host where you want to upgrade the Management Agent, download the Management Agent Software as described in Procuring Oracle Management Agent Software.

  3. Navigate to the following location and edit the response file upgrade_agent.rsp as described in Table 25-1.

    <Software_Location>/<platform>/response/

  4. Invoke the installer:

    • If you have the default name for the Oracle home of your existing Management Agent, that is, agent10g, then run the following command:

      ./runInstaller -noconfig -silent -responseFile <absolute_path_to_upgrade_agent.rsp_file>

    • If you have a custom name for the Oracle home of your existing Management Agent, then run the following command:

      ./runInstaller -noconfig -silent -responseFile <absolute_path_to_upgrade_agent.rsp_file> s_oldAgentHome=<absolute_path_to_Old_Oracle_Home>

After You Upgrade

After you upgrade the software binaries of the Management Agent, follow these steps to install the add-ons in the Oracle home of the Management Agent.

  1. Create a response file titled addon_agent.rsp, and specify the following details:

    RESPONSEFILE_VERSION=2.2.1.0.0
    FROM_LOCATION=<full path of products.xml>
    DEINSTALL_LIST={"<add-on agent component name>","<add-on agent component version>"}
    TOPLEVEL_COMPONENT={"<add-on agent component name>","<add-on agent component version>"}
    ORACLE_HOME=<Agent OracleHome>
    ORACLE_HOME_NAME=<name of the Oracle Home>
    b_upgrade=false
    b_silentInstall=true
    ACCEPT_LICENSE_AGREEMENT=true
    
  2. Run the following command from the Oracle home of the Management Agent and pass the response file to install the add-ons:

    $<ORACLE_HOME>/oui/bin/runInstaller -noconfig -silent -responseFile <absolute_path_to_Location>

Configuration Procedure

After installing the add-ons, configure the Management Agent by running the following command:

  • If you are upgrading a standalone Management Agent, then run the following command from the Oracle home of the Management Agent:

    $<ORACLE_HOME>/bin/agentca -u

  • If you are upgrading a cluster-based Management Agent, then on each of the nodes of the cluster, run the following command:

    $<ORACLE_HOME>/bin/agentca -u -c <node1,node2,node3,...nodeN> -r <absolute_path_to_Response_File>

    Note:

    • In this command, -c lists the nodes of the cluster separated by a comma, and the response file is a user-defined response file that contains the following entry to refer to the node on which you are invoking the agentca script.

      s_hostname=<Node_Name>

    • You can ascertain the node name from the old Oracle home of the Management Agent by running the following command:

      $<ORACLE_HOME>/bin/emctl getemhome

    For example, if you have a cluster of three nodes, mainly node1, node2, node3, then create a response file called response.rsp with the entry s_hostname=node1, and on node1, run the following command:

    $<ORACLE_HOME>/bin/agentca -u -c node1,node2,node3 -r /home/john/response.rsp

    Now, update the response file to reflect s_hostname=node2, and on node2, run the same command. Finally, update the response file to reflect s_hostname=node3, and on node3, run the same command.

After You Configure

After configuring the Management Agent, follow the steps outlined in After You Upgrade.