Look for disks with a state of FAILED , FORCING , or HUNG . An unhealthy disk is a common cause of the alert.
One failure found. One failure fixed. Back to sleep—until the next thread started to pull. deepen the technical details of the ASM failure, or should we pivot to a post-mortem report style for this story?
The message "ASM Health Checker found 1 new failures" is a proactive alert generated by a background health monitoring process. This Health Checker is like a doctor for your database or system, routinely examining internal components for signs of illness—in this case, corruption, inconsistencies, or failures.
: A disk may have failed, leading to a loss of redundancy or a disk group being forced to dismount. asm health checker found 1 new failures
Go to the console and select the problematic secret. Scroll down to the Rotation configuration section.
SUCCESS: ALTER DISKGROUP... followed by immediate GMON dumping or failure notes.
: Review the ASM alert log file (usually found in the ADR home) for specific ORA- errors or messages about disk evictions. Validate Path Visibility Look for disks with a state of FAILED , FORCING , or HUNG
Loss of physical fiber channel paths, faulty host bus adapters (HBAs), or incorrect multipathing layers ( multipathd ) will drop the physical storage paths. ASM detects this loss of communication as a failed disk heartbeat. 3. Disk Header Mutilation
When a physical disk or storage network pipeline exhibits anomalies, the health checker records a localized failure. It handles these using several specific operations:
There are several possible causes for the ASM Health Checker to report a new failure. Some common causes include: One failure fixed
Recent changes that haven't propagated correctly across a cluster.
The failure can be related to various aspects of ASM, such as:
This alert is not a sign of imminent database doom, but it is a critical early warning that requires a structured and thorough response. This comprehensive guide provides a complete reference for understanding, diagnosing, and resolving the health checker alert, along with actionable best practices to prevent it from occurring again.
Oracle's Health Monitor records every automatic and manual health check. Use the V$HM_RUN view to confirm the execution of the health checker that triggered the alert and to get its specific run ID.
Look for the "Health Checker" section to see the red "Fail" status.