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
 

27 Tracking the Status of Accrued Data Migration Jobs


Note:

This chapter is applicable only for 2-System upgrade approach.

This chapter describes the following:

Overview of Accrued Data Migration

Accrued Data Migration is a post-upgrade activity to migrate the accrued data stored in an earlier release of Oracle Management Repository (Management Repository) to the upgraded Management Repository. The accrued data relates to functional areas such as blackouts, alerts, events, metrics, and so on.


Note:

The Accrued Data Migration Process does not migrate any manually created data such as new job type, user-defined metrics, Software Library-related changes, and so on.

The migration activity is essentially a job in Enterprise Manager that runs in the background immediately after the earlier releases of Oracle Management Agents (Management Agents) are switched over to Oracle Management Agent 12c, particularly in the case of 2-System upgrade approach.

As part of the upgrade process, when you switch over the earlier releases of Oracle Management Agents to Oracle Management Agent 12c, the new Management Agents start communicating with Enterprise Manager Cloud Control, and start uploading data to the upgraded Oracle Management Repository (Management Repository).

In the 1-System upgrade approach, the entire Enterprise Manager system is upgraded, and therefore, all the Management Agents are switched over at a given time. In this approach, earlier releases of Management Agents cannot coexist with the upgraded ones, and once they are switched over, the upgraded Management Agents upload data only to one Management Repository at any given point, which is the upgraded repository. Therefore, there is no scope for accrued data.

However, in the 2-System upgrade approach, you can choose to switch over your Management Agents in phases. When one set of Management Agents are switched over, they start uploading data about their hosts and targets to the upgraded Management Repository, whereas the ones that are not switched over yet, continue to upload data about their hosts and targets to the old Management Repository. Therefore, the earlier releases of Management Agents coexist with the upgraded ones when only some of them are switched over, and under such circumstances, the data is uploaded to the old Management Repository as well as the new one at a given point. However, note that only one Management Agent represents a host at any given time, so the coexistence does not indicate two Management Agents on the same host. It only indicates an earlier release of Management Agent monitoring a host that coexists with an upgraded Management Agent monitoring another host.

When you swtich over the next set of Management Agents in the next phase, although they start uploading data to the upgraded Management Repository, the data uploaded to the old ManagementRepository before being switched over continues to exist in the old Management Repository. This data is called the Accrued Data, and the process of migrating this accrued data from the old Management Repository to the new one is called the Accrued Data Migration Process.


Note:

The accrued data migration jobs migrate ECM history data with the following exceptions:
  • If the ECM history data is associated with a target that is no longer part of the Enterprise Manager system, then the ECM history data for that target is not migrated to Enterprise Manager Cloud Control.

  • For Oracle WebLogic Server targets, the WebLogic configuration data is not migrated. This configuration data has changed significantly in Enterprise Manager Cloud Control.

  • As part of the data migration process, summary counts are now calculated and displayed in the ECM Summary region. For migrated data, the summary counts are only calculated for the last seven days.

If you do not see key values that you saw in the past, or if you see new values as key values, then note that this is an expected behavior. Some snapshots have had metadata changes in the last release and key values have changed. If metadata keys were removed from the metadata, those values will no longer be displayed in the Enterprise Manager Cloud Control as key columns, though the data is still present in the migrated database. If existing columns are now flagged as key columns, those columns will start appearing as key columns for newly collected data only. For new columns that are added either as key columns or non key columns, data will start appearing for newly collected data only.



Note:

If you want to prevent the ADMP jobs from running immediately by default, then see Chapter 8 (Step 6).

Tracking the Status of Accrued Data Migration Jobs

To track the status of accrued data migration jobs, follow these steps:

  1. In Cloud Control, from the Setup menu, click Post Upgrade Tasks.

  2. On the Post Upgrade Console page, click the Accrued Data Migration tab.

    The Accrued Data Migration page displays information about the accrued data migration jobs related to all the targets available in your Enterprise Manager system. By default, for every target, the accrued data migration job migrates the ECM history details as well as the metric details.

  3. In this tab, you can do the following:

    • To control the data being migrated for all the targets, from the Run accrued data migration for list, select one of the following options:

      • ECM HISTORY MIGRATION, to migrate only the ECM history details.

      • METRIC DATA MIGRATION, to migrate only the metric details.

      • All, to migrate the ECM history details as well as the metric details.

    • To view different types of data, from the View Targets list, select one of the following options:

      • All, to view all the accrued data migration jobs for all the targets in your Enterprise Manager system.

      • Active, to view the accrued data migration jobs that either failed or are currently running.

      • History, to view the accrued data migration jobs that succeeded.

      • Not Started, to view the accrued data migration jobs that have not started yet.

    • To retry a failed job, select the target for which the job failed and click Retry.

    • To stop a running job, select the target for which you want to stop the job and click Stop.