Though less common due to ASM mirroring, if you are running an EXTERNAL REDUNDANCY disk group (relying entirely on hardware RAID) and a bad sector corrupts an essential metadata block, the health routine will flag it instantly. Step-by-Step Diagnostic and Resolution Workflow
The error log entry is one of the most critical warnings an Oracle Database Administrator (DBA) can encounter in an Oracle Automatic Storage Management (ASM) environment.
Resource Constraints: Memory exhaustion or disk space limits on the /var or /appdata partitions. Step 1: Identify the Specific Error asm health checker found 1 new failures
Based on standard ASM operational patterns, the failure is likely attributed to one of the following scenarios:
Verification failure due to expired security subscriptions. Though less common due to ASM mirroring, if
This message indicates that the internal ASM Health Checker background framework has detected a critical structural, hardware, or connection failure. This failure is often accompanied by an automated, ungraceful "dirty detach" or an immediate dismount of an active diskgroup.
# As grid user cd $GRID_HOME/log/<hostname>/alert tail -100 alert_+ASM1.log | grep -i "health check" Step 1: Identify the Specific Error Based on
Connect to your ASM instance using sqlplus and run the following command to see a history of Health Monitor runs:
:
Look for lines containing SQL> select * from v$asm_health_check or health_check_summary . You will see a failure line like: "Check: Disk Path Accessibility, Status: FAIL, Details: Disk DATA_0002 path /dev/mapper/asm_data2 is not readable"
