The disk group is normal; the issue might be confined to a single disk.
When your ASM instance registers a failure, use this sequence of administrative tasks to evaluate and fix the problem. 1. Locate the Relevant Trace Files asm health checker found 1 new failures updated
Slow response times from the storage subsystem cause the Oracle ASM instance to drop the impacted disks. The disk group is normal; the issue might
Too many offline disks in the PST disable the read quorum, triggering a forced dismount. Locate the Relevant Trace Files Slow response times
Intermittent loss of connectivity to the SAN/LUNs causes heartbeat timeout warnings (e.g., Waited 15 secs for write IO ).
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.
Re-scans, OS reboots, or sector size changes ( ORA-15085 ) on the SAN break the shared storage layer. 📋 Comprehensive Troubleshooting Guide