Asm Health Checker Found: 1 New Failures
: One or more LUNs/disks became inaccessible due to hardware, cable, or storage controller issues. Write I/O Errors
The alert itself is a summary. To fix the issue, you must find the specific failure code. Log into the BIG-IP Configuration Utility (GUI). Navigate to Security > Overview > Health Reports.
Because the initial alert does not specify the exact nature of the failure, you must collect diagnostic details using Oracle’s command-line utilities. Check the Grid Infrastructure Alert Log
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. asm health checker found 1 new failures
-- 2. From the output, note the NAME of the relevant health check run (e.g., 'HM_RUN_123') -- 3. Generate the detailed report for that specific run SET LONG 100000 LONGCHUNKSIZE 1000 LINESIZE 512 SELECT DBMS_HM.GET_RUN_REPORT('HM_RUN_123') FROM DUAL;
Monitors input/output (I/O) latency and connection drops between nodes.
The failure relates to performance bottlenecks, slow I/O response times, or asymmetrical disk sizes within a disk group. : One or more LUNs/disks became inaccessible due
) identifies a configuration issue or a hardware fault that doesn't match the established "best practices" or previous healthy state What This Usually Means
Conclusion “asm health checker found 1 new failures” is more than a log line: it is an early warning. Responding effectively requires prompt triage, methodical diagnosis, and decisive remediation—combined with post-incident learning and engineering improvements to reduce recurrence. By classifying possible causes (storage, probe, resource, network, regression, auth), following a disciplined RCA approach, and implementing monitoring and automation best practices, teams can convert such alerts from frightening unknowns into manageable events and steadily improve system resilience.
Look for disks with a state of FAILED , FORCING , or HUNG . An unhealthy disk is a common cause of the alert. Log into the BIG-IP Configuration Utility (GUI)
. This message indicates that a failure has been logged in the Automatic Storage Management (ASM) health check framework, often related to disk group dismounts, header corruption, or voting file issues. Oracle ASM Health Check Failure Report Report Field Description / Details Alert Message ASM Health Checker found 1 new failures System Component Oracle Automatic Storage Management (ASM) Detection Source ASM Alert Log (typically located at diag/asm/+asm/ /trace/alert_+asm.log Incident Status
If the fix is correct, v$asm_health_check will show status='RESOLVED' for that failure ID.
Locate the exact timestamp of the error in the ASM alert log. Look for preceding errors like ORA-15130 (diskgroup being dismounted) or specific path-related I/O errors.
[Your Name / Automated Monitoring System] Attachments: Full ASM health check log (if available)
ALTER DISKGROUP DATA ONLINE DISK 'DATA_0001' POWER 3; -- wait for rebalance to complete SELECT * FROM v$asm_operation;
