Once you have fixed the underlying physical or logical issue, the Health Checker should automatically update during its next run. However, if the status remains "Failed" in the views, you can manually trigger a re-run of the health check or use ADRCI to purge the alert. Summary Checklist
After the underlying issue is resolved (e.g., the disk is back online or the metadata is repaired), you need to "close" the failure in the ADR so the health checker stops reporting it. Inside ADRCI : asm health checker found 1 new failures
Based on standard ASM operational patterns, the failure is likely attributed to one of the following scenarios: Once you have fixed the underlying physical or
If only one new failure exists, this yields exactly one row with actionable details. Inside ADRCI : Based on standard ASM operational
Database Administration Team / System Health Monitoring Group Date: [Insert Date] Priority: Medium
Before troubleshooting the error, understanding the tool is crucial. The ASM Health Checker is an automatic, background diagnostic framework introduced in Oracle Grid Infrastructure 11gR2 (enhanced in 12c and 19c). It runs periodically (typically every hour or on specific triggers) to validate:
It turned out a routine disk add operation from earlier that morning had gone sideways. A subtle corruption on had been lying in wait. When the ASM rebalance operation hit that specific block, the Health Checker—a silent guardian that usually stays in the background—spotted the anomaly and pulled the emergency brake to prevent further data loss.