Asm Health Checker Found 1 New Failures | Updated

The ASM Health Checker can trigger this alert for a variety of reasons. Below are the most frequent root causes encountered in production environments.

asmcmd health check

Or from SQL:

SELECT name, state, type, total_mb, free_mb 
FROM v$asm_diskgroup;

The Automatic Storage Management (ASM) health check utility has identified 1 new failure since the last successful check. This report details the failure and recommended actions.

The ASM health checker does not just detect failures — it maintains a persistent failure record.

The message "ASM Health Checker found 1 new failures updated" is a crucial early warning system. It signifies that your storage layer has lost resilience, even if the database is currently online. Because ASM relies on redundancy to protect data, a "new failure" effectively puts the system in a degraded state.

Immediate investigation is required to determine if the failure is physical (requiring hardware replacement) or logical (requiring resync). Ignoring this alert significantly increases the risk of a total storage outage. asm health checker found 1 new failures updated

The message "ASM Health Checker found 1 new failures" typically appears in the Oracle Automatic Storage Management (ASM) alert log when a critical issue—such as a disk failure or a forced diskgroup dismount—is detected. This is part of Oracle's fault diagnosability infrastructure designed to capture diagnostic data at the first sign of trouble. Immediate Actions to Take

If you see this message, follow these steps to identify and resolve the failure:

Check the ASM Alert Log: Review the alert log (often located in /u01/app/grid/diag/asm/+asm/+ASM/trace/alert_+ASM.log) for errors preceding the health checker message, such as ORA-15130 (diskgroup being dismounted) or ORA-15032.

Run ADRCI: Use the ADR Command Interpreter (ADRCI) to view the specific "incident" or "problem" that was logged. Command: adrci> show problem or adrci> show incident

Verify Diskgroup Status: Log into the ASM instance and check if any diskgroups are offline or if disks have been dropped. SQL> select name, state from v$asm_diskgroup; The ASM Health Checker can trigger this alert

SQL> select name, header_status, mode_status from v$asm_disk;

Investigate I/O Failures: Look for hardware-level issues, such as storage path failures, SAN/NFS connectivity problems, or OS-level permission changes that might have caused the disk to go offline. Common Causes

Disk Path Failure: The OS can no longer see the physical storage device.

Forced Dismount: ASM may force a dismount if too many disks in a failure group are lost, exceeding the redundancy limit.

Communication Issues: In a RAC environment, network or heartbeat failures between nodes can trigger ASM health alerts. Or from SQL: SELECT name, state, type, total_mb,

For automated assistance, you can use tools like Oracle ORAchk to run a comprehensive health check on your entire Oracle stack.

The one-line alert is just a header. Immediately examine the ASM alert log for surrounding messages.

Location of ASM alert log:

Look for entries with timestamps matching the health checker alert. You will often see additional details like:

WARNING: ASM Health Checker found 1 new failures updated
Failure details:
   Disk group: DATA
   Disk: DATA_0003 (path: /dev/mapper/data_disk3)
   Failure type: OFFLINE
   Timestamp: 2025-01-15T14:23:10

This message comes from Oracle ASM (Automatic Storage Management) , typically when you run:

It indicates that the ASM health checker has detected one new failure in the ASM disk group’s redundancy or usability status since the last check, and that failure record has been updated in the ASM metadata or alert log.

Key points: