Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 4 (12.1.0.4)

E22625-28
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

4 Getting Started

This chapter describes the high-level process for upgrading your Enterprise Manager 12c Release 3 (12.1.0.3) or 12c Release 2 (12.1.0.2) to 12c Release 4 (12.1.0.4).

In particular, this chapter covers the following:

Note:

  • If you have Oracle Management Service 12c Release 1 (12.1.0.1) [with or without Bundle Patch 1], then first upgrade it to either 12c Release 2 (12.1.0.2) or 12c Release 3 (12.1.0.3), and then upgrade to 12c Release 4 (12.1.0.4).

    For instructions to upgrade to 12c Release 2 (12.1.0.2) or 12c Release 3 (12.1.0.3), refer to the Oracle Enterprise Manager Cloud Control Upgrade Guide for the respective release, available in the Enterprise Manager documentation library:

    http://docs.oracle.com/cd/E24628_01/index.htm

  • If you have Oracle Management Agent 12c Release 1 (12.1.0.1) that communicates with Oracle Management Service 12c Release 2 (12.1.0.2) or 12c Release 3 (12.1.0.3), then before upgrading the Oracle Management Service to 12c Release 4 (12.1.0.4), make sure you upgrade your Oracle Management Agent 12c Release 1 (12.1.0.1) to either 12c Release 2 (12.1.0.2) or 12c Release 3 (12.1.0.3) using the Agent Upgrade Console present within the Enterprise Manager Cloud Control Console.

    This is a prerequisite for upgrading your Oracle Management Service 12c Release 2 (12.1.0.2) or 12c Release 3 (12.1.0.3) to 12c Release 4 (12.1.0.4).

WARNING:

Do not upgrade 12c Release 3 (12.1.0.3) or 12c Release 2 (12.1.0.2) while it is undergoing a 2-system upgrade from its earlier release (10.2.0.5 or 11.1.0.1). Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress.

4.1 Upgrading Enterprise Manager in a Single-OMS Non-HA Environment

Table 4-1 describes the steps for upgrading your Enterprise Manager to 12c Release 4 (12.1.0.4) in a single-OMS non-HA (or non-high availability) environment.

Table 4-1 Upgrading Enterprise Manager in a Single-OMS Non-HA Environment

Step No. Step Procedure

Step 1

Prepare Yourself

 

(a)

Learn about the 1-System upgrade approach.

Section 2.1

(b)

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

Chapter 3

Step 2

Upgrade Oracle Management Service and Oracle Management Repository

 

(a)

Meet the following prerequisites:

  • Meet the Oracle Management Service-related prerequisites described in the chapter on installing Enterprise Manager Cloud Control, in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

  • Upgrade to 12c Release 4 (12.1.0.4) is an out-of-place upgrade, therefore make sure your host meets the hardware requirements specific to 12c Release 4 (12.1.0.4) as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide. Here, host refers to the host on which your current Enterprise Manager, which you want to upgrade, is running.

  • Ensure that you are upgrading only on the supported platforms as listed in Section 3.2.

  • Ensure that the ports used by Enterprise Manager are not set to a value lower than or equal to 1024. If they are, then the upgrade will fail. Ports up to 1024 are typically reserved for root users (super users). Therefore, make sure the ports are greater than 1024.

  • If you have BI Publisher installed on Enterprise Manager Cloud Control 12c installation that you are upgrading from, then stop the BI Publisher Managed Server named BIP using the WebLogic Administration Console. For instructions, refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

  • Back up the OMS (the middleware home and the inventory), the Management Repository, and the Software Library. In case the upgrade fails, you can always restore using the backup. For instructions to back up, refer to Oracle Enterprise Manager Cloud Control Administrator's Guide.

  • Make a copy (using the Create Like action) of the out-of-box rule sets you are using to receive e-mail notifications. Otherwise, you will lose the e-mail subscriptions made to the rule sets.

    To make a copy, from the Setup menu, select Incidents, then select Incident Rules. On the Incident Rules - All Enterprise Rules page, in the table, select the out-of-box rule set you want to copy. Then, from the Actions menu, select Create Like Rule Set. In the Create Like Rule Set page, provide the required details and click Save.

  • Ensure that the contents of the following directory across OMS hosts are the same. If the number of plug-ins and/or their revisions are different across OMS hosts, then ensure that you copy them over from one pluginextract_with_rev directory to another to make them consistent.

    <OMS_HOME>/sysman/install/pluginextract_with_rev

    For example, on the first OMS host, OMS_Host1, you may have the following plug-ins and revisions:

    oracle.sysman.emfa 12.1.0.1.0 and 12.1.0.2.0; oracle.sysman.bda 12.1.0.1.0, 12.1.0.2.0, and 12.1.0.3.0; and oracle.em.sidb 12.1.0.1.0 and 12.1.0.2.0.

    On the additional OMS host, OMS_Host2, you may have the following plug-ins: oracle.sysman.emfa 12.1.0.1.0 and 12.1.0.2.0; oracle.sysman.bda 12.1.0.3.0; and oracle.em.sehc 12.1.0.1.0.

    In this case, ensure that you copy oracle.sysman.bda 12.1.0.1.0 and 12.1.0.2.0, and oracle.em.sidb 12.1.0.1.0 and 12.1.0.2.0 from the first OMS host to the additional OMS host, and ensure that you copy oracle.em.sehc 12.1.0.1.0 from the additional OMS host to the first OMS host. This way, the plug-ins and their revisions in both OMS hosts will be consistent.

 

(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 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)

(CRITICAL MANDATORY STEP)

