To troubleshoot and resolve ASM health checker failures, follow these steps:
ALTER DISKGROUP data SET ATTRIBUTE 'disk_repair_time' = '6h';
to run a manual health check for your specific Oracle version? RAC/ ASM Health Check - Oracle Forums 13 Sept 2011 — asm health checker found 1 new failures updated
: Run crsctl check crs to verify the status of the clusterware stack.
Once the incident is found, determine if it is a physical, logical, or metadata issue. To troubleshoot and resolve ASM health checker failures,
A DBA was analyzing the ASM alert log and saw: "ASM Health Checker found 1 new failures" . The DBA then ran ALTER DISKGROUP DATA CHECK; and discovered that there was indeed an inconsistency in the disk group metadata—an orphaned extent map entry. After confirming that the database was still operational, the DBA ran ALTER DISKGROUP DATA CHECK ALL REPAIR; . The command completed successfully, the health checker alert cleared, and a subsequent health check reported zero failures.
In the complex ecosystem of modern enterprise computing, the Oracle Automatic Storage Management (ASM) layer serves as the critical bridge between the database software and the physical storage hardware. It is the circulatory system of the data center, managing the flow of information to the disks. Within this high-stakes environment, the alert message "ASM Health Checker found 1 new failures updated" is rarely a trivial notification. It is a digital pulse check—a signal that the system’s automated immunity has detected an anomaly that requires immediate human intervention. A DBA was analyzing the ASM alert log
There are several possible causes for ASM health checker failures, including:
If a disk group drops below its minimum redundancy requirement (e.g., losing a partner disk in normal redundancy), ASM will immediately dismount it to protect against split-brain scenarios or data corruption.
In many production environments, the Enterprise Manager metric “Checker Failure Detected” is triggered by this exact entry in the ASM alert log. Consequently, the appearance of this message should be treated as a requiring immediate investigation.
Use SQL*Plus connected to the ASM instance to identify which disk group or disk is involved.