Asm Health Checker Found 1 New Failures Today

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

Look for MOUNTED state but with disks OFFLINE or UNUSABLE.

Error example: Attribute 'compatible.asm' value '19.0.0.0.0' higher than software version '12.2.0.1.0'

Fix:

ALTER DISKGROUP DATA SET ATTRIBUTE 'compatible.asm' = '12.2';

For the disk mentioned in the failure detail: asm health checker found 1 new failures

# Check if device exists
ls -l /dev/oracleasm/disks/   (if using ASMLIB)
or
ls -l /dev/mapper/ | grep asm
The asm health checker found 1 new failures alert is Oracle’s way of saying: "Something in your storage stack is not perfect." In most cases, it's a disk path issue or an offline disk that can be fixed with a few commands. However, ignoring even one failure invites gradual degradation.
By following the diagnostic steps, applying the appropriate fix, and implementing preventive measures like ASMFD and regular scrubbing, you can ensure that this alert remains a minor reminder—not a major incident.
Remember: A healthy ASM is the silent foundation of a robust Oracle database. Listen to its health checker, and your database will thank you with uptime. Look for MOUNTED state but with disks OFFLINE

Have you encountered an unusual "1 new failure" not covered here? Share your specific error message—solutions vary by Oracle version (11.2 to 23ai) and storage vendor.

Subject: [ALERT] ASM Health Checker Detected 1 New Failure - Immediate Investigation Required
Use ASM Filter Driver (ASMFD) instead of raw devices or ASMLIB. It automatically enforces permissions and detects failures faster. For the disk mentioned in the failure detail:


Short-term (Within 24 hours)



Long-term




If you manage Oracle Grid Infrastructure (GI) or a standalone Automatic Storage Management (ASM) instance, one notification can send a chill down your spine: "ASM health checker found 1 new failures."
This message, often found in your alert log, crsd.log, or email alerts from Enterprise Manager (EM12c/13c), indicates that the automated ASM Health Checker has detected a new issue affecting the integrity, availability, or performance of your ASM environment. Ignoring it is not an option; unresolved failures can lead to disk group mount issues, I/O latency, or even database crashes.
This article provides a 360-degree breakdown of this alert: what triggers it, how to diagnose the root cause, step-by-step repair procedures, and long-term prevention strategies.