Asm Health: Checker Found 1 New Failures Updated

: A LUN or physical disk has become inaccessible due to storage network (SAN) or hardware failure.

Disks in FORCING state (attempting recovery) or OFFLINE state are the culprits.

Automatic Storage Management (ASM) is Oracle’s volume manager and file system, built specifically for database files. It manages disk groups, handles storage redundancy (Normal, High, or External), and balances I/O. However, even with robust redundancy, disk corruption or metadata corruption can occasionally occur. asm health checker found 1 new failures updated

The is an internal mechanism, part of the ASM Instance , that continuously monitors the integrity of the disk groups, disk headers, and metadata structures. It acts as a preventative tool, alerting administrators to issues before they become full-blown outages, such as data corruption or disk group dismounting.

This article provides a comprehensive overview of what this message means, how to analyze the findings, and steps to resolve the reported failures to avoid database dismounts (e.g., ORA-15130, ORA-15196). What Does "1 New Failures Updated" Mean? : A LUN or physical disk has become

SET LONG 100000; SET LONGCHUNKSIZE 1000; SET PAGESIZE 1000; SET LINESIZE 512; SELECT DBMS_HM.GET_RUN_REPORT('HM_RUN_NAME') FROM DUAL;

By following these steps, you can troubleshoot and resolve ASM health checker failures, ensuring the stability and performance of your Oracle database and ASM environment. It manages disk groups, handles storage redundancy (Normal,

Proactive monitoring—via scheduled health checks, OEM metric alerts, and third‑party tools—ensures that you catch these failures early, often before they impact database availability. In the event of a genuine corruption that cannot be repaired, a robust backup and recovery strategy (including RMAN block recovery) will be your ultimate safeguard.

In this case, the root cause was a transient I/O error that left a metadata reference inconsistent. The automatic repair command corrected the metadata without data loss or downtime.

To properly resolve the alert, it's helpful to understand what typically causes it. Common scenarios that trigger the health checker include: