Asm Health Checker Found 1 New Failures Updated May 2026

When the health checker reports a "new failure," it is rarely vague. It usually points to one of three specific categories:

1. Disk Accessibility Issues (I/O Errors) The most common cause is a transient or permanent I/O failure on a specific disk within a Disk Group. If a disk is slow to respond, or if the underlying storage array reports a read/write error, ASM marks the disk as "offline" or flags the error. The "1 new failure" often refers to a specific disk in a failure group becoming inaccessible.

2. Redundancy Loss In a Normal or High Redundancy ASM setup, data is mirrored. If one mirror copy becomes corrupted or unavailable, ASM can still function on the remaining copies. The health checker will flag this as a failure because the system is no longer fully redundant. A second disk failure during this state could result in data loss. asm health checker found 1 new failures updated

3. Corruption or Metadata Mismatch Occasionally, the failure is logical rather than physical. The health checker runs validation algorithms on ASM metadata (the maps that tell ASM where data lives). If it finds a mismatch between the metadata and the physical blocks, it logs a failure.

| Failure Type | Example | |-------------|---------| | Disk offline | A disk in a disk group is offline or missing. | | Disk path error | Underlying LUN/device path inaccessible. | | Read/write errors | OS or storage reports I/O errors. | | Stale disk | Disk not synchronized with partner disks. | | Failure group issues | Entire failure group degraded. | When the health checker reports a "new failure,"

If you are an Oracle Database Administrator (DBA), seeing the message "ASM Health Checker found 1 new failures" in your alert logs or enterprise manager console is a call to immediate action. While the database may still be running, this message indicates that the Automatic Storage Management (ASM) layer—which handles the physical storage logic for the database—has detected a deviation from expected parameters.

This alert is generated by the ASM health check background process. Unlike a hard crash, which stops operations immediately, this alert suggests a "soft failure" or a predictive failure that requires diagnosis before it escalates into data loss or downtime. If you are an Oracle Database Administrator (DBA),

If the disk is still NORMAL but shows path errors: