: Corruption in the ASM metadata blocks, which can happen during intensive operations like rebalancing. Configuration Issues
If the failure coincides with a scheduled credential rotation, the rotation Lambda function may have failed mid-process.
When the health checker reports a new failure, the underlying issue almost always falls into one of four categories:
This command checks and attempts to repair the found corruption, which typically resolves the alert. asm health checker found 1 new failures
The host machine running the ASM instance may be experiencing resource contention, causing the health check script to lag or fail execution.
One or more disk groups have breached the free space threshold, or an unbalanced rebalance operation has stalled. How to Fix: Check the capacity and imbalance of your disk groups:
The ASM module is heavy on logging. If the /var or /appdata partitions reach 100%, the health checker will immediately trigger a failure. Symptoms: "Disk partition /var has insufficient space." : Corruption in the ASM metadata blocks, which
SELECT * FROM V$ASM_DISKGROUP; SELECT * FROM V$ASM_DISK;
If your fix involved bringing a disk back online or adding a new disk, ensure the ASM rebalance process completes successfully without errors:%%MAGIT_PARSER_PROTECT%% sql SELECT operation, state, power, est_minutes FROM v$asm_operation; %%MAGIT_PARSER_PROTECT%% Summary Checklist Command/Tool 1 Identify the specific failure detail tfactl orachk -status 2 Check structural errors adrci (Look for ORA- errors) 3 Check disk status Query v$asm_disk & v$asm_diskgroup 4 Repair & Rebalance
Verify if CPU or Memory spikes are causing the health monitor to time out. 📋 Common Root Causes The host machine running the ASM instance may
: A physical disk or a storage path (LUN) has become inaccessible. Forced Dismounts
# Check the status and location of recent AHF/Orachk reports tfactl orachk -status Use code with caution. Step 2: Query the ASM Alert Log
| | Component | Failure Description | Severity | First Detected | |--------------|---------------|------------------------|--------------|--------------------| | ASM-042 | Disk Group Mount Consistency | Disk group DATA – one offline disk not yet force-mounted after node reboot | Warning | [Date/Time of scan] |
Receiving an "ASM Health Checker found 1 new failures" alert can be stressful, but it's a sign that your system's built-in diagnostics are working as intended. By following the structured approach in this guide—first identifying your environment (Oracle vs. cPanel), then diving into the logs, performing a detailed diagnosis, and finally applying the precise fix—you can resolve the issue efficiently and prevent future occurrences.
A repair operation can sometimes trigger an automatic rebalance of the disk group to restore its optimal state. Monitor the progress using the V$ASM_OPERATION view.