Asm Health Checker Found 1 New Failures Updated Jun 2026

If errors are found, you may need to:

ASM Health Checker found 1 new failures updated, ASM alert log, Oracle ASM troubleshooting, disk group failure, v$asm_diskgroup, offline disks, ASM metadata corruption, multipath failure, Oracle RAC health check.

The health checker might run many times successfully, but a previously latent corruption (for example, a block that was never read) becomes discovered. In this case, the message “found 1 new failures” may be the first indication of a problem that has existed for weeks.

Follow this step-by-step framework to isolate and resolve the underlying issue behind the Health Checker failure. Step 1: Trace the Chronological Sequence of Events asm health checker found 1 new failures updated

ASM Health Check Report – New Failures Detected

Automatic Storage Management (ASM) is a crucial component of Oracle databases, providing a robust and efficient storage management system. However, like any complex system, ASM can encounter issues that impact database performance and security. To identify and address these issues, Oracle provides the ASM Health Checker, a utility that monitors ASM's overall health and alerts administrators to potential problems. In this essay, we will discuss the importance of ASM Health Checker, its functionality, and what it means when it reports "Found 1 new failures updated."

The alert is a call to action. It usually indicates a physical storage hiccup or a metadata inconsistency. By checking the ASM alert logs and querying v$asm_disk , you can usually pinpoint the culprit disk and bring it back online or replace it before a total outage occurs. If errors are found, you may need to:

Bad blocks on physical storage devices are another common cause. Even if the storage appears healthy at a high level, individual blocks can become corrupted due to:

If you are an Oracle Database Administrator (DBA) managing an Oracle Real Application Clusters (RAC) environment, you have likely encountered a cryptic but critical message in your alert logs or monitoring console:

The "ASM Health Checker found 1 new failures" alert is not a cause for panic but an invitation to investigate. With a methodical approach—checking the alert log, using V$HM_RUN , running a manual ALTER DISKGROUP CHECK , and applying the appropriate repair—you can resolve most issues without data loss. Follow this step-by-step framework to isolate and resolve

: Changes to initialization parameters or clusterware settings that don't align with Oracle's Recommended Best Practices Troubleshooting Steps

Use SQL to identify malfunctioning disks:

Oracle's ASM command-line utility ( asmcmd ) offers a powerful alternative for troubleshooting and repairing disk groups. The chkdg command can be used to check and optionally repair disk group metadata without using SQL: