Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Database Performance Analyzer (DPA) > Metrics charts missing data in DPA, Oracle 11 database crash - workaround

Metrics charts missing data in DPA, Oracle 11 database crash - workaround

Updated August 29, 2017

Overview

This article provides a workaround for an issue that occurs when DPA is monitoring an Oracle database instance with ASM (Automatic Storage Management) metrics enabled, and the Oracle database instance has a disk group number higher than 63.

Environment

  • DPA 11.0 or later
  • Oracle 11

Cause 

This issue occurs when both of the following conditions are met:

  • An Oracle 11 database instance has a disk group number greater than 63 - You can verify the disk group number in the v$asm_disk view on the database instance.
  • The database instance has ASM (Automatic Storage Management) metrics enabled.

 

Missing data in DPA metrics charts happens because Oracle 11 crashes when the above conditions are met.

Resolution

To fix this issue, upgrade to Oracle 12, which supports more than 63 volume groups.

 

To work around this issue when using Oracle 11, disable ASM metrics. This can stop Oracle 11 from crashing, preventing data loss. There are two ways to disable ASM metrics. You only need to do one of the following:

 

  • Disabling ASM metrics in the DPA user interface
  1. Open the main window of DPA. In the database instance table, click on the name of the database that you want to disable metrics for.
  2. Click on the Resources tab at the top of the DPA window. Go to the ASM tab.
  3. Choose one of the metrics on the ASM tab and click the Settings link below the chart.
  4. In the Resource Settings category, choose Custom and uncheck “Enable Data Collection”.
  5. Perform steps 3 and 4 for all metrics in the ASM tab.

 

  • Disabling ASM metrics implicitly in the repository table
  1. Open the main window of DPA. Click on Options in the main menu.
  2. Choose the Support tab and click on the Database Query Tool.
  3. Find out the ID of the database you want to turn off metrics for by using a SELECT query on the COND table:
    SELECT ID FROM COND WHERE NAME = <your database name in DPA>;
  1. Disable ASM metrics for the database ID by using an INSERT query on the CON_METRICS_DISABLED  table where <DB ID> is the database ID found in step 3 and <metric name> is the ASM metric to disable (see list below):
    INSERT INTO CON_METRICS_DISABLED (DB_ID, ENTITY_TYPE, METRIC_NAME, BRANCH_NAME, DISABLED_FLAG, DISABLED_REASON) VALUES (<DB ID>, 'DB', <metric name>, 'IGNITE', 0, '');

    Perform this query for all ASM metric names:

    • ASM Summary Bytes Written

    • ASM Summary Bytes Read

    • ASM Summary Write Time

    • ASM Summary Read Time

    • ASM Summary Writes

    • ASM Summary Reads

  1. Restart DPA.

 

 

 

Last modified

Tags

Classifications

Public