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


12 Generating Health Report of Deployed Oracle Management Agents

Before you switch over from your old, existing Management Agent to the newly deployed and configured Oracle Management Agent 12c, generate a report to check the health and the readiness of the deployed Management Agents so that any issues with the deployment can be identified beforehand.

For all the Management Agents to switch over successfully and function properly in the upgraded Enterprise Manager system, you must ensure that the Management Agents are in a position to contact the upgraded Oracle Management Service, monitor all the targets they monitored before, and collect all the metrics details they collected before. The health report helps in identifying any issues related to these requirements so that you can resolve them beforehand.


Perform these steps in the Enterprise Manager Grid Control console of the earlier release.


You can generate health reports only for Management Agents that have been successfully deployed and configured.

To generate a health report of the deployed Management Agents and check their readiness, follow these steps:

  1. In Grid Control, click Deployments.

  2. On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.

  3. On the Upgrade Console page, in the Agent Upgrade Steps section, from the table, click Generate Health Report of Deployed Agents.

  4. On the Generate Health Report for Deployed Agents page, in the Provide Inputs section, do the following:

    1. Enter a unique name for the deployment operation you are about to perform. The custom name you enter can be any intuitive name, and need not necessarily be in the same format as the default name.

      For example, CheckHealth_Agents_Phase1_2010_12_23.


      The operation name you enter here is only a logical name and will be used for saving the details of the operation you are about to perform. After checking the health of the deployed Management Agents, at a later point in time, if you want to switch over from old to newly deployed and configured Management Agents, then you can use the operation name to identify and track the Management Agents selected as part of this operation.

    2. If you want to perform the readiness check for the Management Agents you had previously deployed, then click the torch icon against Load Agents from Previous Operations, and select the operation you had submitted for deploying those Management Agents, click Go.

      Enterprise Manager Grid Control populates the table in the Search Agents section with a list of Management Agents that are associated with the operation you selected.

  5. In the Search Agents section, search and add the Management Agents for which you want to perform the readiness check:

    • If you specified a readiness operation name as described in Step 4 (a), then search (or add) and select the existing, old Management Agents for which you have already deployed the software and for which you want to check the health now. To understand how to search and add Management Agents, see Appendix G.

    • If you selected a deployment operation as described in Step 4 (b), then review the Management Agents that are displayed based on the operation you selected.

  6. After you add the Management Agents, select each of them from the Select column.

  7. In the Agent Credentials section, retain the default selection, that is, Use Oracle Home Preferred Credentials, so that the preferred credentials stored in the Management Repository can be used for this job.


    Ensure that the preferred credentials were registered with the Enterprise Manager system using the Enterprise Manager Command Line Interface (EM CLI). For more information, see Appendix F.

    You can optionally override these preferred credentials. To do so, select Override Oracle Home Preferred Credentials and enter one set of credentials that can be used for all Oracle homes.


    Ensure that you use the same credentials that you used for the existing, earlier release of the Management Agent

  8. Click Submit.


  • After you submit the operation, if you see the following error, then first run from the old Management Agent home, and then, resubmit this operation.

    ERROR: NMO not setuid-root (Unix-only) 
  • If you see the following error, then verify the credentials entered in Step (10).

    Local Authentication Failed...Attempt PAM authentication...PAM failed . . .
  • When the operation is in progress, if a Management Agent for which you are performing a readiness check becomes unavailable for some reason, you may see the status Suspended on Event. Once the Management Agent becomes available, the status automatically changes to show the current state. This is an expected behavior.

  • If you were monitoring a SOA target in your earlier release of Enterprise Manager, then in the health report, you might see metric collection errors for the following metrics:

    • Top SOA SQL Queries

    • Dehydration Store Tables

    As this stage, you can ignore these errors and proceed further. However, ensure that you provide the database credentials for this target as described in Chapter 25.