Asm Health Checker Found 1 New Failures May 2026

The alert "ASM Health Checker found 1 new failures" is a critical notification from Oracle's Automatic Storage Management (ASM) health monitoring system. It typically appears in the ASM alert logs or via automated email notifications when a storage-related incident is detected. Failure Overview

This specific message indicates that the Fault Diagnosability Infrastructure has identified a new incident in the Automatic Diagnostic Repository (ADR). While "1 new failure" is a generic count, it often points to one of the following underlying issues:

Disk Group Instability: A disk may have failed, leading to a loss of redundancy or a disk group being forced to dismount.

Metadata Corruption: Corruption in ASM metadata blocks (typically within the first 250 blocks) detected during routine operations or rebalancing.

Rebalance Failures: An error occurring during the addition or removal of disks, often accompanied by background process (ARB0) alerts.

Resource State Changes: CRS (Cluster Ready Services) resources moving to an INTERMEDIATE or OFFLINE state due to storage latency or connectivity issues. Immediate Diagnostic Actions

To identify the exact cause, execute the following steps within your environment:

Check the ADRCI Utility:Use the ADR Command Interpreter (ADRCI) to list the details of the specific failure. adrci> list failure Use code with caution. Copied to clipboard

This command provides a unique Failure ID and a description of the problem.

Inspect ASM Alert Logs:Locate the log file (usually in the trace directory of your Oracle Base) to see the events leading up to the "1 new failure" message. Look for: ORA-15xxx errors (ASM-specific).

SUCCESS: ALTER DISKGROUP... followed by immediate GMON dumping or failure notes. asm health checker found 1 new failures

Run Data Recovery Advisor:If the failure involves data loss or disk group mounting issues, use RMAN to get a repair recommendation: RMAN> list failure; RMAN> advise failure; Use code with caution. Copied to clipboard

Query V$ Views:Verify the status of your disks and current operations:

Disk Status: SELECT name, path, mount_status, header_status, state FROM v$asm_disk;

Active Operations: SELECT operation, state, est_minutes FROM v$asm_operation; Common Remediation Steps KB88485 - My Oracle Support

6.1 Proactive Monitoring

Set up alerts on v$asm_health_check itself:

-- Create a daily check script
spool asm_health_report.html
SELECT * FROM v$asm_health_check WHERE status='FAIL';
spool off
-- Email the report via crontab or OEM.

Step 1: Locate the Full Failure Details

The message asm health checker found 1 new failures is just the headline. The details are written to the ASM alert log.

# As grid user
cd $GRID_HOME/log/<hostname>/alert
tail -100 alert_+ASM1.log | grep -i "health check"

Look for lines containing SQL> select * from v$asm_health_check or health_check_summary. You will see a failure line like:
"Check: Disk Path Accessibility, Status: FAIL, Details: Disk DATA_0002 path /dev/mapper/asm_data2 is not readable"

Next Steps

Please acknowledge this alert in the monitoring dashboard. If the issue is resolved, update the ticket with the root cause analysis (RCA).

Note: If "ASM" in your context refers to Oracle Automatic Storage Management, the focus of this write-up should shift immediately to Disk Group redundancy, ASM instance connectivity, and I/O latency checks.

The error message "ASM Health Checker found 1 new failures" typically appears in the Oracle ASM alert logs when the system detects an issue with a disk or disk group The alert "ASM Health Checker found 1 new

. This message indicates that a failure has been logged in the Automatic Storage Management (ASM) health check framework, often related to disk group dismounts, header corruption, or voting file issues. Oracle ASM Health Check Failure Report Report Field Description / Details Alert Message ASM Health Checker found 1 new failures System Component Oracle Automatic Storage Management (ASM) Detection Source ASM Alert Log (typically located at diag/asm/+asm//trace/alert_+asm.log Incident Status

(Requires immediate investigation to prevent data loss or service disruption) Potential Causes & Findings Disk Group Dismount

: A disk group may have been forced to dismount due to lost connectivity or multiple disk failures in a failure group. Disk Header Corruption

: The metadata (headers) on one or more ASM disks may be corrupted or in a "FORMER" or "PROVISIONED" status instead of "MEMBER". Voting File Issues

: If the ASM disk group hosts the Cluster Registry (OCR) or Voting Disks, a failure can cause node evictions or cluster instability. Storage Latency/I/O Timeouts

: 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

The message " asm health checker found 1 new failures typically appears in environments using Oracle Automatic Storage Management (ASM) when an automated health check tool (like Oracle ORAchk Oracle EXAchk

) identifies a configuration issue or a hardware fault that doesn't match the established "best practices" or previous healthy state What This Usually Means

