Asm Health Checker Found 1 New Failures Updated !!top!! Jun 2026

This query will help you identify exactly which health check failed and when it was executed.

: ASM relies heavily on an internal MySQL database. Check for database corruption or space issues by running tmsh load sys config verify or reviewing /var/log/asm for SQL-related errors. Utilize iHealth Diagnostics : Generate a file and upload it to the F5 iHealth portal

: If the disk group is still mounted, manually trigger a metadata check: SQL> ALTER DISKGROUP CHECK ALL; asm health checker found 1 new failures updated

When you see this alert, a methodical investigation is required. Begin by locating the ASM alert log, which is typically found in the following location: <GRID_HOME>/diag/asm/+asm/+<ASM>/alert/log.xml

Check the ASM alert log for accompanying error codes (e.g., ORA-15000 to ORA-15999 ). This query will help you identify exactly which

Conclusion The single-line notice "ASM health checker found 1 new failures updated" is a prompt to investigate. While one new failure may be harmless in a fault-tolerant system, it can also be the first sign of worsening conditions. Rapid, evidence-based triage followed by durable fixes and improved monitoring reduces risk and operational burden.

This message comes from , typically when you run: Utilize iHealth Diagnostics : Generate a file and

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.

The message is a critical alert typically found in the Oracle Automatic Storage Management (ASM) alert logs. It indicates that the Oracle Fault Diagnosability Infrastructure has detected an issue—such as metadata corruption or disk accessibility problems—and has created an "incident" for further investigation . What This Failure Means