Oracle's Autonomous Health Framework (AHF) provides additional diagnostic tools that can assist support engineers in resolving complex corruption issues efficiently.
A formal review of this failure should include an investigation of the root cause and an immediate assessment of data risk.
: High network latency on the private interconnect caused a temporary node eviction or voting disk timeout. Step 3: Resolution Protocol asm health checker found 1 new failures updated
Oracle tracks all health check executions in the V$HM_RUN view. Run the following query to see recent checks:
A prior error (like an IO error) forced a dismount, triggering this health check finding [Per 2.2.4]. Step-by-Step Resolution Guide 1. Identify the Affected Diskgroup Step 3: Resolution Protocol Oracle tracks all health
Significant performance degradation or I/O bottlenecks may also trigger warnings that require a manual Next Steps for Remediation Identify affected Diskgroup: V$ASM_DISKGROUP view for any group not in a Review ASM Logs: ADRCI tool show alert -p "message_text like '%error%'" to find the exact timestamp and error code. Validate Hardware:
Do not ignore this alert. Follow this standard triage procedure: asm health checker found 1 new failures updated
The potential causes for such an alert are numerous, ranging from the benign to the catastrophic. It could be a transient I/O error caused by a hiccup in the storage area network (SAN), or it could be the early warning sign of a physical disk sector corruption. In some cases, it may relate to a mismatch in ASM attributes following a patch or a configuration drift. Regardless of the root cause, the Health Checker acts as the canary in the coal mine. By flagging the failure before the database crashes or data is corrupted, it provides the invaluable commodity of time.
Based on real‑world case studies and Oracle diagnostic reports, the “found 1 new failures” alert is most frequently caused by:
Proactively run ALTER DISKGROUP ... CHECK during maintenance windows.