By continuing to use this site, you accept our use of cookies and other online technology to send you targeted advertisements, for social media, for data analytics and to better understand your use of our website. Click here for more information on the types of cookies we use and how to change your cookie settings.

 
Start the party early. Discover our bestselling products. SHOP.

QUICK LINKS

Bose QuietComfort Earbuds Bose Sleepbuds™ II Bose Noise Cancelling Headphones 700 Bose Frames Bose Sport Earbuds

Suggestions

Top results

Related content

Cancel
Stores
Stores

Asm Health Checker Found: 1 New Failures

The first rule of any IT crisis is to check the logs. The alert message itself is a symptom; the log file contains the diagnosis.

This command will provide more detailed information about the failure.

When it prints found 1 new failures , it means a single, distinct event has degraded the cluster's idealized state. Common Root Causes Behind the Failure Alert

# Navigate to your ASM trace directory cd $ORACLE_BASE/diag/asm/+asm/+ASM1/trace/ tail -n 200 alert_+ASM1.log Use code with caution. asm health checker found 1 new failures

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

Troubleshooting AWS ASM: How to Fix "ASM Health Checker Found 1 New Failures"

SQL> SET LONG 100000; SQL> SET LONGCHUNKSIZE 1000; SQL> SELECT DBMS_HM.GET_RUN_REPORT('HM_RUN_361') FROM DUAL; The first rule of any IT crisis is to check the logs

If the analysis confirms a correctable form of corruption, the most direct solution is to run the CHECK command with the REPAIR clause.

To fix the error, you must first uncover exactly what the Health Checker discovered. Follow this step-by-step triage workflow. Step 1: Locate the Diagnostic Report

: Problems during the addition of new disks or voting file refreshes. Immediate Troubleshooting Steps Check the ASM Alert Log : Locate the alert log for your ASM instance (often in /u01/app/oracle/diag/asm/.../trace/alert_+ASM.log When it prints found 1 new failures ,

2026-05-30T10:14:22.102555+01:00 WARNING: Write Failed. group:1 disk:2 AU:4 offset:4190208 size:4096 path:/dev/oracleasm/disks/DATA02 asynchronous result:'I/O error' 2026-05-30T10:14:22.155824+01:00 ORA-15130: diskgroup "DATA" is being dismounted 2026-05-30T10:14:22.193916+01:00 ASM Health Checker found 1 new failures 2026-05-30T10:14:22.201907+01:00 List of instances (total 1) : 1 My inst 1 2026-05-30T10:14:22.210482+01:00 NOTE: initiating dirty detach from lock domain 1 Use code with caution. The Sequence of Events

For long-term monitoring, use the Oracle Autonomous Health Framework to proactively identify issues before they lead to health checker failures. AI responses may include mistakes. Learn more

He dug deeper into the ASM logs. The health checker hadn't flagged a total crash; it had flagged a "Zombie Process" in the health-check script itself. A legacy script, written years ago by an engineer who had long since moved on, had timed out while trying to ping a decommissioned staging server.

process has detected an issue—often a disk failure or a forced dismount—that requires immediate attention What This Alert Means

This is the most frequent partner error. If the storage layer loses connectivity to a device for even a few seconds, Oracle ASM may drop the disk or force a complete dismount of the disk group to protect against data corruption. In your log, it will typically look like this: