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
 

25 Performing General Postupgrade Tasks

This chapter describes the postupgrade steps you must follow after upgrading to Enterprise Manager Cloud Control. In particular, this chapter describes the following postupgrade steps:

Performing General Postupgrade Steps

Follow the postupgrade steps outlined in the chapter that describes how to install a new Enterprise Manager system, in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Stopping OCM Scheduler

If OCM was installed in the Enterprise Manager system that you upgraded, then follow these steps:

Deleting Obsolete Targets

The following targets from the earlier release of Enterprise Manager are not deleted automatically. This is because you might have created notification rules, metric threshold settings, compliance standard settings, jobs, and so on for these targets, and you might want to copy them to the new Oracle WebLogic Server targets of Enterprise Manager Cloud Control. After copying them, manually delete these targets.

Disabling Incident Rule Sets

If you upgraded using the 2-System upgrade approach, then disable the default incident rule sets. If you do not disable them, the incidents are automatically created for all critical metric alerts.

To disable the default incident rule sets, follow the steps:

  1. In Cloud Control, from the Setup menu, select Incidents, and then select Incident Rules.

  2. On the Incident Rules - All Enterprise Rules page, scroll down the table, and expand Incident management Ruleset for all targets.

  3. Select the row for the rule set you want to disable.

  4. From the Actions menu, click Disable.

  5. On the pop-up window, click OK.

  6. Repeat Step (3) to Step (5) for every rule set you want to disable.

  7. Once all the rule sets are disabled, ensure that the Enabled column of the table shows No with a warning icon next to it.

Resolving Metric Collection Errors for SOA Target

If you were monitoring a SOA target in your earlier release of Enterprise Manager, then in the health report you generated in Chapter 12, you might have seen metric collection errors for the metrics Top SOA SQL Queries and Dehydration Store Tables.

To resolve that issue, access the Monitoring Configuration page of the SOA target, and provide the database credentials.

Enabling Linux Patching After Enterprise Manager Upgrade

After upgrading Enterprise Manager, you must stop all active jobs for Linux patching that were submitted prior to the upgrade, and resubmit them on the same targets. This section describes how you can achieve this.

In particular, this section covers the following:

Configuring DownloadLatestPackages Job

To configure the DownloadLatestPackages job, follow these steps:

  1. Stop active jobs which were scheduled prior to upgrade as follows:

    1. From the Enterprise menu, select Job and then Activity. The Job Activity page is displayed.

    2. In the Job Activity page, click the Advanced Search link.

    3. In the Advanced Search options, select Job Type as DownloadLatestPkgs, Target Type as Host, Status as Active, Scheduled Start as All, and then click Go.

    4. In the Advanced Search result, select each job listed in the table and click Stop.

  2. For each host target on which an active DownloadLatestPkgs job was stopped, resubmit a new DownloadLatestPkgs job on it as follows:

    1. From the Setup menu, select Provisioning and Patching and then Linux Patching. The Patching Setup page is displayed.

    2. In the Patching Setup page, click Setup RPM Repository.

    3. In the Setup RPM Repository page, select the Host target and set Normal Host Credentials and Privileged Host Credentials for this host target.

    4. Click Apply to submit the new job.

Configuring UpdateHostPackages Job

To configure the UpdateHostPackages job, follow these steps:

  1. Stop active jobs which were scheduled prior to upgrade as follows:

    1. From the Enterprise menu, select Job and then Activity. The Job Activity page is displayed.

    2. In the Job Activity page, click the Advanced Search link.

    3. In the Advanced Search options, select Job Type as UpdateHostPackages, Target Type as All Target Types against which jobs were submitted, Status as Active, Scheduled Start as All, and then click Go.

    4. In the Advanced Search result, select each job listed in the table and click Stop.

  2. For each group target on which an active UpdateHostPackages job was stopped, resubmit a new UpdateHostPackages job on it as follows:

    1. From the Setup menu, select Provisioning and Patching and then Linux Patching.

    2. In the Patching Setup page, click Setup Groups. The Setup Groups page is displayed.

    3. In the Setup Groups page, select the group on which you stopped an active UpdateHostPackages job and click Edit. The Edit Group wizard is displayed.

    4. In the Edit Group: Properties page, click Next.

    5. In the Edit Group: Package Repositories page, click Next.

    6. In the Edit Group: Credentials page, either use Host Preferred Credentials or Override Preferred Credentials and specify Normal Host Credentials and Privileged Host Credentials. Click Next.


      Note:

      Before editing this step, ensure that the host Preferred credentials are set already or the appropriate Named Credentials have been created already. If not, from the Setup menu, select Security and then Named Credentials to create Named Credentials or Preferred Credentials to set the Preferred Credentials for the host targets contained in the Linux Patching group.

    7. In the Edit Group: Review page, click Finish to submit the new job.