This chapter describes the high-level process for upgrading your Enterprise Manager Grid Control 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1) to Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) using different upgrade approaches. In particular, this chapter describes the following:
Table 9-1 describes the steps for upgrading your Enterprise Manager Grid Control 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1) to Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) with 1-system upgrade approach.
Table 9-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. |
|
(b) |
Review the important facts you need to know before you begin. |
|
Step 2 |
Perform Preupgrade Tasks |
|
(a) |
Apply the preupgrade console patch on all your OMS instances to get access to the Preupgrade Console. |
|
(b) |
Manually download the following software, and stage them to an accessible location:
|
|
(c) |
Provide information about the location of the software you manually downloaded and staged in Step 2 (b) |
|
(d) |
Analyze your environment to identify Oracle Management Agents (Management Agent) with valid and invalid inventory, check their upgradability status, and identify the problematic Management Agents. If a required software is missing, then repeat Step (b) and Step (c). |
|
(e) |
Meet the prerequisites for upgrading the Management Agents as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
|
Step 3 |
Upgrade Oracle Management Agent |
|
(a) |
Deploy and configure the software binaries of Oracle Management Agent 12c. |
|
(b) |
Generate a health report and check the readiness of the predeployed Management Agents. |
|
(c) |
Verify and sign off the health check report. |
|
(d) |
Switch over the old Management Agents to the newly deployed ones so that they can communicate with the upgraded Enterprise Manager Cloud Control. Note: If you have a large number of agents, then you can choose to upgrade one set of Oracle Management Agents in one attempt, and the next set in the subsequent attempt. In this case, you can repeat Step 3 (a) to Step 3 (d) for each attempt. |
|
Step 4 |
Upgrade Oracle Management Service and Oracle Management Repository |
|
(a) |
Meet the following prerequisites:
|
|
(b) |
On the Management Repository, meet the following prerequisites:
|
|
(c) |
(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. |
|
(d) |
Stop all running and scheduled deployment procedures in your existing Enterprise Manager system before upgrading the system. To verify this, run the following query, and note down the GUID of the running or scheduled deployment procedures.
To stop the running or scheduled deployment procedures, run the following query, and pass the GUID you noted down from the output of the preceding command:
|
|
(e) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed) Perform the following steps before the upgrade:
Perform the following steps after the upgrade:
|
|
(f) |
Copy the emkey from the existing OMS, either the Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), to the existing Management Repository. To do so, run the following command on the old OMS home you are trying to upgrade. The following command is applicable for both releases.
Note: When the following command is run on Enterprise Manager 11g Grid Control (11.1.0.1), you will be prompted for an admin password. 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". |
|
(g) |
Stop the OMS you are about to upgrade and also the other OMS instances that connect to it.
|
|
(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 do the following:
|
For single-OMS environment, see: For multi-OMS environment (with additional OMS instances), see Section 12.6 |
Step 5 |
Perform Postupgrade Task |
|
(a) |
If you have a Server Load Balancer (SLB) configured, then modify the settings of your monitors. |
|
(b) |
Check agent upgrade status. |
|
(c) |
Perform the general post-upgrade tasks. |
|
(d) |
Track the status of deferred data migration jobs. |
|
(e) |
Sign off agent migration process. |
|
(f) |
Sign off the upgrade process and exit the upgrade mode. |
|
(g) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
|
(h) |
Configure Oracle BI Publisher if required. |
Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide |
(i) |
Delete the old OMS home. |
Table 9-2 describes the steps for upgrading your Enterprise Manager Grid Control 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1) to Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) with 2-system upgrade approach.
Table 9-2 Upgrading Enterprise Manager Grid Control with 2-System Upgrade Approach
Step No. | Step | Procedure |
---|---|---|
Step 1 |
Prepare Yourself |
|
(a) |
Learn about the 2-System upgrade approach. |
|
(b) |
Review the important facts you need to know before you begin. |
|
Step 2 |
Perform Preupgrade Tasks |
|
(a) |
Apply the preupgrade console patch on all your OMS instances to get access to the Preupgrade Console. |
|
(b) |
Provide information about the host where you plan to upgrade your existing OMS. |
|
(c) |
Manually download the following software, and stage them to an accessible location:
|
|
(d) |
Provide information about the location of the software you manually downloaded and staged in Step 2 (c) |
|
(e) |
Analyze your environment to identify Oracle Management Agents (Management Agent) with valid and invalid inventory, check their upgradability status, and identify the problematic Management Agents. If a required software is missing, then repeat Step 2 (c) and Step 2 (d). |
|
(f) |
Meet the prerequisites for upgrading the Management Agents as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
|
Step 3 |
Upgrade Oracle Management Service and Oracle Management Repository Note: Optionally, you can choose to deploy and configure your Oracle Management Agents before upgrading the Oracle Management Service and Oracle Management Repository. In this case, perform Step 4 (a) before Step 3 (a) to Step 3 (o). |
|
(a) |
On the remote host where you plan to install Enterprise Manager Cloud Control, meet the following prerequisites:
|
|
(b) |
Stop all running and scheduled deployment procedures in your existing Enterprise Manager system before upgrading the system. To verify this, run the following query, and note down the GUID of the running or scheduled deployment procedures.
To stop the running or scheduled deployment procedures, run the following query, and pass the GUID you noted down from the output of the preceding command:
|
|
(c) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed) Perform the following steps before the upgrade:
Perform the following steps after the upgrade:
|
|
(d) |
Copy the emkey from the existing OMS, either the Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), to the existing Management Repository before creating a backup of the Management Repository. To do so, run the following command on the old OMS home you are trying to upgrade. The following command is applicable for both releases.
Note: When the following command is run on Enterprise Manager 11g Grid Control (11.1.0.1), you will be prompted for an admin password. 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) |
(Only if your old Enterprise Manager system has Oracle Software Library configured) If you have Oracle Software Library (Software Library) configured, then back up each of the configured Software Library directories to a location accessible from the remote host where you plan to install Enterprise Manager Cloud Control. The location to which you back up the directories is required for reconfiguring the Software Library [as described in Step 5 (b)] once you install Enterprise Manager Cloud Control. For example, if your Software Library was configured in |
|
(f) |
Clone (or back up) your existing database, which houses the Management Repository, using the RMAN utility, to a host that can be either a completely new host or the host where your existing OMS is running. Choose to clone (or back up) the repository on the host where your existing OMS is running only if you have sufficient space to accommodate it. Then, restore it and create a new database instance out of it so that the repository configured in it can be upgraded. Note:
|
|
(g) |
On the cloned (or backed up) Management Repository, meet the following prerequisites:
|
|
(h) |
(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. |
|
(i) |
Ensure that the character set in the cloned (or backed up) Management Repository is the same as the one in the original Management Repository. If they are different, you will see the following error: ERROR emschema.wpxegn6m8wkg - ERROR:ORA-06502: PL/SQL: numeric or value error: character to number conversion error ORA-06512: at "SYSMAN.EM_CRYPTO", line 62 ORA-06512: at "SYSMAN.EM_CRYPTO", line 229 ORA-06512: at line 1 ORA-06512: at line 24 To verify if the character set is the same, run the following query on the Management Repository:
If the character set is not the same, then make them identical. |
|
(j) |
Remove the emkey from the old Management Repository by running the following command from the old OMS home, either Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or Enterprise Manager 11g Grid Control Release 1 (11.1.0.1):
|
|
(k) |
Provide the date and time when the Management Repository was cloned (or backed up). Note: Any Management Agent or target added to the existing Enterprise Manager system after cloning (or backing up) the Management Repository will not be upgraded and will need to be manually added to the upgraded Enterprise Manager system. To identify the targets that need to be manually added to the upgraded system, see the diff report as described in .Section 13.9. |
|
(l) |
If you have a Server Load Balancer (SLB) configured, then configure the settings of your monitors and keep the SLB ready. |
|
(m) |
Install Enterprise Manager Cloud Control on the remote host and upgrade the Management Repository in the database you cloned (or backed up) in Step 3 (f). You can choose to install 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 that states that you cannot upgrade your OMS because the host on which you are performing the 2-system upgrade does not match with the host name you have entered in the Preupgrade Console, go to the Preupgrade Console and provide the correct host name. (Note: If you had chosen to deploy your Management Agents before upgrading the OMS, and if you see this error, fix the error in the Preupgrade Console, and then deploy your Management Agents again, before upgrading the OMS.) If you see an error message stating that you have not copied the emkey, then do the following: For 11g Release 1 (11.1.0.1)
For 10g Release 5 (10.2.0.5)
(Note: If you had chosen to deploy your Management Agents before upgrading the OMS, and if you see this error, then after running the previous command, make sure you deploy all the Management Agents again. However, after running the command, and before re-deploying the Management Agents, Oracle recommends that you run the installer to ensure that the error about emkey does not reoccur.) |
For single-OMS environment, see: For multi-OMS environment (with additional OMS instances), see Section 12.6 |
(n) |
If your database domain name has any characters other than A-Z (letters), 0-9 (numerals), _ (underscore), # (hash), $ (dollar),. (period), or @ (at the rate), then the Run Presync step of the switchover operation might fail, and you will see the following error in the ORA-20000: Found exception Error Message :ORA-02083: database name has illegal character '-' Error Number ;-2083 To avoid this issue, as a prerequisite, follow the instructions outlined in Section L.1. If the database domain name has an illegal character, such as a hyphen, then correct it. |
|
(o) |
Link the earlier release of the Management Repository with the upgraded Management Repository. |
|
Step 4 |
Upgrade Oracle Management Agent |
|
(a) |
Deploy and configure the software binaries of Oracle Management Agent 12c. Note: After deploying and configuring the Management Agents, do not make any configuration changes, for example, the metric thresholds, job definitions, templates, and so on, in the old Management Repository. If you do, then those changes will not be carried over when you switch over to the new Management Agents; the only way to transfer the changes is to reconfigure the new Management Agents. For information about reconfiguring them, see the note in Step (6) of Section 11.1.2. |
|
(b) |
Generate a health report and check the readiness of the predeployed Management Agents. |
|
(c) |
Verify and sign off the health check report. |
|
(d) |
Switch over the old Management Agents to the newly deployed ones so that they can communicate with the upgraded Enterprise Manager Cloud Control. Note: If you have a large number of agents, then you can choose to upgrade one set of Oracle Management Agents in one attempt, and the next set in the subsequent attempt. In this case, you can repeat Step 4 (a) to Step 4 (d) for each attempt. |
|
Step 5 |
Perform Postupgrade Task |
|
(a) |
Verify the host on which you installed Enterprise Manager Cloud Control. |
|
(b) |
(Only if your old Enterprise Manager had Software Library configured) Reconfigure the Software Library in Enterprise Manager Cloud Control so that it is independent of the Software Library configured for the old Enterprise Manager system. |
|
(c) |
Secure the central agent [the Management Agent installed by default with the new OMS you installed as part of Step 3 (m)]. |
|
(d) |
Check the agent upgrade status. |
|
(e) |
Perform the general post-upgrade tasks. |
|
(f) |
Track the status of deferred data migration jobs. |
|
(g) |
Track the status of accrued data migration jobs. |
|
(h) |
Generate diff reports to identify all configuration or setup-related changes that were manually made to the earlier release of the Enterprise Manager system while it was being upgraded. |
|
(i) |
View a list of targets that are currently inactive in the upgraded Enterprise Manager system. |
|
(j) |
Sign off agent migration process. |
|
(k) |
Sign off the upgrade process and exit the upgrade mode. |
|
(l) |
Delete unwanted central agents. |
|
(m) |
(Optional) Monitor the targets that were monitored by the deleted central agent. |
|
(n) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
|
(o) |
Configure Oracle BI Publisher if required. |
Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide |
(p) |
Delete the old OMS home. |
Table 9-3 describes the steps for upgrading your Enterprise Manager Grid Control 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1) to Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) with 1-system upgrade approach on a different host.
Table 9-3 Upgrading Enterprise Manager Grid Control with 1-System Upgrade Approach on a Different Host
Step No. | Step | Procedure |
---|---|---|
Step 1 |
Prepare Yourself |
|
(a) |
Learn about the 1-System upgrade approach on a different host. |
|
(b) |
Review the important facts you need to know before you begin. |
|
Step 2 |
Perform Preupgrade Tasks |
|
(a) |
Apply the preupgrade console patch on all your OMS instances to get access to the Preupgrade Console. |
|
(b) |
Provide information about the host where you plan to upgrade your existing OMS. |
|
(c) |
Manually download the following software, and stage them to an accessible location:
|
|
(d) |
Provide information about the location of the software you manually downloaded and staged in Step 2 (c). |
|
(e) |
Analyze your environment to identify Oracle Management Agents (Management Agent) with valid and invalid inventory, check their upgradability status, and identify the problematic Management Agents. If a required software is missing, then repeat Step (c) and Step (d). |
|
(f) |
Meet the prerequisites for upgrading the Management Agents as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
|
Step 3 |
Upgrade Oracle Management Agent |
|
(a) |
Deploy and configure the software binaries of Oracle Management Agent 12c. |
|
(b) |
Generate a health report and check the readiness of the predeployed Management Agents. |
|
(c) |
Verify and sign off the health check report. |
|
(d) |
Switch over the old Management Agents to the newly deployed ones so that they can communicate with the upgraded Enterprise Manager Cloud Control. Note: If you have a large number of agents, then you can choose to upgrade one set of Oracle Management Agents in one attempt, and the next set in the subsequent attempt. In this case, you can repeat Step 3 (a) to Step 3 (d) for each attempt. |
|
Step 4 |
Upgrade Oracle Management Service and Oracle Management Repository |
|
(a) |
On the remote host where you plan to install Enterprise Manager Cloud Control, meet the following prerequisites:
|
|
(b) |
On the Management Repository, meet the following prerequisites:
|
|
(c) |
(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. |
|
(d) |
Stop all running and scheduled deployment procedures in your existing Enterprise Manager system before upgrading the system. To verify this, run the following query, and note down the GUID of the running or scheduled deployment procedures.
To stop the running or scheduled deployment procedures, run the following query, and pass the GUID you noted down from the output of the preceding command:
|
|
(e) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed) Perform the following steps before the upgrade:
Perform the following steps after the upgrade:
|
|
(f) |
Copy the emkey from the existing OMS, either the Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), to the existing Management Repository. To do so, run the following command on the old OMS home you are trying to upgrade. The following commands are applicable for both releases.
Note: When the following command is run on Enterprise Manager 11g Grid Control (11.1.0.1), you will be prompted for an admin password. 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". |
|
(g) |
If you have a Server Load Balancer (SLB) configured, then configure the settings of your monitors and keep the SLB ready. |
|
(h) |
If your old Enterprise Manager has Oracle Software Library (Software Library) configured on a shared, NFS-mounted drive, then ensure that the shared drive is accessible from the remote host where you plan to install Enterprise Manager Cloud Control. However, if the Software Library is configured on the local file system where the existing, earlier release of Enterprise Manager is running, then copy the Software Library to the remote host where you plan to install Enterprise Manager Cloud Control, in the same directory path as the one maintained in the old Enterprise Manager system. |
|
(i) |
Install Enterprise Manager Cloud Control on the remote host and upgrade the Management Repository in the existing database. |
|
Step 5 |
Perform Postupgrade Task |
|
(a) |
Secure the central agent [the Management Agent installed by default with the new OMS you installed as part of Step 4 (i)]. |
|
(b) |
Check the agent upgrade status. |
|
(c) |
Perform the general post-upgrade tasks. |
|
(d) |
Track the status of deferred data migration jobs. |
|
(e) |
Sign off agent migration process. |
|
(f) |
Sign off the upgrade process and exit the upgrade mode |
|
(g) |
Deleted unwanted central agents. |
|
(h) |
(Optional) Monitor the targets that were monitored by the deleted central agent. |
|
(i) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
|
(j) |
Configure Oracle BI Publisher if required. |
Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide |
(k) |
(Optional) Delete the old OMS home. |