Asm Health Checker Found 1 New Failures -
To minimize the risk of encountering this or similar alerts, implement these best practices:
Addressing this alert promptly ensures cluster stability and prevents potential database downtime. Understanding the ASM Health Checker
Run lsdg to confirm that all disk groups are properly mounted, displaying the correct usable capacity and balanced allocation units.
The error is rarely an isolated software bug. Instead, it is a symptom of underlying infrastructural or physical disruptions: asm health checker found 1 new failures
This method is recommended in Oracle documentation for identifying specific health check failures.
The hum of the server room was usually a comforting white noise for Leo, the lead DevOps engineer. But at 3:00 AM, that hum sounded more like a low-pitched warning.
Oracle Automatic Storage Management uses localized, automated checking subroutines to monitor disk integrity, read/write timeouts, and consistency across failure groups. The runs continuously or is automatically triggered during crucial storage events, such as: An intentional or accidental storage reconfiguration . The initiation of a diskgroup rebalance operation. To minimize the risk of encountering this or
I can provide the specific syntax to fix the precise failure you are experiencing. Share public link
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
The error message "ASM Health Checker found 1 new failures" typically appears in the Oracle ASM alert logs when the system detects an issue with a disk or disk group Instead, it is a symptom of underlying infrastructural
The response to this finding must be methodical, not panicked. The first step is triage: querying V$ASM_DISK and V$ASM_OPERATION to identify the exact nature of the failure. Is the disk marked FORCED or FAILED ? Has an offline disk exceeded DISK_REPAIR_TIME ? Often, the new failure is a “stale” disk that failed to resync after a transient outage. The solution might be as simple as an ALTER DISKGROUP ... ONLINE DISK command. Other times, the failure points to degraded hardware—a flaky SAS cable, a failing SSD, or a misconfigured multipath. In these cases, the DBA shifts from technician to detective, correlating the ASM alert with OS logs ( dmesg , syslog ) and storage array warnings. The one failure demands a root cause analysis before it metastasizes into a cascade.
: The instance forces a "dirty detach" from the clustered storage domain to shield the rest of the Oracle RAC cluster from corrupted structures. Root Causes of ASM Health Checker Failures
Before troubleshooting the error, understanding the tool is crucial. The ASM Health Checker is an automatic, background diagnostic framework introduced in Oracle Grid Infrastructure 11gR2 (enhanced in 12c and 19c). It runs periodically (typically every hour or on specific triggers) to validate:
