Asm Health Checker Found 1 New Failures Updated !!exclusive!! < FAST >

If you're an Oracle DBA, the first time you encounter the message in your alert logs can be concerning. This article provides a comprehensive guide to understanding this alert, diagnosing the underlying issues, and implementing the correct resolution steps to restore your ASM infrastructure to full health.

: A failure might be triggered if a disk group drops below its required redundancy level (e.g., a disk failing in a "Normal" redundancy group). Space Constraints

Check for offline or missing disks in the failing diskgroup:

: ASM cannot find a disk that is expected to be part of a disk group. asm health checker found 1 new failures updated

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

Alternatively, dynamically add a new disk to the group to trigger an automatic rebalance.

You can also find the traditional text-based alert log for ASM, typically in: If you're an Oracle DBA, the first time

If the failure is directly related to storage, the ASM instance alert log will pinpoint the disk or group: $GRID_BASE/diag/asm/+asm/+asm1/trace/alert_+asm1.log Use code with caution. Step 2: Identify Common Causes of ASM Failures

While the message itself is a general notification, the "1 new failure" usually stems from one of the following:

command to validate that all disks are present and have the correct header status. Examine Cluster Health : Ensure that the Oracle Grid Infrastructure is running correctly across all nodes using crsctl check crs Space Constraints Check for offline or missing disks

When it detects a discrepancy—such as a corrupted metadata block, a disk timeout, or an offline disk—it logs a "failure." The "Updated" status usually means the health check engine has refreshed its findings and confirmed that the issue is persistent and requires administrator intervention. Common Causes for This Alert

asmcmd health check