Oracle® Enterprise Manager Cloud Control Upgrade Guide 12c Release 2 (12.1.0.2) Part Number E22625-11 |
|
|
PDF · Mobi · ePub |
To upgrade your Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) to Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2), follow these steps:
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.
Table 3-1 Upgrading Enterprise Manager Grid Control with 1-System Upgrade Approach
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. |
|
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.
|
|
(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:
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,
|
|
(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:
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". |
|
(e) |
Stop the OMS you are about to upgrade and also the other OMS instances that connect to it.
|
|
(f) |
Shut down the Management Agent that monitors the Management Services and Repository target. |
|
(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:
IMPORTANT: Upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS. |
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 |
(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. |
|
(b) |
Meet the 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 |
|
Step 4 |
Perform Postupgrade Task |
|
(a) |
Perform postupgrade tasks. |
|
(b) |
Track the status of deferred data migration jobs. |
|
(c) |
(Applicable if you upgrade from 12c Release 1 (12.1.0.1) released in February 2012, April 2012, and July 2012 to 12c Release 2 (12.1.0.2)) Upgrade the existing database plug-in revisions to the latest revision. |
|
(d) |
Upgrade Application Dependency and Performance (ADP) engines and JVM Diagnostics (JVMD) engines |