Apply the following patches on the database. You can access My Oracle Support and search for these patches. For instructions, see the ReadMe file associated with the patch. If you do not apply these patches, you will run into upgrade failures that cannot be corrected.

For Oracle Database 11 Release 1 (11.1.0.7)

  • On Unix platforms, apply patch 17082366 (Patch Set Update 17). Then apply patch 9577583 and patch 8405205.

  • On Microsoft Windows (32 bit and 64 bit) platforms, apply patch 17363760 (Patch 54).

For Oracle Database 11g Release 2 (11.2.0.1)

  • On Unix platforms, apply patch 12419378 (Patch Set Update 6).

  • On Microsoft Windows (64 bit) platforms, apply patch 13423278 (Patch 16).

For Oracle Database 11g Release 2 (11.2.0.2)

  • On Unix platforms, apply patch 11061801 and patch 9748749.

  • On Microsoft Windows (32 bit) platforms, apply patch 11061801 and patch 12429530.

  • On Microsoft Windows (64-bit) platforms, apply patch 11061801 and patch 12429531.

For Oracle Database 11g Release 2 (11.2.0.3), 10g Release 2 (10.2.0.5)

On Unix as well as Microsoft Windows platforms, apply the patch 11061801.

For Oracle Database 12c Release 1 (12.1.0.1)

On Unix as well as Microsoft Windows platforms, apply the patch 16619249.

Note: Oracle also recommends that you apply patch 13496395. For information on what database releases you can apply the patch, see the ReadMe that is packaged with the patch.

 

(e)

[IN CASE OF MULTI-OMS UPGRADE, PERFORM THIS STEP ONLY FOR THE FIRST OMS UPGRADE]

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".
 

(f)

If you have changed the default, out-of-box memory settings for an OMS instance, then preserve the changes so that they are not lost during upgrade.

To preserve the changes, follow these steps:

  1. Run the following command on all the OMS instances:

    $<OMS_HOME>/bin/emctl set property -name 'JAVA_EM_MEM_ARGS' -value '<java_memory_arguments>'

    For example,

    $<OMS_HOME>/bin/emctl set property -name 'JAVA_EM_MEM_ARGS' -value '-Xms256m -Xmx1740m'

  2. Restart all the OMS instances:

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

    $<OMS_HOME>/bin/emctl start oms

 

(g)

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

  1. As a prerequisite, stop the JVMD and ADP engines explicitly:

    • To stop them in silent mode, run the following commands:

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

      $<OMS_HOME>/bin/emctl extended oms adp stop –all

    • To stop them in graphical mode, access the weblogic console, and stop the JVMD and ADP weblogic managed servers manually.

  2. Now stop the OMS you are about to upgrade and also the other OMS instances that connect to it:

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

 

(h)

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.

 

(i)

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

    For example,

    /u01/software/oracle/middleware/oms/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc '"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost.mydomain.com)(PORT=1521)))(CONNECT_DATA=(SID=emrepos12)))"' -repos_user sysman -emkey_file /u01/software/oracle/middleware/oms/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. To upgrade this Management Agent, use the Agent Upgrade Console.

For single-OMS environment, see Section 5.1, Section 5.2, Section 5.3, or Section 5.4

For multi-OMS environment (with additional OMS instances), see Section 5.5

Step 3

Upgrade Oracle Management Agent

 

(a)

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

Section 6.2

(b)

Meet the prerequisites.

Section 6.3

(c)

Ensure that you restart the Management Agent that you shut down in Step 2 (h).

 

(d)

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. To upgrade this Management Agent, use the Agent Upgrade Console.

Section 6.4

Step 4

Perform Postupgrade Task

 

(a)

Perform postupgrade tasks.

Section 12.6.1

(b)

Reconfigure Oracle WebLogic Server with custom certificates

Section 12.6.14

(c)

Track the status of deferred data migration jobs.

Section 12.7.2

(d)

Delete unwanted central agents

Section 12.13.2

(e)

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

Chapter 7

(f)

As part of the upgrade to Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4), Oracle BI Publisher 11.1.1.7.0 is automatically installed. Therefore, do not perform a software-only install of any version of Oracle BI Publisher in the middleware home that contains Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4). However, although Oracle BI Publisher is installed by default, it is not configured by default.

If you already had Oracle BI Publisher in your earlier release, then you can upgrade it. Otherwise, you can configure the newly installed Oracle BI Publisher.

Oracle Enterprise Manager Advanced Installation and Configuration Guide.

(g)

Delete old OMS home

Section 12.15


4.2 Upgrading Enterprise Manager in a Multi-OMS Non-HA Environment

For instructions to upgrade your Enterprise Manager to 12c Release 4 (12.1.0.4) in a multi-OMS non-HA (or non-high availability) environment, see Section 5.5.

4.3 Upgrading Enterprise Manager in an HA Environment (Primary and Standby Sites)

Table 4-2 describes the steps for upgrading your primary as well as standby Enterprise Manager sites to 12c Release 4 (12.1.0.4) in an HA (or high availability) environment.

Table 4-2 Upgrading Primary and Standby Enterprise Manager Sites in an HA Environment

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.

Section 4.1

Step 3

Redeploy Standby Enterprise Manager

 
 

Re-create the standby OMS environment using either a Standby WebLogic Domain or storage replication.

IMPORTANT: If you use a Standby WebLogic Domain, then ensure that you re-create with a domain name that is different from the one used for the primary site and for the old standby site.

"Enterprise Manager Disaster Recovery" chapter of the Oracle Enterprise Manager Cloud Control Administrator's Guide for details.