Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 1 (12.1.0.1)
E22625-09
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

2 Introduction to Upgrade Approaches

With the option of deploying Enterprise Manager across the enterprise and in any number of permutations, upgrading the entire environment becomes a very complex activity involving updating of software and configurations in different levels (tiers) located in different hosts. In addition, there are challenges of upgrading the environment with near-zero downtime or minimal monitoring loss.

Considering these challenges, Oracle offers upgrade options that not only offer the flexibility to select the approach that best suits your requirement but also aim at simplifying the entire upgrade operation with the intent of making it seamless and error-free.

This chapter provides an overview of these upgrade approaches. In particular, this chapter covers the following:

Overview of Upgrade Approaches

Oracle offers the following upgrade approaches to upgrade your existing Enterprise Manager system:

Table 2-1 lists the differences between the three upgrade approaches:

Table 2-1 Differences Between the Upgrade Approaches

1-System Upgrade Approach 2-System Upgrade Approach 1-System Upgrade Approach on Different Host

Involves predeployment and switch over of Management Agents prior to upgrading the OMS and the Management Repository, unlike the traditional approach that focussed on upgrading only the OMS and the Management Repository.

Resembles fresh installation.

Resembles fresh installation.

Requires a reasonable downtime.

(Essentially, the downtime lasts from the time you switch over the Management Agents till the time you upgrade the OMS.)

Requires minimum or zero downtime.

Requires a reasonable downtime.

Upgrades to Enterprise Manager Cloud Control on the same host where your earlier release of Enterprise Manager is running.

Installs Enterprise Manager Cloud Control on a host that is different from the host where your existing Enterprise Manager system is running.

Installs Enterprise Manager Cloud Control on a host different from where the existing Enterprise Manager is running, but upgrades the Management Repository in the existing database itself.

Does not require an additional hardware resource because it upgrades on the same host.

Requires an additional hardware resource because it installs on a different host.

Requires an additional hardware resource because it installs on a different host.

Existing Enterprise Manager system must be shut down so that the configuration information can be copied and carried over to the upgraded Enterprise Manager system.

Existing Enterprise Manager system can continue to run until you switch over all your earlier releases of Management Agents to the newly upgraded environment.

Existing Enterprise Manager system must be shut down so that the configuration information can be copied and carried over to the new system.

Management Agents must be deployed and configured before upgrading the OMS and the Management Repository.

Management Agents can be deployed and configured before or after upgrading the OMS and the Management Repository.

Management Agents must be deployed and configured before upgrading the OMS and the Management Repository.

Management Agents can be deployed and configured in an incremental or phased manner, that is, in groups.

Management Agents can be deployed and configured in an incremental or phased manner, that is, in groups.

Management Agents can be deployed in an incremental or phased manner, that is, in groups.

Management Agents must be switched over before upgrading the OMS and the Management Repository.

Management Agents must be switched over after upgrading the OMS and the Management Repository.

Management Agents must be switched over before upgrading the OMS and the Management Repository.

Upgrades the Management Repository in the existing, certified database.

Upgrades the Management Repository in the backed up database. Therefore, as a prerequisite, you are required to back up your existing Oracle Database.

Upgrades the Management Repository in the existing, certified database.

Requires no changes to the ports and firewall settings. The upgraded Management Agents and the OMS use the same ports used earlier.

Requires some changes to the ports and firewall settings. The upgraded Management Agents use the same ports used earlier. However, the Management Agent and the OMS installed on the remote host might use new ports.

In a multi-OMS environment, if you have a Server Load Balancer (SLB), then you can either open up new ports for the new Management Agent and the OMS in the same SLB, or configure a completely new SLB for them.

Requires some changes to the ports and firewall settings. The upgraded Management Agents use the same ports used earlier. However, the Management Agent and the OMS installed on the remote host might use new ports.

In a multi-OMS environment, if you have a Server Load Balancer (SLB), then you can either open up new ports for the new Management Agent and the OMS in the same SLB, or configure a completely new SLB for them.

All deployment procedures must be finished before the upgrade is started. Otherwise, the scheduled procedures will be canceled, and you will have to re-create them.

All deployment procedures must be finished before the upgrade is started. Otherwise, the scheduled procedures will be canceled, and you will have to re-create them.

All deployment procedures must be finished before the upgrade is started. Otherwise, the scheduled procedures will be canceled, and you will have to re-create them.

Running jobs will be aborted at the start of the downtime.

Running jobs will continue to run on the existing Enterprise Manager system after the start of the backup. In Enterprise Manager Cloud Control, these jobs will appear to be aborted or failed.

