Asm Health Checker Found 1 New Failures

If the header_status reads CANDIDATE or UNKNOWN instead of MEMBER , you must re-add the disk or trigger an ASM disk online operation: ALTER DISKGROUP ONLINE DISK ; Use code with caution. 2. ASM Disk Header Corruption

The ASM Health Checker runs as part of the and CHM (Cluster Health Monitor) . Locate the latest HTML or text report generated by tfactl or orachk .

-- 1. Identify the recent health checks SET LINESIZE 200 PAGESIZE 100 COLUMN name FORMAT a20 COLUMN check_name FORMAT a30 COLUMN start_time FORMAT a30 COLUMN end_time FORMAT a30 SELECT run_id, name, check_name, TO_CHAR(start_time, 'YYYY-MM-DD HH24:MI:SS') AS start_time, TO_CHAR(end_time, 'YYYY-MM-DD HH24:MI:SS') AS end_time, status FROM v$hm_run WHERE check_name LIKE '%ASM%' OR name LIKE 'HM_RUN_%' ORDER BY start_time DESC;

While the "1 new failure" could technically be anything, it usually falls into one of these three categories: A. Disk Corruption or Metadata Inconsistency asm health checker found 1 new failures

This message usually appears alongside other ORA- errors and signals that ASM has identified a problem with the storage layer. Common triggers include: Disk Failures

The alert " ASM Health Checker found 1 new failures " is a critical notification typically found in Oracle Automatic Storage Management (ASM) alert logs. It indicates that the GMON (Group Monitor)

Search for the timestamp of the alert. You will often see a corresponding ORA- error code (like ORA-15078 or ORA-15032 ) that provides the exact technical reason for the health check failure. 4. How to Resolve the Failure Scenario A: Disk Connectivity Issues If the header_status reads CANDIDATE or UNKNOWN instead

The message is a critical warning often found in Oracle Automatic Storage Management (ASM) alert logs. It typically signals that the system has detected a significant issue—such as disk corruption or a communication breakdown—that could lead to a diskgroup being forcibly dismounted .

[Trigger Alert] -> Check ASM Alert Log -> Run ASMCMD/SQL -> Inspect OS Paths -> Rebalance/Remount Step 1: Trace the Associated Errors

The first step is to determine precisely which disk group or component is affected. You can do this by querying Oracle's V$HM_RUN view to review the health check report. Locate the latest HTML or text report generated

) will have created an HTML report. Locate this report to see the specific and description of the failure. Verify ASM Disk Status utility to check the status of your disks and disk groups: asmcmd lsdsk -t asmcmd lsdg Use code with caution. Copied to clipboard Look for disks with a status of Inspect the ASM Alert Log

Execute the CHECK command: ALTER DISKGROUP CHECK ALL; Note: This checks for consistency but does not fix errors. If errors are found, you may need to involve Oracle Support. Scenario C: Space Pressure

: The health checker may trigger a failure if it waits too long (e.g., >15 seconds) for I/O operations to complete on a specific disk. Oracle Forums Recommended Troubleshooting Steps