If the health check failed because a disk group hit 100% capacity:
Then the health checker will flag this as a new failure.
Re-scans, OS reboots, or sector size changes ( ORA-15085 ) on the SAN break the shared storage layer. 📋 Comprehensive Troubleshooting Guide
Once you have identified the specific health check run from the V$HM_RUN view, retrieve the full report: asm health checker found 1 new failures updated
Proactively run ALTER DISKGROUP ... CHECK during maintenance windows.
SELECT path, disk_number, header_status, state, mount_status FROM v$asm_disk WHERE group_number = (SELECT group_number FROM v$asm_diskgroup WHERE name = 'YOUR_DISKGROUP'); Use code with caution. 4. Verify Physical Connectivity (OS Level)
[Insert Date] Host/Cluster: [Insert Environment Name] Severity: Warning / Critical (as applicable) If the health check failed because a disk
SELECT * FROM v$asm_disk_iostat WHERE read_errs > 0 OR write_errs > 0 OR bytes_read = 0;
Which environment are you running this in? I can tailor the post if it's for a specific platform like Oracle Cloud K14194: Troubleshooting the BIG-IP ASM MySQL database
SELECT group_number, name, state, type FROM v$asm_diskgroup; SELECT path, header_status, mode_status, state FROM v$asm_disk; Use code with caution. CHECK during maintenance windows
Slow response times from the storage subsystem cause the Oracle ASM instance to drop the impacted disks.
Search for keywords like ORA- , ASM , or ERROR around the timestamp of the health checker alert. 3. ASM Instance Alert Log
SELECT name, state, type, total_mb, free_mb, offline_disks FROM v$asm_diskgroup;