Running jobs will be aborted at the start of the downtime.

Scheduled jobs will run after the downtime is over if their grace period allows them. Otherwise, they will be skipped.

Scheduled jobs will run on the existing Enterprise Manager system from the time of the backup until the point where the Management Agent for that target is migrated to Enterprise Manager Cloud Control. Once the Management Agent is migrated, the jobs will run in Enterprise Manager Cloud Control.

Scheduled jobs will run after the downtime is over if their grace period allows them. Otherwise, they will be skipped.

Repeating jobs will run at their next scheduled time after the downtime. If repeating jobs fall within the downtime, they may be skipped.

Repeating jobs will continue to run according to their schedule on the existing Enterprise Manage system. Once the Management Agent is migrated, subsequent runs will be in Enterprise Manager Cloud Control.

Repeating jobs will run at their next scheduled time after the downtime. If repeating jobs fall within the downtime, they may be skipped.



Note:

Jobs run either in the existing Enterprise Manager system or in Enterprise Manager Cloud Control, and not on both systems. The true status of a job must be viewed only on the system where it actually ran. For more information, see Appendix C. Also, job executions with multiple targets will not run on either system unless all Management Agents for all targets are migrated at the same time.

Overview of Upgrade Utilities

To enable you to select one of the upgrade approaches, orchestrate the entire upgrade operation seamlessly, and also track the post-upgrade activities such as the data migration processes, Oracle offers the following utilities:

Preupgrade Console

The Enterprise Manager 12c Upgrade Console acts as the primary user interface and is indeed the starting point for upgrading your Enterprise Manager 10g Grid Control Release 5 (10.2.0.5.0) or Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0) to Enterprise Manager Cloud Control.

The Enterprise Manager 12c Upgrade Console enables you to select an appropriate upgrade approach, predeploy the Oracle Management Agent 12c software, and switch over the earlier releases of Management Agents to the newly predeployed Management Agents.


Note:

Oracle Management Service 12c communicates only with Oracle Management Agent 12c. Therefore, unlike the earlier releases, you must first upgrade the Management Agents in your system before upgrading your existing OMS. Hence, the Enterprise Manager 12c Upgrade Console acts as a starting point to the upgrade process.

To access the Enterprise Manager 12c Upgrade Console, apply the preupgrade console patch on your existing Enterprise Manager system. For information about the patch you need to download and apply for your platform, access the following URL:

http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

After downloading the patch, follow the instructions outlined in the ReadMe, which is packaged with the patch. Ensure that you use the latest release of OPatch to apply the patch. After applying the patch, log in with super administrator privileges to access the Enterprise Manager 12c Upgrade Console.


IMPORTANT:

  • You will have to shut down your OMS to apply the patch, and as a result, your Enterprise Manager system will be down until you complete the patching operation.

  • Despite applying the patch, if you do not see the hyperlink to the Enterprise Manager 12c Upgrade Console on the Deployments page, then do the following:

    1. Move the jsp_servlet directory out of the following location:

      $<OMS_INSTANCE_BASE>/user_user_projects/domains/GCDomain/generated_classes

    2. Stop the OMS from the OMS home:

      $<OMS_HOME>/bin/emctl stop oms

    3. Restart the OMS from the OMS home:

      $<OMS_HOME>/bin/emctl start oms


The following diagram clearly illustrates the features it offers.

Upgrade Console

Note:

The supported earlier releases for upgrade include: Oracle Management Agent 10g Release 2 (10.2.x.x.x), Oracle Management Agent 11g Release 1 (11.1.0.1.0), Oracle Management Service 10g Release 5 (10.2.0.5.0), and Oracle Management Service 11g Release 1 (11.1.0.1.0).

Installation Wizard

The Enterprise Manager Cloud Control Installation Wizard is the primary user interface that enables you to select the type of upgrade approach you want to perform, and upgrade your existing OMS and Management Repository.

The following diagram clearly illustrates the features it offers.

Surrounding text describes install_wiz.gif.

Postupgrade Console

The Postupgrade Console is the primary user interface for tracking all post-upgrade activities, including accrued data migration jobs and deferred data migration jobs. In addition, you can generate diff reports and view a list of targets that are currently inactive in the upgraded Enterprise Manager system.

The following diagram clearly illustrates the features it offers.

Surrounding text describes postupg_console.gif.

Note:

For more information about these jobs, refer to Chapter 26, Chapter 27, Chapter 28, and Chapter 29.

Overview of Upgrade Processes

This section describes the high-level flow or sequence of steps to be followed for each of the upgrade approaches. In particular, this section describes the following:

