Asm Health Checker Found 1 New Failures Updated Jun 2026

Match the redundancy of your disk groups to the importance of the data they store. Use HIGH redundancy for critical databases, NORMAL for most production workloads, and EXTERNAL only when you have hardware RAID protection.

SQL> SET LONG 100000; SQL> SET LONGCHUNKSIZE 1000; SQL> SET PAGESIZE 1000; SQL> SET LINESIZE 512; SQL> SELECT DBMS_HM.GET_RUN_REPORT('run_name_here') FROM DUAL;

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

Look for any disks where the header_status is CANDIDATE (instead of MEMBER ) or mode_status is OFFLINE . 3. Check for Ongoing Rebalances asm health checker found 1 new failures updated

A new failure was identified during the latest ASM health check scan. Current Action Plan: incidents to identify the specific failure. Verifying disk group redundancy and member disk status. Running a manual health check via Oracle AHF/ORAchk to confirm if the issue is persistent.

In this example, --repair tells ASMCMD to automatically fix any errors it encounters in the data disk group. The chkdg command is particularly useful when you need a quick, command-line-driven verification of a disk group's health.

Proactively run ALTER DISKGROUP ... CHECK during maintenance windows. Match the redundancy of your disk groups to

Often, the health checker finds a "failure" simply because a storage array is too slow. Monitor your OS-level tools like iostat or sar .

This message is a summary alert generated by Oracle's health monitoring. Common triggers include:

Operational impacts

WARNING: ASM Health Checker found 1 new failures updated Failure details: Disk group: DATA Disk: DATA_0003 (path: /dev/mapper/data_disk3) Failure type: OFFLINE Timestamp: 2025-01-15T14:23:10

A disk was dropped or taken offline due to I/O errors, but the redundancy (if using Normal or High redundancy) kept the database running. Step-by-Step Resolution Guide 1. Identify the Specific Failure

The one-line alert is just a header. Immediately examine the ASM alert log for surrounding messages. Check for Ongoing Rebalances A new failure was

SELECT name, state, type, total_mb, free_mb, offline_disks FROM v$asm_diskgroup;