Health Checker Found 1 New Failures - Asm

Sometimes the failure is not about the disks themselves, but about the ASM instance’s ability to manage them—such as running out of processes or memory in the SGA. 4. How to Resolve the Failure

The most common cause is an inconsistency in the ASM metadata. This can happen due to an unexpected power loss, a bug in the storage firmware, or "lost writes." Run an internal ASM check. ALTER DISKGROUP CHECK ALL; Use code with caution. B. Offline Disks or Path Issues asm health checker found 1 new failures

Regularly monitor your v$asm_operation view. If you see long-running "REBAL" (rebalance) operations following a failure, ensure your ASM_POWER_LIMIT is set high enough to complete the recovery quickly without impacting database I/O. Sometimes the failure is not about the disks

Check v$asm_disk to ensure all disks are ONLINE and HEADER_STATUS is MEMBER . C. Resource Exhaustion This can happen due to an unexpected power

If a path to a physical disk is lost (due to HBA failure or cable issues), ASM might mark the disk as "OFFLINE." If the diskgroup is still mounted but missing a member, the Health Checker will flag it.

To fix the failure, you first have to identify it. You can do this via the Command Line Interface (CLI) using ADRCI . Step A: Access ADRCI Log in to your grid infrastructure server and run: adrci Use code with caution. Step B: Set the Home Path

Run the following command to see the specific failure identified: list failure Use code with caution.