When this alert is triggered, it indicates that a recent scan has detected a deviation in your ASM environment. Common causes for a single new failure include: Disk Path Issues

: A single disk path has become unavailable, even if the disk is still accessible via a redundant path. Disk Group Redundancy Step 1: Locate the Full Failure Details The

: One of the disks in a "Normal Redundancy" disk group has failed, putting the group in a "degraded" state. Parameter Mismatches : An ASM instance parameter (like ASM_POWER_LIMIT

) has been changed and no longer aligns with recommended settings. Offline Disks

: A disk has been taken offline due to I/O errors but has not yet been dropped from the disk group. Oracle Forums Recommended Steps to Investigate Check the Health Check Report : The tool that generated this message (likely

) 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

: Review the ASM alert log file (usually found in the ADR home) for specific ORA- errors or messages about disk evictions. Validate Path Visibility

: Ensure the OS can still see all physical devices associated with the ASM disks. Oracle Help Center For more detailed troubleshooting, you can refer to the Oracle Automatic Storage Management documentation or check for tool-specific errors on the Oracle Support portal ASMCMD commands to check for disk redundancy or rebalance status?

Here’s a structured feature implementation for “ASM Health Checker found 1 new failure” — suitable for a monitoring or alerting system.

3. ASM Metadata Corruption

Rare, but serious. Corruption in the file directory (KFD) or allocation tables can cause "stale metadata" errors. Often seen after abnormal cluster shutdowns.

Post-incident actions (short incident report template)

Step-by-step troubleshooting (prescriptive)

  1. Identify the failing check name and exact error message.
  2. Classify the failure: Availability, Performance, Integrity, Configuration, or Security.
  3. Reproduce locally or on a non-production instance, if possible.
  4. If Availability:
    • Verify process is running.
    • Restart service if safe and observe logs.
    • Check port, firewall, and LB rules.
  5. If Performance:
    • Capture current metrics (CPU, memory, I/O, network).
    • Check recent spikes correlated with failure time.
    • Scale up or roll back recent load changes if needed.
  6. If Integrity/Config:
    • Validate current configuration versus source-of-truth.
    • Reapply configuration from the trusted source.
    • Run any integrity or schema checks.
  7. If Dependency:
    • Ping/connect to dependency.
    • Review authentication and TLS certs; confirm expiry dates.
    • Check network routes and DNS resolution.
  8. If Credentials/Permissions:
    • Verify the account/keys used by the service are valid and not expired.
    • Roll back changed permissions or reissue credentials if necessary.
  9. After fix attempt:
    • Re-run the failing health check until it passes consistently.
    • Monitor metrics and logs for at least 30–60 minutes.
  10. If unable to resolve:

Part 5: Clearing the Failure from Alert Log

After fixing the issue, the ASM health checker will automatically re-evaluate within 1 hour (by default). To force an immediate recheck:

sqlplus / as sysasm
EXEC DBMS_SCHEDULER.RUN_JOB('SYS.ASM_HEALTH_CHECK_JOB');
-- Or manually:
SELECT * FROM table(asm_health_check());

If the fix is correct, v$asm_health_check will show status='RESOLVED' for that failure ID.

To acknowledge and purge the failure from the persistent repository (without waiting for auto-clear):

DECLARE
  v_fid NUMBER;
BEGIN
  SELECT failure_id INTO v_fid FROM v$asm_health_check WHERE status='FAIL' AND rownum=1;
  DBMS_SCHEDULER.SET_ATTRIBUTE('SYS.ASM_HEALTH_CHECK_JOB','COMMENTS','Manually cleared');
  EXECUTE IMMEDIATE 'BEGIN SYS.ASM_HEALTH_CHECK_PURGE('||v_fid||'); END;';
END;
/
X

Stay up to date with the latest SNOW news