
Asm Health Checker - Found 1 New Failures Updated
The ASM alert log contains a chronological log of messages and errors. Scan for the timestamp of the "ASM Health Checker found 1 new failures" message to see what other errors are logged around the same time. This can provide critical clues about the specific problem.
Share public link
SELECT group_number, name, state, type, total_mb, free_mb FROM v$asm_diskgroup; Use code with caution. asm health checker found 1 new failures updated
When managing Oracle Automatic Storage Management (ASM), receiving an alert stating can be alarming. This message usually appears in the ASM alert log or Oracle Enterprise Manager (OEM) and indicates that the background health check process has detected a potential issue with the disk group structural integrity or a device, which requires immediate attention to avoid downtime.
: Run tfactl status to ensure the Autonomous Health Framework is active. The ASM alert log contains a chronological log
A physical drive, virtual block device, or storage area network (SAN) path experiences deep queue latency or drops offline. 2. Force Dismount Triggers
The ASM instance triggers a "dirty detach" from the lock domain, temporarily freezing portions of the Global Resource Directory (GRD) to isolate the damaged disk group while keeping unaffected groups online. Technical Context: Log Snippet Analysis Share public link SELECT group_number, name, state, type,
The message is a critical warning. However, with systematic investigation of the diskgroup status and OS-level paths, this can often be resolved by taking a disk offline or re-silvering in a high-redundancy environment [Per 2.2.3].
Do not guess the cause of the failure. Oracle logs the exact root cause across several diagnostic files. Check these locations first: 1. TFA and Autonomous Health Framework (AHF)
In rare cases, the disk group metadata is temporarily inconsistent but not corrupt. Unmounting and remounting the group can force a metadata refresh:
SQL> SELECT name, state, type, total_mb, free_mb, required_mirror_free_mb FROM V$ASM_DISKGROUP;