This chapter describes the high-level process for upgrading your Enterprise Manager 13cRelease 1, 12c Release 5 (184.108.40.206), or 12c Release 4 (220.127.116.11), to 13c Release 2.
In particular, this chapter covers the following:
If you have configured Oracle BI Publisher with 12c Release 3 (18.104.22.168), then you cannot directly upgrade to 13c Release 2. You must first upgrade to 12c Release 4 (22.214.171.124) or 12c Release 5 (126.96.36.199), or 13c Release 1, and then upgrade to 13c Release 2.
If you have Oracle Management Service (OMS) 12c Release 1 (188.8.131.52) [with or without Bundle Patch 1], 12c Release 2 (184.108.40.206), or any pre-12c release such as 10g or 11g, then first upgrade it to either 12c Release 4 (220.127.116.11), 12c Release 5 (18.104.22.168) or 13c Release 1.
The Oracle Management Agent (Management Agent) releases that are supported for Enterprise Manager Cloud Control 13c Release 2 are 13c Release 2, 13c Release 1, 12c Release 5 (22.214.171.124), and 12c Release 4 (126.96.36.199). Therefore, if you have any earlier releases of Management Agent, then before upgrading the OMS to 13c Release 2, make sure you upgrade your Management Agent to either 12c Release 4 (188.8.131.52), 12c Release 5 (184.108.40.206), or 13c Release 1 using the Agent Upgrade Console present within the Enterprise Manager Cloud Control Console.
To upgrade your Enterprise Manager Cloud Control 13c Release 1, 12c Release 5 (220.127.116.11), or 12c Release 4 (18.104.22.168), to 13c Release 2 in a single-OMS or multi-OMS non-HA (non-high availability) environment, follow these steps:
[Optional] Prepare Yourself for the UpgradeFamiliarize yourself with the upgrade process, understand the implications, and review the important facts related to upgrade.
|Upgrade Facts||Upgrade Facts||Upgrade Facts|
Upgrade Your OMS, Repository, Central Agent, and Plug-ins
Upgrade of your Enterprise Manager system is a three-step process - you have to first meet the prerequisites; then run the installer to upgrade the OMS, the repository, the central agent, and the plug-ins; and then perform the postupgrade tasks. The installer guides you through the upgrade process, and upgrades not only the OMS but also the repository, the central agent, and the existing plug-ins. In addition to upgrading your existing plug-ins, you can also deploy additional new plug-ins of your choice.
Step 1: Meet the Prerequisites
Before starting the upgrade, meet the upgrade prerequisites so that your environment is ready for the upgrade.
Step 2: Upgrade Your OMS, Repository, and Plug-ins
Run the installer and select the upgrade option to upgrade your Enterprise Manager system.
There are various ways in which you can upgrade the OMS and the Management Repository, either in interactive mode using the installer, in silent mode using a response file, or in software-only mode using the installer or a response file. This section lists only the steps of the interactive mode using the installer.
|Upgrading Steps||Upgrading Steps||Upgrading Steps|
Step 5: Selecting the Installation Type
Step 9: Deploying Additional Plug-ins
Step 12: Configuring the Ports
Step 13: Reviewing the Upgrade Details
Step 14: Monitoring the Upgrade Progress
Step 15: Ending the Upgrade
Step 17: Upgrading the Management Agents
Step 3: Upgrade Your Central Agent
After Upgrading the OMS, immediately upgrade the central agent. A central agent can be upgraded only using the Agent Upgrade Console.
Oracle recommends that you upgrade your central agent immediately after upgrading your OMS instances. However, for some reason if you are unable to upgrade your central agent immediately after upgrading the OMS instances, then ensure that you apply the JDK 1.6u95 patch on your central agent. Otherwise, the targets of the GC WLS domain will not be monitored in the Enterprise Manager Cloud Control Console. This issue will not occur once the central agent is upgraded.
Step 4: Perform Postupgrade Tasks
Perform the postupgrade tasks to verify that the upgrade was successful.
|Post Upgrade Task||Post Upgrade Task||Post Upgrade Task|
Upgrade Your Standalone Agents
Your upgrade is complete only after you upgrade all your standalone agents. Upgrade of your standalone agents is a three-step process - you have to first upgrade one of the standalone agents using the Agent Upgrade Console, then create a gold image out of that, and then upgrade the rest of them using that gold image.
Step 1: Upgrade a Standalone Agent
As a prerequisite, first upgrade one of your standalone agents.
Step 2: Create an Agent Gold Image
Create an agent gold image and an image version. Set it to the current version, and subscribe the standalone agents to this version.
Step 3: Update the Standalone Agents
Using the agent gold image, update all other standalone agents.
To upgrade your primary and standby OMS instances where the standby OMS is created using Storage Replication, follow these steps:
You do not have to remove the standby OMS as part of this procedure.