Asm Health Checker Found 1 New Failures Updated Instant

: Log into the ASM instance as SYSASM and check the state of your disk groups: SQL> SELECT name, state FROM v$asm_diskgroup;

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. asm health checker found 1 new failures updated