health checker has detected a potential issue, such as disk corruption or a hardware-related failure group problem . In Oracle environments, this message often appears in the
Use SQL*Plus connected to the ASM instance to identify which disk group or disk is involved.
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
⚠️ For production systems, always run a manual CHECK first. Review the output. If the repair command risks data loss, Oracle will refuse to apply the repair. In that case, you must restore from backup or use advanced tools (such as RMAN block recovery).
If the SQL diagnostics point to a disk or path failure, move to the operating system level: asm health checker found 1 new failures updated
Do not panic. A "new failure" is an alert, not necessarily a catastrophe. Follow these steps to determine the severity: 1.1 Check the Alert Log
A specific block (often metadata blocks 0-250) becomes unreadable, triggering a health check failure. Hardware Timeout:
A prior error (like an IO error) forced a dismount, triggering this health check finding [Per 2.2.4]. Step-by-Step Resolution Guide 1. Identify the Affected Diskgroup
Use ASM’s disk_repair_time attribute to control how long ASM waits before permanently offlining a disk. A higher value (e.g., 6-12 hours) allows time for storage maintenance without triggering "new failures." health checker has detected a potential issue, such
ALTER DISKGROUP <diskgroup_name> ONLINE DISK <disk_name>;
SQL> ALTER DISKGROUP <disk group name> CHECK ALL REPAIR;
SQL> SELECT path, header_status, mode_status FROM v$asm_disk; . KB88485 - My Oracle Support
Remember: Ignoring the alert can lead to a cascade of failures, especially in lower redundancy configurations. With the diagnostic steps and remediation strategies provided in this guide, you can confidently resolve the alert and restore your ASM environment to full health. If the repair command risks data loss, Oracle
Temporary SAN outages, faulty Host Bus Adapters (HBAs), or bad network switches can break communication lines between the ASM instance and the physical LUNs.
Are you experiencing this alert on an or a standard Oracle RAC cluster ? Share public link
-- Check Disk Group Status SELECT name, state, type FROM v$asm_diskgroup; -- Check Disk Health SELECT path, header_status, mode_status, failgroup, state FROM v$asm_disk WHERE state != 'NORMAL'; Use code with caution. 2. Analyzing the "1 New Failure" ASM failures are often caused by one of three things: