Oracle® Enterprise Manager Cloud Control Upgrade Guide 12c Release 2 (12.1.0.2) Part Number E22625-11 |
|
|
PDF · Mobi · ePub |
This part describes the high-level process you must follow for each of the upgrade approaches. Oracle strongly recommends you to read the chapters covered in this part, and consider this part to be the starting point for upgrading your existing Enterprise Manager system. In particular, this chapter describes the following:
To upgrade your Enterprise Manager Grid Control to Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2) with 1-system upgrade approach, follow these steps:
Table 7-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 10g Release 5 (10.2.0.5) and 11g Release 1 (11.1.0.1) to 12c Release 2 (12.1.0.2) |
(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 instance 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. |
|
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. |
Generating Health Report of Deployed Oracle Management Agents |
(c) |
Verify and sign off the health check report. |
Verifying and Signing Off the Health Report of Deployed Oracle Management Agents |
(d) |
Switch over the old Management Agents to the newly deployed ones so that they can communicate with 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. |
|
(e) |
If you have a Server Load Balancer (SLB) configured, then modify the settings of your monitors. |
|
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) |
Stop all running and scheduled deployment procedures in your existing Enterprise Manager system before upgrading the system. |
|
(d) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
|
(e) |
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". |
|
(f) |
Stop the OMS you are about to upgrade and also the other OMS instances that connect to it.
|
|
(g) |
Shut down the Management Agent that monitors the Management Services and Repository target. |
|
(h) |
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:
|
Upgrading with 1-System Upgrade Approach in Graphical Mode, Upgrading with 1-System Upgrade Approach in Silent Mode, Upgrading in Software-Only Mode with 1-System Upgrade Approach in Graphical Mode, or Upgrading in Software-Only Mode with 1-System Upgrade Approach in Silent Mode |
Step 5 |
Perform Postupgrade Task |
|
(a) |
Perform the general post-upgrade tasks. |
|
(b) |
Track the status of deferred data migration jobs. |
|
(c) |
Sign off agent migration process. |
|
(d) |
Update the incident rules for metrics associated with the OMS. |
|
(e) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
To upgrade your Enterprise Manager Grid Control to Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2) with 2-system upgrade approach, follow these steps:
Table 7-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. |
Upgrading 10g Release 5 (10.2.0.5) and 11g Release 1 (11.1.0.1) to 12c Release 2 (12.1.0.2) |
(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. |
|
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 (l). |
|
(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. |
|
(c) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
|
(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 3 (l)] once you install Enterprise Manager Cloud Control. For example, if your Software Library was configured in |
|
(f) |
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 back up the repository on the host where your existing OMS is running only if you have sufficient space to accommodate it. Then, create a new database instance out of it so that the repository configured in it can be upgraded. Note: - Before backing up the database, ensure that you stop all the running and scheduled deployment procedures in your existing Enterprise Manager system. - Oracle recommends using the RMAN utility to back up the database. - If you back up the database using DBCA, then ensure that you unlock all the user accounts, except for MGMT_VIEW user, before installing Enterprise Manager Cloud Control. - Do not back up the repository using the DB cloning feature in the Enterprise Manager console. If you do, then you will not see the cloned database discovered in the Enterprise Manager console. - Do not backup while you are in the daylight saving window. - Any Management Agent or target added to the existing Enterprise Manager system after 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 . Generating and Viewing Diff Reports. |
|
(g) |
On the backed up Management Repository, meet the following prerequisites:
|
|
(h) |
Ensure that the character set in the 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. |
|
(i) |
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):
|
|
(j) |
Provide the date and time when the Management Repository was backed up. Note: Any Management Agent or target added to the existing Enterprise Manager system after 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 . Generating and Viewing Diff Reports. |
|
(k) |
Install Enterprise Manager Cloud Control on the remote host and upgrade the Management Repository in the database you 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 Prepgrade 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 dploy 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.) |
Upgrading with 2-System Upgrade Approach in Graphical Mode, Upgrading with 2-System Upgrade Approach in Silent Mode, Upgrading in Software-Only Mode with 2-System Upgrade Approach in Graphical Mode, or Upgrading in Software-Only Mode with 2-System Upgrade Approach in Silent Mode |
(l) |
Link the ealier release of the Management Repository with the upgraded Management Repository. |
|
(m) |
(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. |
|
Step 4 |
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. |
Generating Health Report of Deployed Oracle Management Agents |
(c) |
Verify and sign off the health check report. |
Verifying and Signing Off the Health Report of Deployed Oracle Management Agents |
(d) |
Switch over the old Management Agents to the newly deployed ones so that they can communicate with 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) |
Check the agent upgrade status |
|
(b) |
Perform the general post-upgrade tasks. |
|
(c) |
Track the status of deferred data migration jobs. |
|
(d) |
Track the status of accrued data migration jobs. |
|
(e) |
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. |
|
(f) |
View a list of targets that are currently inactive in the upgraded Enterprise Manager system. |
Viewing Inactive Targets in the Upgraded Enterprise Manager System |
(g) |
Sign off agent migration process. |
|
(h) |
Update the incident rules for metrics associated with the OMS. |
|
(i) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
To upgrade your Enterprise Manager Grid Control to Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2) with 1-system upgrade approach on a different host, follow these steps:
Table 7-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. |
Upgrading 10g Release 5 (10.2.0.5) and 11g Release 1 (11.1.0.1) to 12c Release 2 (12.1.0.2) |
(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. |
|
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. |
Generating Health Report of Deployed Oracle Management Agents |
(c) |
Verify and sign off the health check report. |
Verifying and Signing Off the Health Report of Deployed Oracle Management Agents |
(d) |
Switch over the old Management Agents to the newly deployed ones so that they can communicate with 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) |
Stop all running and scheduled deployment procedures in your existing Enterprise Manager system before upgrading the system. |
|
(d) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|
|
(e) |
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". |
|
(f) |
If you have a Server Load Balancer (SLB) configured, then make changes to your monitors. |
|
(g) |
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 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. |
|
(h) |
Install Enterprise Manager Cloud Control on the remote host and upgrade the Management Repository in the existing database. |
Upgrading OMS and Management Repository for 1-System on Different Host Approach |
Step 5 |
Perform Postupgrade Task |
|
(a) |
Check the agent upgrade status. |
|
(b) |
Perform the general post-upgrade tasks. |
|
(c) |
Track the status of deferred data migration jobs. |
|
(d) |
Sign off agent migration process. |
|
(e) |
Update the incident rules for metrics associated with the OMS. |
|
(f) |
(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)
|