: High network latency on the private interconnect caused a temporary node eviction or voting disk timeout. Step 3: Resolution Protocol
tail -100 $ORACLE_BASE/diag/asm/+asm/+ASM1/trace/alert_+ASM1.log
The "ASM Health Checker found 1 new failures" alert is not a cause for panic but an invitation to investigate. With a methodical approach—checking the alert log, using V$HM_RUN , running a manual ALTER DISKGROUP CHECK , and applying the appropriate repair—you can resolve most issues without data loss. asm health checker found 1 new failures updated
If a disk group shows DISMOUNTED or BROKEN , this is the source of your health checker failure. Check Individual Disk Status
Update your UDEV rules file if permissions reset after a reboot. Reload UDEV triggers using udevadm trigger . Clear the Health Checker Alert : High network latency on the private interconnect
Once you have identified the alert log, follow these steps to gather essential diagnostic information:
The most direct diagnostic command is the built‑in disk group validation: If a disk group shows DISMOUNTED or BROKEN
Before making any changes, retrieve the trace file that corresponds to the background error. Look for lines right above the alert in your ASM alert log to identify the specific RBAL or GMON background trace file.
Health checks detect file corruptions, physical and logical block corruptions, undo and redo inconsistencies, and data dictionary corruption. When any of these targeted validations fail, the Health Checker logs an entry into the ASM alert log ( alert_+ASM.log ) and, in many monitoring environments, triggers an Enterprise Manager (OEM) metric alert.