Check for offline or missing disks in the failing diskgroup:
The message "" typically appears in the Oracle Automatic Storage Management (ASM) alert log when a critical issue—such as a disk failure or a forced diskgroup dismount—is detected . This is part of Oracle's fault diagnosability infrastructure designed to capture diagnostic data at the first sign of trouble. Immediate Actions to Take
. It means the internal health checker has identified a failure in a service or a violation that requires attention. Common Causes Service Instability : Critical daemons (like asm_config_server ) might have hung or crashed. Resource Exhaustion : The disk partition for logs (
If the disk has physically failed, you must replace it at the hardware level. asm health checker found 1 new failures updated
⚠️ : The REPAIR option may not be available for all types of corruption, especially physical disk issues. Use it cautiously and always ensure you have a valid backup before attempting repairs.
: ASM instances may lose sight of a disk due to OS-level permission changes or SAN/storage connectivity issues. Disk Group Redundancy Issues
Understanding the root causes of ASM health check failures is crucial for prevention. Here are some common scenarios: Check for offline or missing disks in the
. This is often triggered when a monitored resource crosses a predefined threshold or a critical daemon stops responding. Immediate Review Checklist To review and resolve this failure, follow these steps: Identify the Failure Source : Navigate to Security > Reporting > Settings > ASM Alerts
Oracle frequently releases patches that improve the robustness of the Health Checker.
Ensure the entire cluster acknowledges the fix: crsctl check crs crsctl stat res -t Use code with caution. To help find the exact fix, let me know: What Oracle Grid Infrastructure version are you running? What errors ( ORA-XXXXX ) show up in your ASM alert log? Is this a standalone (SIHA) or RAC environment? Share public link It means the internal health checker has identified
. This will automatically compare your system state against known bugs and best practices to pinpoint the exact failure. Common Root Causes
: High network latency on the private interconnect caused a temporary node eviction or voting disk timeout. Step 3: Resolution Protocol
Troubleshooting "ASM Health Checker Found 1 New Failures" in Oracle Grid Infrastructure