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
 

6 Upgrading with 1-System Approach on a Different Host

To upgrade your existing Enterprise Manager system to Enterprise Manager Cloud Control with 1-System upgrade approach on a different host, follow these steps:

Table 6-1 Upgrading Enterprise Manager 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.

Chapter 2


(b)

Review the important facts you need to know before you begin.

Chapter 3


Step 2

Perform Preupgrade Tasks


(a)

Apply the preupgrade console patch on your existing Enterprise Manager system to get access to the Enterprise Manager 12c Upgrade Console.

Preupgrade Console


(b)

Provide information about the host where you plan to upgrade your existing OMS.

Chapter 8


(c)

Manually download the following software, and stage them to an accessible location:

  • Oracle Management Agent 12c

  • All the required plug-ins

Installing Plug-Ins While Upgrading Oracle Management Agent


(d)

Provide information about the location of the software you manually downloaded and staged in Step 2 (c).

Chapter 9


(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).

Chapter 10


(f)

Meet the prerequisites for upgrading the Management Agents.

Appendix D


Step 3

Upgrade Oracle Management Agent


(a)

Deploy and configure the software binaries of Oracle Management Agent 12c.

Chapter 11


(b)

Generate a health report and check the readiness of the predeployed Management Agents.

Chapter 12


(c)

Verify and sign off the health check report.

Chapter 13


(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.

Chapter 14


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:

  • Meet the Oracle Management Service-related prerequisites described in the chapter on installing Enterprise Manager Cloud Control, in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

  • Meet the Management Agent-related prerequisites described in Appendix D.

  • Meet these additional requirements:

    If you have Power Broker set up, then disable the welcome message.

    If you have SUDO set up, then ensure that you have SUDO privileges to invoke /bin/sh as root. Ensure that you have the line Defaults visiblepw in the /etc/sudoers file. Also ensure that you comment out the line Defaults requiretty in the file.


(b)

On the Management Repository, meet the following prerequisites:

  • Ensure that the MGMT_CONNECTOR_CONFIG table does not have any NULL rows. To verify this, run the following SQL query.

    select * from mgmt_cntr_config where connector_type_guid IS NULL and connector_guid IS null;

    Typically, the command must not return any rows. If it does return any rows, then run the following SQL query to clean the table:

    delete from mgmt_cntr_config where connector_guid IS NULL or connector_type_guid IS NULL;

    commit;

  • Ensure that there are no custom-created materialized views in the Management Repository. To verify this, run the following SQL query. Typically, the command must not return any rows. If it does return any rows, then contact Oracle Support.

    select count(1) from ALL_MVIEW_LOGS where log_owner=<EM_REPOS_USER>

  • Ensure that the tables do not have any snapshots created. To verify this, log in to the Management Repository and run the following SQL query as SYSMAN user:

    select master , log_table from all_mview_logs where log_owner='<EM_REPOS_USER>

    For example,

    select master , log_table from all_mview_logs where log_owner='SYSMAN'

    If there are snapshots created in a table, then the query displays the master table and the snapshot details. For example,

    SQL> master log_table

    em-violations em$violation_log

    If there are snapshots, then drop them by running the following command as SYSMAN user:

    SQL> Drop snapshot log on <master>

    For example,

    SQL> Drop snapshot log on em-violations

(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)

  1. Take an inventory of the JVMs and WebLogic Domains being monitored by JVMD and/or ADP.

  2. Deinstall the JVMD and ADP applications from your inventory by logging into the WebLogic Administration Console for each monitored domain and removing the jamagent and Acsera application deployments.

  3. Shut down all of your ADP and JVMD managers.

  4. Remove all ADP and JVMD managed servers from the GCDomain using the WebLogic Administration Console.

  5. Run purge scripts for JVMD:

    (a) Navigate to the following location:

    <middleware_home>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.1.0/archives/jvmd/

    (b) Extract the file jvmd.zip.

    (c) Run the script jvmd_monitoringupgrade11_12.sql.

    (d) Run the script jvmd_traceupgrade11_12.sql if there are existing Thread Snapshots from Enterprise Manager 11g Grid Control Release 1 (11.l.0.1).


(e)

Copy the emkey from the OMS to the Management Repository:

  • If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5), then run the following command from the OMS home:

    $<OMS_HOME>/bin/emctl config emkey -copy_to_repos -sysman_pwd <sysman_pwd>

  • If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), then run the following command from the OMS home:

    $<OMS_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_host <repository_host> -repos_port <port> -repos_sid <sid> -repos_user <username> [-repos_pwd <pwd>] [-admin_pwd <pwd>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora


(f)

If you have a Server Load Balancer (SLB) configured, then make changes to your monitors.

Appendix E


(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.

Chapter 20


Step 5

Perform Postupgrade Task


(a)

Check the agent upgrade status.

Chapter 24


(b)

Perform the general post-upgrade tasks.

Chapter 25


(c)

Track the status of deferred data migration jobs.

Chapter 26


(d)

Update the incident rules for metrics associated with the OMS.

Chapter 31


(e)

(Only if you have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed)

  1. If you have not deinstalled the JVMD and ADP applications from your inventory by logging into the WebLogic Administration Console for each monitored domain and removing the jamagent and Acsera application deployments, then do so now.

  2. Delete all ad4jTarget targets:

    (a) Navigate to the following location:

    <middleware_home>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.1.0/archives/jvmd/

    (b) Extract the file jvmd.zip.

    (c) Run the script jvmd_targetupgrade11_12.sql.

  3. Delete all OCAMM Manager targets:

    (a) Navigate to the following location:

    <middleware_home>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.1.0/archives/ocamm/

    (b) Extract the file ADPManager.zip.

    (c) Run the script adp_targetupgrade11_12.sql.

  4. Deploy new JVMD and ADP managers.

  5. Deploy new JVMD and ADP agents based on your inventory.