Asm Health Checker Found 1 New Failures ★ Reliable & Newest
The log warning indicates that an Oracle Automatic Storage Management (ASM) background monitoring process has detected a critical hardware, connectivity, or configuration issue. This message frequently surfaces in the ASM alert log immediately following infrastructure complications like I/O timeouts, sector corruptions, or storage network drops. When it drops into your logs, it signals that the ASM layer has isolated a fault to protect your database cluster from split-brain scenarios or data loss. Understanding the ASM Health Checker Architecture
:
:
The system is designed to run these checks periodically. When it finds a new issue, it logs the message "ASM Health Checker found 1 new failures" in the ASM alert log, located at <GRID_HOME>/diag/asm/+asm/+<ASM>/alert/log.xml . This alert is often also picked up and reported by Oracle Enterprise Manager (OEM) as a 'Checker Failure Detected' event.
The alert itself is generic. To find out what actually failed, you need to query the ASM instance. asm health checker found 1 new failures
This will return a list of all health checks, like this sample output: | run_id | name | check_name | start_time | end_time | status | |---|---|---|---|---|---| | 361 | HM_RUN_361 | DB Structure Integrity Check | 2011-11-13 11:02:11 | 2011-11-13 11:02:19 | COMPLETED | This step helps you correlate the alert's timestamp with the corresponding health check run.
sqlplus / as sysasm SET LINESIZE 200 COL failure_type FORMAT a30 COL detail FORMAT a60 SELECT failure_id, failure_type, check_name, time_detected, status, detail FROM v$asm_health_check WHERE status = 'FAIL' ORDER BY time_detected DESC; The log warning indicates that an Oracle Automatic
Troubleshooting "ASM Health Checker Found 1 New Failures" in Oracle RAC
The response to this finding must be methodical, not panicked. The first step is triage: querying V$ASM_DISK and V$ASM_OPERATION to identify the exact nature of the failure. Is the disk marked FORCED or FAILED ? Has an offline disk exceeded DISK_REPAIR_TIME ? Often, the new failure is a “stale” disk that failed to resync after a transient outage. The solution might be as simple as an ALTER DISKGROUP ... ONLINE DISK command. Other times, the failure points to degraded hardware—a flaky SAS cable, a failing SSD, or a misconfigured multipath. In these cases, the DBA shifts from technician to detective, correlating the ASM alert with OS logs ( dmesg , syslog ) and storage array warnings. The one failure demands a root cause analysis before it metastasizes into a cascade. Understanding the ASM Health Checker Architecture : :
Finding Name : Datafile is old Type : FAILURE Priority : HIGH Message : Datafile 2: 'H:\PATH\UNDO.DATA1' needs media recovery
By following these best practices and resolving the issue reported by the ASM Health Checker, you can ensure the health and performance of your ASM infrastructure and prevent future failures.