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
 

13 Verifying and Signing Off the 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, verify and sign off the health report of deployed Management Agents.

For all the Management Agents to switch over successfully and function properly in Enterprise Manager Cloud Control, you must ensure that the Management Agents are in a position to contact the upgraded Oracle Management Service (OMS), 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.


Note:

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

To verify and sign off the health report, 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 Sign Off Health Report for Deployed Agents.

  4. On the Sign Off Health Report for Deployed Agents page, view the health and the readiness details for each of the Management Agents.

    • Verify the Ping Test column, which indicates whether or not the deployed Oracle Management Agent 12c will be able to contact the upgraded OMS.


      Note:

      For 1-System upgrade, in the Ping Test column, you will see the value N/A.

      For 2-System upgrade, you will see either Passed or Failed. The status Passed indicates that the ping test was successful, and the status Failed indicates that the test was unsuccessful. If you see the status Failed for any Management Agent, then do the following:

      • Verify the OMS host name and OMS port entered in the Identify Host and Port for New Enterprise Manager System page.

        Alternatively, verify the REPOSITORY_URL parameter in the following file. Here, <Agent_Instance_Home> refers to the 12c agent home.

        <Agent_Instance_Home>/sysman/config/emd.properties

        If the OMS host name and port are correct, then check for errors in the following log file:

        <Agent_Instance_Home>/sysman/log/gcagent.log

      • If any Management Agent is in unsecure mode, and if you have already upgraded the OMS, then run these commands, generate the health check report again, and then switch over:

        $<OMS_HOME>/bin/emctl secure unlock -console

        $<OMS_HOME>/bin/emctl secure unlock -upload



      Caution:

      If your old Management Agent was running in secure (or unsecure) mode before backing up the Management Repository in case of the 2-System upgrade approach, then ensure that it continues to run in the same mode while you deploy and configure the new Management Agent for it. Otherwise, the ping test can fail due to a mismatch between the configuration stored in the repository and the actual configuration of the Management Agent.

    • Verify the Broken Targets column, which indicates whether or not the deployed Oracle Management Agent 12c will be in a position to monitor all the targets that were monitored earlier by the old Management Agent. The numeric value you see in the column indicates the number of targets that cannot be monitored in the upgraded system.

      If you see any value other than 0, then view the detailed report (as described in the next step) to see a list of broken targets and the reasons why they are broken.

    • Verify the Failed Metrics column, which indicates whether or not the deployed and configured Oracle Management Agent 12c will be able to collect all the metrics in the upgraded Enterprise Manager system. The numeric value you see in the column indicates the number of metrics that have an issue.

      If you see any value other than 0, then view the detailed report (as described in the next step) to see a list of failed metrics and the reasons for their failure.

    • Verify the Sign-Off User column and the User Verified Column, which indicate whether or not the health report was signed off for a Management Agent. If you do not see any value in these columns, then formally sign off the report as described in Step (6).

  5. If you want to view a detailed report, select the Management Agent for which you want to view a detailed report, and click View Detailed Report.

  6. After checking the report, click Verify and Sign Off Report to sign off. Ensure that the Management Agent for which you viewed a detailed report is selected.


Note:

  • After you submit the operation, if you see the following error, then first run root.sh 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 . . .
    
  • 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.