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

25 Upgrading Oracle Management Agent Using a Response File

This chapter describes how you can upgrade an existing Oracle Management Agent 10g Release 4 or 5 (10.2.0.4.0 or 10.2.0.5.0) to Oracle Management Agent 11g Release 1 (11.1.0.1.0) in a silent mode using the response file.

In particular, this chapter covers the following:

Overview

You can upgrade an existing Oracle Management Agent 10g Release 4 or 5 (10.2.0.4.0 or 10.2.0.5.0) to Oracle Management Agent 11g Release 1 (11.1.0.1.0) using the response file upgrade_agent.rsp. The response file collects all the information that the Agent Upgrade Wizard collects in its screens, and performs exactly the same function that the Agent Upgrade Wizards performs.

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, ensure that you meet the prerequisites described in Prerequisites.

Upgrade Procedure

To upgrade an existing Management Agent using a response file, 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/upgrade_agent.rsp

  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 -silent -responseFile <absolute_path_to_upgrade_agent.rsp_file>

      Note:

      On Microsoft Windows, do the following:
      • If you are upgrading a non-shared RAC Agent, then run the following command on every node of the cluster:

        setup.exe -silent -responseFile <absolute_path_to_upgrade_agent.rsp_file> -local

      • If you are upgrading a shared RAC Agent, then do the following:

        (a) On one of the nodes, run the following command:

        setup.exe -silent -responseFile <absolute_path_to_upgrade_agent.rsp_file> -local

        (b) On each of the other nodes, run the following command from the Oracle home of the Management Agent:

        <ORACLE_HOME>/bin/agentca -u -c <comma-separated_list_of_nodes'_short_names> -r <absolute_path_to_response_file>

        Here, the response file passed in the above-mentioned command contains the following parameter with the fully qualified name of the node on which you are invoking the command:

        s_hostname=<fully_qualified_name_of_node>

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

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

      Note:

      On Microsoft Windows, technical writing blogs:
      • If you are upgrading a non-shared RAC Agent, then run the following command on every node of the cluster:

        setup.exe -silent -responseFile <absolute_path_to_upgrade_agent.rsp_file> s_oldAgentHome=<absolute_path_to_Old_Oracle_Home> -local

      • If you are upgrading a shared RAC Agent, then do the following:

        (a) On one of the nodes, run the following command:

        setup.exe -silent -responseFile <absolute_path_to_upgrade_agent.rsp_file> s_oldAgentHome=<absolute_path_to_Old_Oracle_Home> -local

        (b) On each of the other nodes, run the following command from the Oracle home of the Management Agent:

        <ORACLE_HOME>/bin/agentca -u -c <comma-separated_list_of_nodes'_short_names> -r <absolute_path_to_response_file>

        Here, the response file passed in the above-mentioned command contains the following parameter with the fully qualified name of the node on which you are invoking the command:

        s_hostname=<fully_qualified_name_of_node>

Table 25-1 Response File Parameters for Upgrading Oracle Management Agent

Variable Name Description

OLD_BASE_DIR

  • If you have the default name for the Oracle home of your existing Management Agent, that is, agent10g, then specify the path to the old installation base directory where the Management Agent to be upgraded is residing.

    For example, if the Management Agent is residing in /john/OracleHomes/10.2/agent10g, then specify only /john/OracleHomes/10.2/

  • If you have a custom name for the Oracle home of your existing Management Agent, then pass the s_oldAgentHome argument while running the installer and specify the path to that Oracle home in the command.

ORACLE_AGENT_HOME_LOCATION

Specify the location where the Oracle home of the Management Agent (agent11g) can be created.


After You Upgrade

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