Asm Health Checker Found 1 New Failures Updated Updated -

The Automatic Diagnostic Repository Command Interface (ADRCI) can be scripted to scan the alert log for health checker messages and send notifications:

Recommended immediate steps (triage checklist)

The ASM Health Checker constantly audits the storage environment's structural and operational integrity. When it logs an updated failure count, it is usually responding to one of four common architecture failures: asm health checker found 1 new failures updated

Do not ignore this alert. Follow this standard triage procedure:

to check the status of your failure groups or disk redundancy? Follow this step-by-step framework to isolate and resolve

Follow this step-by-step framework to isolate and resolve the underlying issue behind the Health Checker failure. Step 1: Trace the Chronological Sequence of Events

Look for the FAILURE_TYPE and FAILURE_STATUS columns. This will tell you if the issue is a disk offline, a corruption block, or a network issue (in the case of ASM on Exadata or Extended Distance clusters). The ASM Health Checker runs continuously within the

The ASM Health Checker runs continuously within the background processes of an ASM instance (specifically managed by components like the and Global Enqueue Service (LMON) ).

This message often precedes a disk group going into an INTERMEDIATE or OFFLINE state.

Always ensure your critical disk groups are at least on "Normal" redundancy to allow the health checker to find and fix issues without taking the database offline.