Troubleshooting Metrics

In the unlikely situation that a metric does not report a correct value, you must determine if the problem is related to the:

  • Metric providing the wrong values or failing with an error, or

  • If the problem is after the Management Agent in the execution flow of the metric, that is, the metric value is correct but, for some reason, the data is not reaching the Oracle Management Service.

To aid you in this determination, Oracle provides the Metric Browser; a troubleshooting tool that can be used with Enterprise Manager to see the raw data being collected by the Management Agent.

Accessing the Metric Browser

When enabled, the Metric Browser can be accessed using a web browser, for example, Netscape, Firefox, and Internet Explorer, using a URL of the form:

http|https://agent_hostname:agent_port/emd/browser/main

for example

http://myServer.myDomain:3872/emd/browser/main

Note:

You can determine the protocol (http or https), the host name, and the Management Agent port that should be used from the output of the following command (run on the Management Agent host):

agent_home/bin/emctl status agent

The Management Agent URL, listed in the output to that command, needs only to have browser placed between emd and main.

By default, the Metric Browser is disabled. When the Metric Browser is disabled, you receive the following error:

HTTP Error 403 - Forbidden if the metric browser has not been enabled.

How to Enable the Metric Browser and the Management Agent Browser for the Oracle Management Agent

Follow these steps to enable the Metric Browser.

  1. The Metric Browser is enabled by setting the enableMetricBrowser property in the Management Agent's emd.properties file. The location of that file depends on the type of Management Agent you are working with:

    • For the Cloud Control (central|standalone) Management Agent, the file is:

      AGENT_HOME/sysman/config/emd.properties

    • For a clustered (RAC) Management Agent install, the file is:

      AGENT_HOME/hostname/sysman/config/emd.properties

    • For the Database Control Management Agent, the file is:

      DATABASE_HOME/hostname_SID/sysman/config/emd.properties

    • For Application Server Control Management Agent, the file is:

      AS_HOME/sysman/config/emd.properties

  2. Make a backup copy of the emd.properties file.

  3. Edit the file and locate the line that reads:

    #To enable the metric browser, uncomment the following line
    #This is a reloadable parameter
    #
    #enableMetricBrowser=true
    
  4. Uncomment the line: #enableMetricBrowser=true, so that it reads:

    enableMetricBrowser=true

  5. Reload the Management Agent Configuration using the command:

    AGENT_HOME/bin/emctl reload agent

  6. After reloading the Management Agent, the Metric Browser will be enabled and therefore accessible using a browser.

Running the Metric Collection Outside the Management Agent

Running the metric collection outside the Management Agent is specific to each metric and requires a firsthand knowledge of each specific metric. Each metric has its own method of collecting its data and some metrics cannot be run standalone because they are calculated from other metrics.

An example of running the metric collection outside the Management Agent is the command line.