EM Triggers Disk Device 100% Busy Alert For ODA Disk Partition

Asset ID:	1-72-1558550.1
Update Date:	2013-06-06
Keywords:

Solution Type Problem Resolution Sure

Solution 1558550.1 : EM Triggers Disk Device 100% Busy Alert For ODA Disk Partition

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Enterprise Manager Cloud Control 12c reports an alert for Oracle Database Appliance (ODA V1 and X2-3) host targets:

No other symptoms or performance impact to the system.

Changes

None.

Cause

An iostat OS (Linux) BUG causes an erroneous results for Disk Usage. This issue is tracked in Unpublished BUG: 16725211 - oda - disk device sdau1 & sdau2 are 100% busy due to avgqu-sz value

Solution

You can ignore this alert for now. A fix will be provided in upcoming ODA releases.

You can Suppress this Alert from EM, but that will not prevent future re-occurrences of the alert once the monitoring agent runs iostat again (every few minutes).

As a *temporary* workaround for now, and until the fix is available for ODA Software Release.

To disable this alert from EM, please perform the following actions for each ODA host, for which you wish to implement this temporary workaround:

Note: The following example uses EM Cloud Control 12c. For older versions such as 11g, the same navigation applies.

1) Login to EM Cloud Control as an administrator with full rights to ODA host targets.

2) Navigate to the ODA host home page and select Monitoring >> Metric and Collection Settings

3) Edit the Disk Activity Busy (%) metric and remove threshold values. (Replace 85 and 90 with 0). Example:

From:

To:

4) Click OK to apply the new settings.

This will disable metric alerts for Disk Activity Busy. No further alerts will trigger until this metric is re-enabled by following the same 4 steps above for each host, and introducing the new threshold values.

Note: Once you apply the iostat fix through an upcoming ODA release, make sure that you re-enable this metric by adding the Warning and Critical threshold values and applying the changes.

Attachments

This solution has no attachment