This comprehensive guide will dissect every aspect of this error message. We will explore what the ASM Health Checker is, why it triggers this alert, how to diagnose the specific failure, and step-by-step remediation strategies.
SQL> SELECT group_number, disk_number, name, state, path FROM V$ASM_DISK WHERE state != 'NORMAL'; asm health checker found 1 new failures updated
Look for the FAILURE_TYPE and FAILURE_STATUS columns. This will tell you if the issue is a disk offline, a corruption block, or a network issue (in the case of ASM on Exadata or Extended Distance clusters). This comprehensive guide will dissect every aspect of
Replace 'HM_RUN_NAME' with the specific run name from the V$HM_RUN table. This will tell you if the issue is
A failing disk, bad sectors, or a disconnected storage path.
If the disk is still NORMAL but shows path errors:
SQL> SELECT header_status, mode_status, path FROM v$asm_disk; Use code with caution.