The response to this finding must be methodical, not panicked. The first step is triage: querying V$ASM_DISK and V$ASM_OPERATION to identify the exact nature of the failure. Is the disk marked FORCED or FAILED ? Has an offline disk exceeded DISK_REPAIR_TIME ? Often, the new failure is a “stale” disk that failed to resync after a transient outage. The solution might be as simple as an ALTER DISKGROUP ... ONLINE DISK command. Other times, the failure points to degraded hardware—a flaky SAS cable, a failing SSD, or a misconfigured multipath. In these cases, the DBA shifts from technician to detective, correlating the ASM alert with OS logs ( dmesg , syslog ) and storage array warnings. The one failure demands a root cause analysis before it metastasizes into a cascade.
The message is a critical warning often found in Oracle Automatic Storage Management (ASM) alert logs. It typically signals that the system has detected a significant issue—such as disk corruption or a communication breakdown—that could lead to a diskgroup being forcibly dismounted . asm health checker found 1 new failures
: A disk group may have been forced to dismount due to lost connectivity or multiple disk failures in a failure group. Disk Header Corruption The response to this finding must be methodical,
Check which home is reporting the error (usually the ASM home): Has an offline disk exceeded DISK_REPAIR_TIME
If you want, I can:
Note: Always back up your metadata and ensure you have a valid backup before running automated repair scripts on production storage. 5. Clearing the Alert