1-System Upgrade Process

The following illustration describes the high-level flow or sequence of steps you must perform when you choose to upgrade using the 1-System upgrade approach:

one system upgrade

Using the Enterprise Manager 12c Upgrade Console, you can deploy the Oracle Management Agent 12c software and switch over the old Management Agents to the newly deployed Management Agents. You will notice that Deploy and Switch Over are two different operations, although they deal with installing and upgrading Management Agents.


Note:

As a best practice, Oracle recommends you to complete the Deploy operation well before you start the Switch Over operation.

While the Deploy operation involves copying of software binaries of the Management Agent and configuring them on the hosts, the Switch Over operation involves stopping the old Management Agents and starting the new Management Agents to work with Enterprise Manager Cloud Control.

The two operations are separated and treated as different entities to ensure that your existing Enterprise Manager system is not shut down or disturbed in any way while the software binaries are copied and configured on the hosts. Once the software binaries are copied and configured, you can switch them over with much less time because the time taken is only for stopping the old Management Agents and starting the new Management Agents.

Once you have switched over the Management Agents, you can upgrade the OMS and the Management Repository.


Note:

As a best practice, Oracle also recommends you to upgrade the OMS immediately after you complete the Switch Over operation. Note that the downtime in 1-System upgrade approach essentially lasts from the time you switch over the Management Agent till the time you upgrade your OMS. So the more you delay your upgrade operation, the more the downtime. During this downtime, none of the targets are monitored and no monitoring data is uploaded to the OMS.

When you upgrade to Enterprise Manager Cloud Control on the host using the installation wizard, the installation wizard does the following by default:

  • Upgrades your OMS and Management Agent

  • Installs Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24 (JDK). Also installs Oracle JRF 11g Release (11.1.1.4.0), which includes the oracle_common directory, and Oracle Web Tier 11g Release (11.1.1.4.0), which includes the Oracle_WT directory.


    Note:

    Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24 are installed only if they do not exist in your environment. If they already exist (supported version or higher version), then the installer detects them and displays the middleware home where they are installed. In this case, you only need to validate the path to this middleware home.

  • Installs the following plug-ins:

    • Oracle Database Management Plug-In

    • Oracle Fusion Middleware Management Plug-In

    • Oracle My Oracle Support Management Plug-In

    • Oracle Exadata Management Plug-In

    • Other plug-ins you installed while predeploying Oracle Management Agent 12c using the Enterprise Manager 12c Upgrade Console (that is, if these plug-ins are available in the software kit)

  • Creates or reuses the Oracle WebLogic domain, the Admin Server, the Node Manager, and the Managed Server, depending on the earlier release of the Enterprise Manager system from which you are upgrading.

    • If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5.0), then by default, the following are created:

      • An Oracle WebLogic domain called GCDomain is automatically created during the configuration of Enterprise Manager Cloud Control. For this WebLogic Domain, a default user account, weblogic, is used as the administrative user. You can choose to change this, if you want, in the installer.

      • A Node Manager user account called nodemanager is automatically created during the configuration of Enterprise Manager Cloud Control. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.

    • If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0), then the same Oracle WebLogic domain and Node Manager, which were created for your earlier Enterprise Manager system, will be reused for the new system.

  • Creates the OMS instance base directory (gc_inst) in the middleware home you enter in the wizard, and stores all configuration information related to the OMS.

  • Runs the following configuration assistants to configure the installed or upgraded components:

    • Plugins Prerequisites Check

    • Repository Upgrade Assistant

    • MDS Schema Configuration Assistant

    • OMS Configuration Assistant

    • Plugins Deployment and Configuration Assistant

    • Start Oracle Management Service

    • Plugins Inventory Migration

    • Oracle Configuration Manager Repeater Configuration Assistant

    • Oracle Configuration Manager for OMS


Note:

The installer does NOT upgrade your existing Management Agent because it is predeployed by the Enterprise Manager 12c Upgrade Console.

2-System Upgrade Process

The following illustration describes the high-level flow or sequence of steps you must perform when you choose to upgrade using the 2-System upgrade approach:

Two System Upgrade

