Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 1 (12.1.0.1)
Part Number E22625-08
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

3 Things to Know

Before you use the upgrade approaches to upgrade to Enterprise Manager Cloud Control, keep these points in mind:

Supported Upgrade Paths

The following upgrade paths are supported:

If you have Enterprise Manager 10g Grid Control Release 1 (10.1) or Enterprise Manager 10g Grid Control Release 4 (10.2.0.4.0) or lower, then you must first upgrade or patch them to Enterprise Manager 10g Grid Control Release 5 (10.2.0.5.0) or Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0). After upgrading or patching them to the supported releases, upgrade them to Enterprise Manager Cloud Control.

Supported Platforms for Upgrade

The following platforms are supported:

Upgrade Scope

The following are some facts about the upgrade approaches:

Reusing Existing Ports

When you upgrade your Management Agents, the ports used by the earlier release of the Management Agents are carried over to the upgraded Management Agents. Therefore, your firewall settings are not affected in any way.

When you upgrade your OMS, the following ports are assigned:

Installing Plug-Ins

To identify the plug-ins required for upgrade, in the Enterprise Manager 12c Upgrade Console, in the Preupgrade Steps section, click Manage Software. On the Manage Software page, view the plug-ins that are required for upgrading your system.

The plug-ins listed on the Manage Software page are based on the targets monitored by the old Management Agents in your existing system, and also based on the new plug-in requirement Enterprise Manager Cloud Control has. You need all the plug-ins listed on this page to successfully upgrade your existing system.

This section describes how you can download and install the required plug-ins while upgrading the Management Agent and OMS. In particular, this section covers the following:

Installing Plug-Ins While Upgrading Oracle Management Agent

To install the required plug-ins while upgrading the Management Agents, follow these steps:

  1. Access the following URL:

    http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

  2. Download the Management Agent software to an accessible location. Do NOT extract the contents of the software ZIP file. The Management Agent software is platform-specific, so ensure that you copy the software for the platform on which you want to install.

  3. Download all the required plug-ins to the same location. Plug-ins are generic, so they are common for all platforms.

    Ensure that you download all the plug-ins listed as required plug-ins on the Manage page, whether or not you want to monitor a target with them. You may feel that a few plug-ins are not required because you do not have targets to be monitored by them, but those plug-ins may be required for upgrading your system. Therefore, download all the plug-ins listed on the Manage Software page. Ensure that you download these plug-ins before backing up the database that contains the Management Repository.

    Note:

    You can also download these plug-ins from the <software_kit>/plugins directory, but Oracle recommends you to download them from OTN so that you always procure the latest plug-ins and the plug-ins for all platforms.

    Note:

    To identify what plug-ins are required, in the Enterprise Manager 12c Upgrade Console, in the Preupgrade Steps section, from the table, click Manage Software. On the Manage Software page, in the Plug-In Software section, see the required plug-ins.

    Download all the plug-ins listed as required plug-ins on the Manage Software page, whether or not you want to monitor a target with them. You may feel that a few plug-ins are not required because you do not have targets to be monitored by them, but those plug-ins may be required for upgrading your system. Therefore, download all the plug-ins listed on the Manage Software page. And ensure that you download these plug-ins before backing up the database that contains the Management Repository.

  4. In the Enterprise Manager 12c Upgrade Console, on the Manage Software page (Preupgrade Steps section), in the Provide Software Location section, enter the absolute path to the directory where the plug-in is present, and click Validate to register that location with the Management Repository.

See:

For information about registering and validating the plug-in location, see Chapter 9.

Installing Plug-Ins While Upgrading Oracle Management Service

To install the required plug-ins while upgrading the OMS, invoke the installer and proceed to the Select Plug-Ins screen. The screen lists all the required plug-ins you registered via the the Enterprise Manager 12c Upgrade Console while upgrading the Management Agents. The mandatory ones are enabled by default.

Note:

If you had missed registering some required plug-ins, then the wizard prompts you to visit the Enterprise Manager 12c Upgrade Console to register them before proceeding with the upgrade.

Ensure that the software for the plug-ins listed on this screen are available in the Enterprise Manager Cloud Control software kit (DVD or downloaded software). If the software for the required plug-ins are not available, then do the following:

Discovering and Monitoring Targets

After you upgrade a Management Agent, by default, the Management Agent and the host on which you upgraded the Management Agent get automatically discovered in the Enterprise Manager Cloud Control console.

After you upgrade an OMS, by default, the following get automatically discovered in the Enterprise Manager Cloud Control console:

However, the other targets running on that host and other hosts do not get automatically discovered and monitored. To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.

For information about discovering targets in Enterprise Manager Cloud Control, refer to the Oracle Enterprise Manager Cloud Control Administrator's Guide available in the Enterprise Manager documentation library at:

http://www.oracle.com/technetwork/indexes/documentation/index.html

Managing Notification

After upgrading the entire Enterprise Manager system, all notification rules and alerts created in the earlier release continue to work in Enterprise Manager Cloud Control. However, note that they have been enhanced and subsumed into a larger and newer concept—Notification Rules are now called Incident Rulesets, and Alerts are now called Events in Enterprise Manager Cloud Control.

For information about Incident Rulesets and how they map to notification rules, and for information about Events and how they map to alerts, see Appendix A.

Managing Alerts

During upgrade, the alerts from the ealier release are migrated as Events in Enterprise Manager Cloud Control in the following manner. For 1-System upgrade approach, the alerts are migrated while upgrading the Management Repository. For 2-System upgrade approach, the alerts are migrated while backing up the Management Repository to the remote host.

This section covers the following:

Migrating Alerts

The following are the ways in which the alerts are migrated:

  • All open alerts are migrated.

    Table 3-1 shows how and when incidents and events are created for different types of open alerts.

  • All alerts that were closed 180 days prior to upgrading or backing up the Management Repository are migrated as part of the Deferred Data Migration Process. This period of 180 days can be changed by the administrator.

    Table 3-2 shows how and when incidents and events are created for different types of closed alerts. Also note that if a closed alert had an associated ticket, then that information is not captured as part of the event migration.

  • All open statefull alerts, and open stateless alerts created within 7 days prior to upgrading or backing up the Management Repository are migrated.

Note:

In case of 2-System uprade approach, if an alert is created in the earlier release of the Enterprise Manager system after the Management Repository is backed up, then that open alert is migrated as part of the Accrued Data Migration Process (see Table 3-1). In addition, all availability records are also migrated as part of the Accrued Data Migration Process.

Creating Incidents and Events for Different Types of Open Alerts

Table 3-1 shows how and when incidents and events are created for different types of open alerts.

Table 3-1 Incidents and Events Created for Different Types of Open Alerts

Open Alert Type Incident Created Event Created

Critical Alert

Yes

Yes

Warning Alert

No

Yes

Critical Alert with Ticket

Yes

Yes (with Ticket)

Warning Alert with Ticket

Yes

Yes (with Ticket)

Warning Alert with Notification Pending

Yes

Yes

Warning Alert without Notification Pending

No

Yes

Critical Alert with Acknowledgement

Yes

Yes

Warning Alert with Acknowledgement

Yes

Yes

Creating Incidents and Events for Different Types of Closed Alerts

Table 3-2 shows how and when incidents and events are created for different types of closed alerts. Also note that if a closed alert had an associated ticket, then that information is not captured as part of the event migration.

Table 3-2 Incidents and Events Created for Different Types of Closed Alerts

Closed Alert Type Incident Created Event Created

Critical Alert

No

Yes

Warning Alert

No

Yes

Critical Alert with Ticket

No

Yes (without Ticket)

Warning Alert with Ticket

No

Yes (without Ticket)

Warning Alert with Notification Pending

No

Yes

Warning Alert without Notification Pending

No

Yes

Critical Alert with Acknowledgement

No

Yes

Warning Alert with Acknowledgement

No

Yes

Managing Jobs

For 1-System upgrade approach, jobs can run more or less as expected. During the downtime, jobs do not run, and any job that is running during the downtime is aborted or failed. In addition, all the scheduled jobs continue as they were planned.

For 2-System upgrade approach, there are some restrictions and caveats on how jobs run. Firstly, since a Management Agent is monitored only by one particular Enterprise Manager system at any point, jobs can run only in the system that monitors the Management Agent. Until a Management Agent is migrated, all jobs against targets monitored by that Management Agent are run in the old Enterprise Manager system. This also means that only one Enterprise Manager system has the true status of a job because the Management Agent communicates only with one of the systems at a given time, so only that Enterprise Manager system knows what the actual status is.

Managing Deployment Procedure Runs

After upgrading the entire Enterprise Manager system, none of the old deployment procedure runs will be available in the upgraded Enterprise Manager. If you want to reference any of the old runtime data, then you must use the following EM CLI verb to export all of the runtime data as an XML file.

get_instance_data_xml

Using Oracle Software Library

The following is the status of Oracle Software Library (Software Library) after the Enterprise Manager is upgraded:

Using Connectors

After upgrading the entire Enterprise Manager system, the connectors that were configured with your old Enterprise Manager system will continue to work in Enterprise Manager Cloud Control. However, the ones that were not configured will not work.

Collecting Metrics

Some metrics related to the Oracle Fusion Middleware targets have been renamed in Enterprise Manager Cloud Control. In addition, a few have been introduced. The following are the targets for which the metrics have undergone some changes. For information about the metric changes, see Appendix B.

In general, do not modify the metric thresholds after deploying and configuring the Management Agents.

Upgrading EMCLI Clients

You must upgrade all existing EMCLI clients of the earlier release to 12c Release 1 so that they can work with Enterprise Manager Cloud Control. This means, you must discard the old one and set up a new one.

For information about setting up a new EMCLI client, see the Enterprise Manager Command Line Interface Download page within the Cloud Control console. To access that page, in Cloud Control, from the Setup menu, select My Preferences, and then, click Command Line Interface.

Go to previous page
Previous		 Go to next page
Next
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