Often, the health checker finds a "failure" simply because a storage array is too slow. Monitor your OS-level tools like iostat or sar .
This command checks the consistency of the metadata directory for the specified disk group, performing checks on all disks in that group. If an inconsistency is found, you’ll get a detailed error message in the alert log indicating the nature of the problem.
This error typically appears when the ASM instance performs an internal check and encounters an issue that could lead to a disk group being forced to dismount. Why Did This Happen? asm health checker found 1 new failures updated
If a disk was accidentally taken offline or lost connectivity but is now accessible:
When Oracle Grid Infrastructure runs its automated diagnostic scripts, the ASM Health Checker (often managed via chm , ahf , or tfactl ) actively monitors the health of ASM disk groups, metadata consistency, and background processes. Seeing this alert means a new hardware or software validation check has just failed. You must investigate immediately to prevent disk group dismounts or database instances crashing. Step 1: Locate the Diagnostic Logs Often, the health checker finds a "failure" simply
The alert message is just the "headline." You need to find the specific error code (like ORA-15032 or ORA-15078).
The ASM Health Checker is a proactive diagnostic utility that runs within the Oracle Grid Infrastructure. It constantly monitors the state of ASM disk groups, metadata consistency, and background processes. If an inconsistency is found, you’ll get a
The Health Checker warning is an outcome, not the source error. You must inspect the ASM trace and alert logs to find out exactly what happened seconds before the failure was printed. KB88485 - My Oracle Support
Based on real‑world case studies and Oracle diagnostic reports, the “found 1 new failures” alert is most frequently caused by: