Failures Updated - Asm Health Checker Found 1 New

The REPAIR clause instructs Oracle ASM to automatically fix any inconsistencies found during the check process. After running this command, the alert will be resolved, and the disk group will be consistent.

The health checker identifies a specific occurrence (incident) of a broader problem, such as a lost disk or corrupted block.

Search for the exact timestamp of the health checker failure. Often, the log entry will also include a reference to the affected disk group or an ORA‑ error code (e.g., ORA‑15042, ORA‑15130).

ALTER DISKGROUP <disk group name> CHECK ALL REPAIR; asm health checker found 1 new failures updated

This isn't just another routine log entry; it signals a potential integrity issue within your ASM storage infrastructure. Understanding what this alert means, why it appears, and how to fix it is a core operational skill for any Database Administrator (DBA).

In the complex ecosystem of modern enterprise computing, the Oracle Automatic Storage Management (ASM) layer serves as the critical bridge between the database software and the physical storage hardware. It is the circulatory system of the data center, managing the flow of information to the disks. Within this high-stakes environment, the alert message "ASM Health Checker found 1 new failures updated" is rarely a trivial notification. It is a digital pulse check—a signal that the system’s automated immunity has detected an anomaly that requires immediate human intervention.

The potential causes for such an alert are numerous, ranging from the benign to the catastrophic. It could be a transient I/O error caused by a hiccup in the storage area network (SAN), or it could be the early warning sign of a physical disk sector corruption. In some cases, it may relate to a mismatch in ASM attributes following a patch or a configuration drift. Regardless of the root cause, the Health Checker acts as the canary in the coal mine. By flagging the failure before the database crashes or data is corrupted, it provides the invaluable commodity of time. The REPAIR clause instructs Oracle ASM to automatically

Use ASM’s disk_repair_time attribute to control how long ASM waits before permanently offlining a disk. A higher value (e.g., 6-12 hours) allows time for storage maintenance without triggering "new failures."

Look for active rebalancing or recovery operations that may have been triggered by the failure.

SELECT group_number, name, state, type FROM v$asm_diskgroup; SELECT path, header_status, mode_status, state FROM v$asm_disk; Use code with caution. Search for the exact timestamp of the health checker failure

If a specific disk is permanently offline:

: ASM cannot find a disk that is expected to be part of a disk group.

To proactively detect such issues, Oracle includes a diagnostic framework known as . For ASM, this manifests as the ASM Health Checker —a set of low‑level diagnostic routines that run automatically in the background. These health checks validate various layers of the ASM instance, including: