Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 2 (12.1.0.2)
E22625-16
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

3 Getting Started

This chapter describes the high-level process for upgrading your Enterprise Manager 12c Release 1 (12.1.0.1) to 12c Release 2 (12.1.0.2). In particular, this chapter covers the following:


WARNING:

Do not upgrade Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) while it is undergoing a 2-system upgrade from its earlier release. Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.



Note:

Oracle recommends you to read My Oracle Support note 1494890.1, which captures some important facts you must know before you get started with the upgrade.

Upgrading Primary Enterprise Manager

Table 3-1 describes the steps for upgrading your primary Enterprise Manager site to 12c Release 2 (12.1.0.2).

Table 3-1 Upgrading Primary Enterprise Manager Site

Step No. Step Procedure

Step 1

Prepare Yourself


(a)

Learn about the 1-System upgrade approach.

Upgrading 12c Release 1 (12.1.0.1) [With or without Bundle Patch 1] to 12c Release 2 (12.1.0.2)


(b)

Review the important facts you need to know before you begin.

Chapter 2


Step 2

Upgrade Oracle Management Service and Oracle Management Repository


(a)

Meet the following prerequisites:


(b)

Check for any outstanding database service instance creation requests. If there are any requests in progress, allow them to complete. For requests that are scheduled, suspend them.

To do so, follow these steps.

  1. In Cloud Control, from the Enterprise menu, select Infrastructure Cloud, then select Self Service Portal.

  2. On the Infrastructure Cloud Self Service Portal page, right under the page title, select My Databases to view only database requests.

  3. In the Requests table, for requests that are in progress, allow them to complete. For requests that are scheduled, suspend them.

    To suspend the scheduled requests, click the request name. Click the Deployment tab. Click the deployment procedure listed there, and suspend it.


(c)

Ensure that the tables in the Management Repository do not have any snapshots created.

To verify this, log in to the Management Repository and run the following SQL query as SYSMAN user:

select master , log_table from all_mview_logs where log_owner='<EM_REPOS_USER>

For example,

select master , log_table from all_mview_logs where log_owner='SYSMAN'

If there are snapshots created in a table, then the query displays the master table and the snapshot details. For example,

SQL> master log_table

em-violations em$violation_log

If there are snapshots, then drop them by running the following command as SYSMAN user:

SQL> Drop snapshot log on <master>

For example,

SQL> Drop snapshot log on em-violations

(d)

Copy the emkey from the existing OMS to the existing Management Repository. To do so, run the following command on the old OMS home you are trying to upgrade:

$<OMS_HOME>/bin/emctl config emkey -copy_to_repos [-sysman_pwd <sysman_pwd>]

To verify whether the emkey is copied, run the following command:

<OMS_HOME>/bin/emctl status emkey

If the emkey is copied, then you will see the following message:

The EMKey  is configured properly, but is not secure.
Secure the EMKey by running "emctl config emkey -remove_from_repos".

(e)

Stop the OMS you are about to upgrade and also the other OMS instances that connect to it.

  • If you are upgrading in graphical mode, then you can stop the OMS later as described in Step (12) of Upgrading OMS and Management Repository in Graphical Mode.

  • If you are installing software only and upgrading later in graphical mode, then you can stop the OMS later as described in Step (4) in Configuring and Upgrading.

  • If you are upgrading in silent mode, then stop the OMS now:

    First, on the OMS you are upgrading, run the following command to stop the OMS. This command stops only the OMS, and not the Admin Server or any of its associated components. The Admin Server and other associated components must be running so that the WebLogic Server credentials can be validated.

    $<OMS_HOME>/bin/emctl stop oms

    Then, on all other additional OMS instances, run the following command. This command stops the OMS and other components such as the node manager, which must be down for the upgrade to end successfully.

    $<OMS_HOME>/bin/emctl stop oms -all


(f)

Shut down the Management Agent that monitors the Management Services and Repository target, to prevent the Management Agent from connecting to the Management Repository for metric collections. Not shutting down this Management Agent might cause the OMS upgrade to fail.


(g)

Upgrade the OMS and the Management Repository. You can choose to upgrade in graphical or silent mode. You can also choose to install the software binaries at one point and upgrade them later in graphical or silent mode.

If you see an error message stating that you have not copied the emkey, then follow these steps:

  1. Copy the emkey from the old OMS to the old Management Repository. To do so, run the following command from the old OMS home you are trying to upgrade:

    $<OMS_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc <conndesc> -repos_user <username> [-repos_pwd <pwd>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora

    Note: Here, the Management Repository details are the details of the existing Management Repository you are trying to upgrade. And <OMS_HOME> is the OMS home you are trying to upgrade.

  2. Try upgrading the OMS and the Management Repository again.

IMPORTANT: Upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS.

For single-OMS environment, see Upgrading OMS and Management Repository in Graphical Mode, Upgrading OMS and Management Repository in Silent Mode, Installing Software Now and Upgrading Later in Graphical Mode, or Installing Software Now and Upgrading Later in Silent Mode

For multi-OMS environment (with additional OMS instances), see Upgrading Multi-OMS Environment

(h)

If you had BI Publisher 11.1.1.5.0 installed to run on Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1), which you had stopped in Step 2 (a), then it is necessary to install and upgrade to BI Publisher 11.1.1.6.0. For instructions, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.


Step 3

Upgrade Oracle Management Agent


(a)

Review the important facts you need to know before you begin upgrading the Management Agents.

Before You Begin


(b)

Meet the prerequisites.

Prerequisites


(c)

Upgrade the Management Agents.

IMPORTANT: Upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS

Upgrade Procedure


Step 4

Perform Postupgrade Task


(a)

Perform postupgrade tasks.

Performing General Postupgrade Steps


(b)

Track the status of deferred data migration jobs.

Tracking the Status of Deferred Data Migration Jobs


(c)

(Applicable only if you are upgrading from 12c Release 1 (12.1.0.1) [with or without Bundle Patch 1] to 12c Release 2 (12.1.0.2) Patch Set 1 released in October 2012, and if you want to upgrade your Oracle Database plug-ins from one revision of 12.1.0.2 to another (for example, from 12.1.0.2 to 12.1.0.2 [u120804], or from 12.1.0.2 [u120427] to 12.1.0.2 [u120804])

Upgrade the existing database plug-in revisions to the latest revision.

Upgrading Oracle Database Plug-ins


(d)

Upgrade Application Dependency and Performance (ADP) engines and JVM Diagnostics (JVMD) engines

Chapter 6



Upgrading Standby Enterprise Manager

Table 3-1 describes the steps for upgrading your standby Enterprise Manager site to 12c Release 2 (12.1.0.2).

Table 3-2 Upgrading Standby Enterprise Manager Site

Step No. Step Procedure

Step 1

Removing Standby Enterprise Manager


(a)

Remove all additional standby OMS instances.

"Removing Additional Standby OMS Instances" section of the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

(b)

Remove the first standby OMS.

"Removing the First Standby OMS" section of the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Step 2

Upgrade Primary Enterprise Manager



Upgrade the primary Enterprise Manager site, both OMS and Management Agents.

Upgrading Primary Enterprise Manager


Step 3

Redeploy Standby Enterprise Manager



Re-create the standby OMS instances—the first as well as the additional instances as required.

IMPORTANT: Ensure that you re-create them with a domain name that is different from the one used for the primary site and for the old standby site.

"Setting Up High Availability" chapter of the Oracle Enterprise Manager Cloud Control Administrator's Guide