2 Getting Started with Upgrading to Enterprise Manager Cloud Control 13c Release 4

This chapter describes the high-level process for upgrading to Enterprise Manager 13c Release 4.

In particular, this chapter covers the following:

• Upgrading to 13c Release 4 in a Single-OMS or Multi-OMS Non-HA Environment

• Upgrading to 13c Release 4 in an HA Environment (Primary and Standby OMS Instances Where the Standby OMS Is Created Using Storage Replication)

Important:

• The Oracle Management Service (OMS) releases that are supported for Enterprise Manager Cloud Control 13c Release 4 are 13c Release 3 and 13c Release 2. Therefore, if you have any earlier releases of the OMS, first you need to upgrade it to 13c Release 2 or 13c Release 3 and then you can upgrade to 13c Release 4.

• The Oracle Management Agent (Management Agent) releases that are supported for Enterprise Manager Cloud Control 13c Release 4 are 13c Release 3 and 13c Release 2. Therefore, if you have any earlier releases of Management Agent, before upgrading the OMS to 13c Release 4, make sure you upgrade your Management Agent to either 13c Release 2 or 13c Release 3 using the Agent Upgrade Console present within the Enterprise Manager Cloud Control Console.

Upgrading to 13c Release 4 in a Single-OMS or Multi-OMS Non-HA Environment

Follow the steps below to upgrade to Enterprise Manager Cloud Control 13c Release 4 in a single-OMS or multi-OMS non-HA (non-high availability) environment:

[Optional] Prepare Yourself for the Upgrade Familiarize yourself with the upgrade process, understand the implications, and review the important facts related to upgrade.

Upgrade Facts	Upgrade Facts	Upgrade Facts
Supported OMS Environments for Upgrading to Enterprise Manager Cloud Control 13c Release 4 Supported Upgrade Paths and Supported Upgrade Approaches for Upgrading to Enterprise Manager Cloud Control 13c Release 4 Supported Platforms for Upgrading to Enterprise Manager Cloud Control 13c Release 4 Upgrade Scope Offered for Upgrading to Enterprise Manager Cloud Control 13c Release 4 Components Upgraded or Installed As Part of the Upgrade to Enterprise Manager Cloud Control 13c Release 4 Ports Used by an Upgraded Enterprise Manager Cloud Control 13c	Upgrading Oracle BI Publisher While Upgrading to Enterprise Manager Cloud Control 13c Release 4 Upgrading Plug-Ins While Upgrading to Enterprise Manager Cloud Control 13c Release 4 Status of Oracle Software Library After Upgrading to Enterprise Manager Cloud Control 13c Release 4 Status of Connectors After Upgrading to Enterprise Manager Cloud Control 13c Release 4 Custom Certificates Status When Upgrading to Enterprise Manager Cloud Control 13c Release 4 XML DB Feature in the Database After Upgrading to Enterprise Manager Cloud Control 13c Release 4	Manually Restarting the OMS and the Management Agent After Upgrading to Enterprise Manager Cloud Control 13c Release 4 Enabling Force Logging When Oracle Data Guard Is Configured with the Standby Database (Management Repository) Before Upgrading to Enterprise Manager Cloud Control 13c Release 4 Wizards or Consoles Used for Upgrading to Enterprise Manager Cloud Control 13c Release 4

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.

Prerequisites	Prerequisites	Prerequisites
Hardware, Software, and Platform Requirements Supported Database Release Requirements Database Patch Requirements Optimizer Adaptive Features Disabling Requirements Port Requirements Customization Removal Requirements	Oracle BI Publisher Shutdown Requirements Database Service Instance Creation Request Verification Requirements Repository Table Snapshot Verification Requirements Logon and Logoff Trigger Setting Verification Requirements Delete Target Operation Auditing Requirements Selectively Skipping Some Job Type Updates for Reduced Downtime of Your Enterprise Manager System EMKEY Copy Requirements Certificate Key Strength Requirements	Out-of-Box Memory Settings Backup Requirements Prerequisite Check and Environment Validation Requirements OMS Backup Requirements OMS Shutdown Requirements Management Agent Shutdown Requirements Management Agent Proxy Removal Requirements

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 1: Invoking the Enterprise Manager Cloud Control Installer in GUI Mode Step 2: Enabling Oracle Configuration Manager Step 3: Applying the Latest Software Updates Step 4: Running the Prerequisite Checks and Validating the Environment Step 5: Selecting the Installation Type Step 6: Configuring a Middleware Home and Validating the Host Name	Step 7: Providing Database Connection Details Step 8: Upgrading or Migrating Plug-ins, or Deploying Dependent Plug-ins Step 9: Deploying Additional Plug-ins Step 10: Extending the Existing WebLogic Server Domain Step 11: Configuring the Shared Locations for Oracle BI Publisher Step 12: Configuring the Ports	Step 13: Reviewing the Upgrade Details Step 14: Monitoring the Upgrade Progress Step 15: Ending the Upgrade Step 16: Upgrading the Additional OMS Instances 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 at least you apply the JDK 1.7u111 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.

• Prerequisites for Upgrading Central Agents or Standalone Management Agents to 13c Release 4 Using the Agent Upgrade Console or EM CLI

• Upgrading Central Agents or Standalone Management Agents to 13c Release 4 Using the Agent Upgrade Console

• After Upgrading Central Agents or Standalone Management Agents to 13c Release 4 Using the Agent Upgrade Console or EM CLI

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
Redoing the Custom Configurations Reconfiguring Oracle WebLogic Server with Custom Certificates Restarting the Management Agent After Upgrading an Additional OMS Tracking the Status of Deferred Data Migration Jobs	Upgrading Oracle Exalogic System Targets (Optional) Deleting the Old OMS Home Deleting Unwanted Central Agents of 10g or 11g Release Migrating the SYSMAN Schema to a Database Configured with CDB and PDB	Managing JVM Targets That Continue to Be Associated with the Old OMS Enabling Upgrade of Job Types That Were Skipped Before the Upgrade of the Enterprise Manager System

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.

• Prerequisites for Upgrading Central Agents or Standalone Management Agents to 13c Release 4 Using the Agent Upgrade Console or EM CLI

• Upgrading Central Agents or Standalone Management Agents to 13c Release 4 Using the Agent Upgrade Console

• After Upgrading Central Agents or Standalone Management Agents to 13c Release 4 Using the Agent Upgrade Console or EM CLI

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.

1. Creating an Agent Gold Image Using Gold Agent Images Home Page

2. Creating an Agent Gold Image Version Using the Gold Agent Images Home Page

3. Setting a Particular Agent Gold Image Version as the Current Version Using Gold Agent Images Home Page

4. Subscribing Management Agents to an Agent Gold Image Using Gold Agent Images Home Page

Step 3: Update the Standalone Agents

Using the agent gold image, update all other standalone agents.

Updating Standalone Management Agents Using Agent Gold Image Version Using Gold Agent Images Home Page

Upgrading to 13c Release 4 in an HA Environment (Primary and Standby OMS Instances Where the Standby OMS Is Created Using Storage Replication)

Follow the steps below to upgrade your primary and standby OMS instances where the standby OMS is created using Storage Replication:

1. 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. For instructions, see Upgrading to 13c Release 4 in a Single-OMS or Multi-OMS Non-HA Environment.
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.

Note:

You do not have to remove the standby OMS as part of this procedure.