5 Upgrading with 2-System Upgrade Approach

Step 1

Prepare Yourself

(a)

Learn about the 2-System upgrade approach.

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 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:

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

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)

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

(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. The following commands are applicable for both versions.

Note: When you run the following command on Enterprise Manager 11g Grid Control (11.1.0.1), you are prompted for the admin password.

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

To verify if the emkey is copied properly, log in to the repository as sys user and run the following sql command:

SQL> select count(*) from MGMT_REPOS_TIME_COEFFICIENT;

COUNT(*)

----------

1

(If the count is 1, then the emkey is copied.)

(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 /programs/swlib and /software/swlib, then create two separate archives, one for each configured directory. In this case, create programs_swlib.zip and software_swlib.zip, respectively.

(f)

Back up your existing database, which houses the Management Repository, 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.

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

- 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 .Chapter 28.

(g)

On the backed up 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

(h)

Remove the emkey from the Management Repository by running the following command from the old Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) OMS home:

$<OMS_HOME>/bin/emctl config emkey -remove_from_repos [-sysman_pwd <pwd>]

(i)

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 .Chapter 28.

Chapter 15

(j)

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 Enterprise Manager 12c Upgrade console, go to the Pre-upgrade 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 Enterprise Manager 12c Upgrade 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 before taking a back up of the OMS, run the following command.

$<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>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora

(Here, the Management Repository details are details of the existing or old Management Repository. If you are running the installer on Enterprise Manager 11g Grid Control, you will be prompted for the admin server password.)

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

Chapter 16, Chapter 17, Chapter 18, or Chapter 19

(k)

Link the ealier release of the Management Repository with the upgraded Management Repository.

Chapter 22

(l)

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

Chapter 23

Step 4

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 4 (a) to Step 4 (d) for each attempt.

Chapter 14

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)

Track the status of accrued data migration jobs.

Chapter 27

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

Chapter 28

(f)

View a list of targets that are currently inactive in the upgraded Enterprise Manager system.

Chapter 29

(g)

Sign off accrued data migration process.

Chapter 30

(h)

Update the incident rules for metrics associated with the OMS.

Chapter 31

(i)

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