When you install and configure Enterprise Manager Cloud Control on the target host using the installer, the installer does the following by default:

  • Installs the following components in the middleware home location you enter in the installation wizard:

    • Java Development Kit (JDK) 1.6 v24

    • Oracle WebLogic Server 11g Release 1 (10.3.5)

    • Oracle Management Service 12c

    • Oracle Management Agent 12c

    • Oracle JRF 11g Release (11.1.1.4.0), which includes oracle_common directory

    • Oracle Web Tier 11g Release (11.1.1.4.0), which includes Oracle_WT directory

    • Oracle Management Plug-Ins

      • Oracle Database Management Plug-In

      • Oracle Fusion Middleware Management Plug-In

      • Oracle My Oracle Support Management Plug-In

      • Oracle Exadata Management Plug-In

      • Other plug-ins you installed while predeploying Oracle Management Agent 12c using the Enterprise Manager 12c Upgrade Console (that is, if these plug-ins are available in the software kit)


        Note:

        Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24 are installed only if they do not exist in your environment. If they already exist (supported version or higher version), then the installer detects them and displays the middleware home where they are installed. In this case, you only need to validate the path to this middleware home.

  • Creates an Oracle WebLogic domain called GCDomain. For this WebLogic Domain, a default user account, weblogic, is used as the administrative user. You can choose to change this, if you want, in the installer.

  • Creates a Node Manager user account called nodemanager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.

  • Configures an OMS Instance Base location in the middleware home, for storing all configuration details related to Oracle Management Service 12c. You can choose to change this, if you want, in the installer.

    For example, if the middleware home is /u01/app/Oracle/Middleware/, then the instance base location is /u01/app/Oracle/Middleware/gc_inst. You can choose to change this, if you want, in the installer.

  • Runs the following configuration assistants to configure the installed or upgraded components:

    • Plugins Prerequisites Check

    • Repository Upgrade Assistant

    • MDS Schema Configuration

    • OMS Configuration

    • Plugins Deployment and Configuration

    • Start Oracle Management Service

    • Plugins Inventory Migration

    • Oracle Configuration Manager Repeater Configuration

    • Oracle Configuration Manager for OMS

    • Agent Configuration Assistant

  • Secures the OMS by generating a password internally. This password is generated by the OMS Configuration Assistant, and the password expires in 30 days from the time it is generated.

    If the OMS Configuration Assistant or the Plugins Deployment and Configuration Assistant fails, then ensure that you resolve the issue within the 30-day period. Otherwise, you will face an error in securing the Management Agent while running the Agent Configuration Assistant.

    If you are unable to resolve the issue within the 30-day period, run the following command from the Management Agent home:

    $<AGENT_HOME>/sysman/install/agentDeploy.sh OMS_HOST=<oms_host_name> EM_UPLOAD_PORT=<oms_upload_https_port> AGENT_REGISTRATION_PASSWORD=<agent_reg_password>

1-System Upgrade Process on a Different Host

The following illustration describes the high-level flow or sequence of steps you must perform when you choose to upgrade using the 1-System upgrade approach on a different host:

one_sys_on_diff_host.gif

As you can see in the illustration, this approach is a combination of 1-System upgrade approach and 2-System upgrade approach. Much like 1-System upgrade approach, you start the upgrade process by predeploying and switching over the Management Agents. Then, like the 2-System upgrade approach, you install Enterprise Manager Cloud Control on a remote host. However, the difference is, you upgrade the same Management Repository that you have been using for the earlier release of the Enterprise Manager, and then decommission the earlier release. This way, only one Enterprise Manager system exists at a given time.

You install the software binaries of Enterprise Manager Cloud Control on the remote host, then upgrade the existing Management Repository, and then, configure the software binaries to complete the installation.

While installing the software binaries, you create Oracle homes and install the following components in the middleware home location:

  • Java Development Kit (JDK) 1.6 v24

  • Oracle WebLogic Server 11g Release 1 (10.3.5)

  • Oracle Management Service 12c

  • Oracle Management Agent 12c

  • Oracle JRF 11g Release (11.1.1.4.0), which includes oracle_common directory

  • Oracle Web Tier 11g Release (11.1.1.4.0), which includes Oracle_WT directory

  • Oracle Management Plug-Ins

    • Oracle Database Management Plug-In

    • Oracle Fusion Middleware Management Plug-In

    • Oracle My Oracle Support Management Plug-In

    • Oracle Exadata Management Plug-In

While configuring the software binaries, you do the following:

  • Create an Oracle WebLogic domain called GCDomain. For this WebLogic Domain, a default user account, weblogic, is used as the administrative user. You can choose to change this, if you want, in the installer.

  • Create a Node Manager user account called nodemanager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.

  • Configure an Oracle Management Service Instance Base location (gc_inst) in the middleware home, for storing all configuration details related to Oracle Management Service 12c.

    For example, if the middleware home is /u01/app/Oracle/Middleware/, then the instance base location is /u01/app/Oracle/Middleware/gc_inst.

  • Configures the plug-ins and the Management Agent.