Asm Health Checker Found 1 New Failures Updated [extra Quality] Official

If the underlying issue was a temporary glitch (e.g., a loose fiber cable or a brief network blip), the disk might still be repairable. If the OS can see the disk again, you may be able to issue:

Check REQUIRED_MIRROR_FREE_MB . If your usable space is negative, the system may not have enough room to rebalance data and restore redundancy after this failure.

When the checker detects a new anomaly that was not present in its previous scan, it increments a failure count and writes the message: to the ASM alert log.

Rarely, the message appears without any actual hardware or storage issue. This can happen due to:

Log into your ASM instance via SQL*Plus ( sqlplus / as sysasm ) and run the following to see the status of your disks: asm health checker found 1 new failures updated

Verify if the number of disks in the diskgroup has dropped below required redundancy.

This command performs a consistency check on the metadata and file directory of the named disk group. If an inconsistency is found, the command returns a description of the problem, such as:

Although rare, ASM metadata (e.g., the File Directory, Alias Directory, or PST (Partnership and Status Table)) can become corrupted due to hardware errors or improper shutdowns. The health checker’s metadata validation routines will detect inconsistencies.

For persistent issues, you may need to gather a diagnostic package using the Incident Packaging Service (IPS) and upload it to Oracle Support exact command If the underlying issue was a temporary glitch (e

This alert indicates that the Oracle Automatic Storage Management (ASM)

Proactive monitoring—via scheduled health checks, OEM metric alerts, and third‑party tools—ensures that you catch these failures early, often before they impact database availability. In the event of a genuine corruption that cannot be repaired, a robust backup and recovery strategy (including RMAN block recovery) will be your ultimate safeguard.

Path: /u01/app/oracle/diag/asm/+asm/ /trace/alert_ .log .

Means the health checker or rebalance operation has updated the status of these errors, which may have happened after disk additions or storage-level changes. When the checker detects a new anomaly that

One disk was lagging, its I/O response times ballooning into the hundreds of milliseconds.

The ominous log line indicates that the Oracle Automatic Storage Management (ASM) background monitoring system has detected an active problem within your storage tier. This alert is immediately appended to the ASM alert log ( alert_+ASM.log ). It often surfaces alongside an explicit storage operation disruption, such as a diskgroup forced dismount or a hardware-level I/O failure.

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

A disk was dropped or taken offline due to I/O errors, but the redundancy (if using Normal or High redundancy) kept the database running. Step-by-Step Resolution Guide 1. Identify the Specific Failure