This chapter describes the high-level process for upgrading your Enterprise Manager 12c Release 4 (12.1.0.4), 12c Release 3 (12.1.0.3), or 12c Release 2 (12.1.0.2) to 12c Release 5 (12.1.0.5).
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), 12c Release 3 (12.1.0.3), or 12c Release 4 (12.1.0.4), and then upgrade to 12c Release 5 (12.1.0.5).
For instructions to upgrade to 12c Release 2 (12.1.0.2), 12c Release 3 (12.1.0.3), or 12c Release 4 (12.1.0.4) refer to the Oracle Enterprise Manager Cloud Control Upgrade Guide for the respective release, available in the Enterprise Manager documentation library:
The Oracle Management Agent releases that are supported for Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) are 12c Release 5 (12.1.0.5), 12c Release 4 (12.1.0.4), 12c Release 3 (12.1.0.3), and 12c Release 2 (12.1.0.2). If you have any earlier releases of Oracle Management Agent, then before upgrading the Oracle Management Service to 12c Release 5 (12.1.0.5), make sure you upgrade your Oracle Management Agent to either 12c Release 4 (12.1.0.4), 12c Release 3 (12.1.0.3), or 12c Release 2 (12.1.0.2) using the Agent Upgrade Console present within the Enterprise Manager Cloud Control Console. For instructions, refer to Oracle Enterprise Manager Cloud Control Upgrade Guide.
If you want to take any additional preparatory steps for a successful upgrade, see My Oracle Support note 1682332.1.
If you want to see a list of known issues before starting the upgrade process, then see My Oracle Support note 2022505.1.
WARNING:
Do not upgrade 12c Release 4 (12.1.0.4), 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.
Table 4-1 describes the steps for upgrading your Enterprise Manager to 12c Release 4 (12.1.0.4) in a single-OMS or multi-OMS non-HA (or non-high availability) environment.
If you want to see a list of known issues before starting the upgrade process, then see My Oracle Support note 2022505.1.
Table 4-1 Upgrading Enterprise Manager Cloud Control to 12c Release 5 (12.1.0.5) in a Single-OMS Non-HA Environment
Step No. | Step | Procedure |
---|---|---|
Step 1 |
Prepare Yourself |
|
(a) |
Learn about the 1-System upgrade approach. |
|
(b) |
Review the important facts you need to know before you begin. |
|
Step 2 |
Upgrade Oracle Management Service and Oracle Management Repository |
|
(a) |
Meet the following prerequisites:
|
|
(b) |
If you have Oracle BI Publisher installed on the Enterprise Manager Cloud Control 12c installation that you are upgrading, then do one of the following:
As part of the upgrade to Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5), Oracle BI Publisher 11.1.1.7.0 with the latest bundle patches is automatically installed in the middleware home. However, although Oracle BI Publisher is installed by default, it is not configured or upgraded from the earlier version by default. Therefore, after upgrading to 12c Release 5 (12.1.0.5), you must manually configure Oracle BI Publisher. This configuration step also migrates all the reports from the old BI Publisher home to the new one. For instructions, see Step 4 (f). |
|
(c) |
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.
|
|
(d) |
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:
For example,
If there are snapshots created in a table, then the query displays the master table and the snapshot details. For example,
If there are snapshots, then drop them by running the following command as SYSMAN user:
For example,
|
|
(e) |
Ensure that you do not have any login or logoff triggers set in the Oracle Database that houses the Oracle Management Repository. To verify this, log into the database and run the following query:
If the query results in anything other than zero or no rows selected, then manually disable the triggers. After completing the upgrade, you can enable them again. To disable the triggers, run the following query:
For example,
|
|
(f) |
Enable auditing of the Delete Target operation.
|
|
(g) |
(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)
For Oracle Database 11g Release 2 (11.2.0.1)
For Oracle Database 11g Release 2 (11.2.0.2)
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 11g Release 2 (11.2.0.4) and 12c Release 1 (12.1.0.2) No patches required for these releases. 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. |
|
(h) |
[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:
To verify whether the emkey is copied, run the following command:
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". |
|
(i) |
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:
|
|
(j) |
Selectively skip some job type updates for reduced downtime of your Enterprise Manager system. While upgrading the Enterprise Manager system, job types are registered. As part of the job type registration process, all active executions corresponding to a job type are automatically upgraded to the newly registered version of the job type. This job type upgrade process is skipped for all queued and waiting executions, thereby reducing the overall downtime of the Enterprise Manager system. However, in some cases, the Enterprise Manager system might experience a considerable backlog, and if such a backlog is not cleared before initiating the upgrade, then the downtime of the Enterprise Manager system can be much longer. To circumvent this issue, you can selectively skip or postpone the upgrade of certain job types so that they are upgraded only after the downtime. To skip or postpone some job types from being upgraded, follow these steps:
|
|
(k) |
Shut down the OMS you are about to upgrade and also the other OMS instances that connect to it. IMPORTANT: If you are upgrading a multi-OMS environment using the software-only upgrade approach, then skip this step. You can stop the OMS instances after copying the software binaries as described in Section 5.3.1 or Section 5.4.1.
|
|
(l) |
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. IMPORTANT: If you are upgrading a multi-OMS environment using the software-only upgrade approach, then skip this step. You can stop the Management Agent after copying the software binaries as described in Section 5.3.1 or Section 5.4.1. |
|
(m) |
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:
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. |
|
Step 3 |
Upgrade Oracle Management Agent |
|
(a) |
Review the important facts you need to know before you begin upgrading the Management Agents. |
|
(b) |
Meet the prerequisites. |
|
(c) |
Ensure that you restart the Management Agent that you shut down in Step 2 (l). |
|
(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. |
|
Step 4 |
Perform Postupgrade Task |
|
(a) |
Perform postupgrade tasks. |
|
(b) |
Reconfigure Oracle WebLogic Server with custom certificates |
|
(c) |
Track the status of deferred data migration jobs. |
|
(d) |
Delete unwanted central agents |
|
(e) |
Upgrade Application Dependency and Performance (ADP) engines and JVM Diagnostics (JVMD) engines |
|
(f) |
As part of the upgrade to Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5), Oracle BI Publisher 11.1.1.7.0 with the latest patch set 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 5 (12.1.0.5). However, although Oracle BI Publisher is installed by default, it is not configured or upgraded from the earlier version by default.
|
For configuring the newly installed Oracle BI Publisher, see Oracle Enterprise Manager Advanced Installation and Configuration Guide. For upgrading Oracle BI Publisher and migrating the reports, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
(g) |
Delete old OMS home |
This section describes how you can upgrade your primary as well as standby Enterprise Manager sites to 12c Release 5 (12.1.0.5) in an HA (or high availability) environment. In particular, this section covers the following:
Table 4-2 describes the steps for upgrading your primary and standby OMS instances when the standby OMS is created using Storage Replication.
Note:
You do not have to remove the standby OMS as part of this procedure.Table 4-2 Upgrading Primary and Standby OMS Instances When the Standby OMS Is Created Using Storage Replication
Step No. | Step | Procedure |
---|---|---|
Step 1 |
Upgrade the Primary OMS |
|
Upgrade the primary Enterprise Manager site, both OMS and Management Agents. There will be some downtime as the primary OMS will go down during upgrade process. |
||
Step 2 |
Verify the New Middleware Home on the Standby Storage Server |
|
Contact your system administrator to make sure that the new middleware home is also replicated to the standby storage server. |
Table 4-3 describes the steps for upgrading your primary and standby OMS instances when the standby OMS is created using Standby WebLogic Domain.
Table 4-3 Upgrading Primary and Standby OMS Instances When the Standby OMS Is Created Using Standby WebLogic Domain
Step No. | Step | Procedure |
---|---|---|
Step 1 |
Remove the Standby OMS |
|
(a) |
Remove all additional standby OMS instances. |
To remove all additional standby OMS instances, see the section on removing additional standby OMS instances in Oracle Enterprise Manager Advanced Installation and Configuration Guide. |
(b) |
Remove the first standby OMS. |
To remove the first standby OMS, see the section on removing the first standby OMS in Oracle Enterprise Manager Advanced Installation and Configuration Guide. |
Step 2 |
Upgrade the Primary OMS |
|
Upgrade the primary Enterprise Manager site, both OMS and Management Agents. |
||
Step 3 |
Redeploy the Standby OMS |
|
Re-create the standby OMS environment using Standby WebLogic Domain. |
To re-create the standby OMS environment using Standby WebLogic Domain, see the chapter on disaster recovery in Oracle Enterprise Manager Cloud Control Administrator's Guide. |