The Automatic Storage Management (ASM) health checker is a crucial tool in Oracle databases that monitors the health and integrity of the storage infrastructure. When the ASM health checker reports a new failure, it's essential to understand the implications and take corrective actions to prevent data loss or system downtime. In this blog post, we'll discuss what an ASM health checker failure means, how to investigate the issue, and steps to resolve it.
This final check ensures the inconsistency has been fully resolved and the disk group is now in a consistent state. The absence of new failure messages in the alert.log confirms a successful resolution.
When the checker finds a failure, it logs the alert. Many users report seeing "ASM Health Checker found 1 new failures" appear in the alert log file ( log.xml ) or as a metric alert in Oracle Enterprise Manager (OEM).
The most common cause is an inconsistency in the ASM metadata. This can happen due to an unexpected power loss, a bug in the storage firmware, or "lost writes." Run an internal ASM check. ALTER DISKGROUP CHECK ALL; Use code with caution. B. Offline Disks or Path Issues asm health checker found 1 new failures
The ASM Health Checker runs automatically and reports any issues or failures it detects. The checker runs at regular intervals, which can be configured using the ASM_CHECK_INTERVAL parameter.
Sometimes, the alert is triggered not by a real failure but by a bug. For example, users of CloudLinux with CageFS enabled reported false-positive health check warnings on cPanel v134 and newer. In this case, the solution was to wait for a patch (e.g., cagefs-7.6.31-1 ) or update your software.
To fix the failure, you first have to identify it. You can do this via the Command Line Interface (CLI) using ADRCI . Step A: Access ADRCI Log in to your grid infrastructure server and run: adrci Use code with caution. Step B: Set the Home Path The Automatic Storage Management (ASM) health checker is
Once you have fixed the underlying physical or logical issue, the Health Checker should automatically update during its next run. However, if the status remains "Failed" in the views, you can manually trigger a re-run of the health check or use ADRCI to purge the alert. Summary Checklist
: If the ASM disk group hosts the Cluster Registry (OCR) or Voting Disks, a failure can cause node evictions or cluster instability. Storage Latency/I/O Timeouts
:
The term "ASM" can point to several technologies, but this specific alert is most commonly associated with two primary contexts: and cPanel/WHM's hosting automation platform . While the urgency is the same, the underlying cause and the fix differ significantly. We'll cover both scenarios, providing step-by-step guidance for each.
: The diskgroup cannot maintain a read quorum, often leading to an automatic dismount. How to Diagnose and Fix To resolve the failure, follow these diagnostic steps:
World
Europe
0
English
English
German
Japanese
Spanish
