Oracle Enterprise Manager Configuration Guide Release 2.2 Part Number A85247-01 |
Library | Service | Contents | Index

# C
Upgrading the Intelligent Agent and Data Gatherer

## Upgrading the Intelligent Agent

Each release of the Intelligent Agent improves Agent performance, functionality, and reliability. We therefore recommend upgrading your Intelligent Agent to the latest version available for your platform. As an integral part of your Enterprise Manager environment, certain steps must be followed to make sure the transition to a newer Agent does not affect your Enterprise Manager jobs and/or events.

### Agent Upgrade Guidelines for Enterprise Manager Version 2

1. Install the latest Intelligent Agent under a new Oracle Home.

2. Make sure that any jobs or events you wish to keep have been saved in the job or event library respectively. To add a job/event to a job/event library, select the job/event from the job/event pane, click on the desired entry using the right mouse button and select Copy to Library from the context-sensitive menu.

3. Move any event alerts to event history. You can save the contents of the history pane or clear them.

Note: If you have events registered against multiple targets, use the Create Like menu option to create individual events for each target and save these events to the Event Library.

1. From the Enterprise Manager Console, de-register any existing events and remove any active jobs scheduled against the node on which you ar upgrading the agent.

2. Shut down the old Agent.

3. Start the new Agent

4. From the OEM Console, refresh the node in the Navigator.

5. Resubmit the saved jobs and events to the new Agent.

### Migrating Enterprise Manager Jobs/Events from an 8.1.5 or 8.1.6 Agent to an 8.1.7 Agent

If you have existing jobs/events submitted against an 8.1.5/8.1.6 Intelligent Agent, and want to upgrade to an 8.1.7 Agent without having to re-submit jobs or re-register events, you must migrate all existing jobs/events using the following procedure.

1. Install the 8.1.7 Agent in a separate ORACLE_HOME.

2. Type lsnrctl dbsnmp_stop at the command line to stop the older 8.1.x Agent.

3. Copy all files ( *.q files, *.inp files, tcl* files) from the older Agent's ORACLE_HOME/network/agent directory to the 8.1.7 Agent's ORACLE_HOME/network/agent directory. Do not copy the directories. These files should now be owned by the user who installed the 8.1.7 Agent. Check the ownership of these files in the newer Agent's directory.

4. Type lsnrctl dbsnmp_start to start the 8.1.7 Agent.

5. Make sure that the services (databases, listeners etc.) discovered by the new Agent are identical to those discovered by the older Agent.

   A quick comparative check between service names and definitions in the older Agent's ORACLE_HOME/network/agent/services.ora file and that of the newer Agent, is highly recommended.

6. From the Enterprise Manager Console, refresh the Agent's node.

After migration, all previous jobs/events should continue to run as before.

## Upgrading From a Previous Version of the Data Gatherer

It is possible to install the new version of the Oracle Data Gatherer into a different Oracle Home than the previous version. If you plan to do this, follow these steps:

1. Stop the previous version of the Oracle Data Gatherer. See "Controlling Operations of the NT and UNIX Data Gathering Service" in the Oracle Intelligent Agent's User's Guide for more information on stopping the Oracle Data Gatherer.

2. Install the new version of the Oracle Data Gatherer, but do not start it.

3. Move the Capacity Planning configuration files (state files) and data files associated with the previous version of Oracle Data Gatherer to the Oracle Home where you have installed the new version of Oracle Data Gatherer.

   The Oracle Data Gatherer state and data files are located in the `$ORACLE_HOME/odg/reco` directory. You need to copy the files into the new `$ORACLE_HOME/odg/reco` directory before you use Oracle Capacity Planner to connect to the new version of the Oracle Data Gatherer and set up any new collections.

   If you do not move these files, the following problems will occur:

   1. Binary data is not loaded.

      Any binary data files created by Oracle Data Gatherer which have not yet been loaded into the Capacity Planner database will not be loaded.

   2. Data collection definitions are not maintained.

      You will need to redefine your Capacity Planner data collections.

   If you have installed the new version of Oracle Data Gatherer into the same Oracle Home as the previous version or if you do not currently use the Oracle Capacity Planner, do not move the state and data files.

4. Start the new version of the Oracle Data Gatherer. See "Controlling Operations of the NT and UNIX Data Gathering Service" in the Oracle Intelligent Agent's User's Guide for more information about starting the Oracle Data Gatherer.

| Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index