Asm Health Checker Found 1 New Failures -

Heavy traffic causing the ASM engine to respond slowly to the health probe.

Look for specific Oracle error codes (such as ORA-15032 , ORA-15075 , or ORA-27063 ) generated at the exact timestamp of the Health Checker alert. Step 3: Check Grid Plug and Play (GPNPD) and CSS Logs

When this failure hits your system, prioritize stabilization and diagnostic isolation to avoid database downtime.

The or log snippet surrounding the failure. Your Oracle Grid Infrastructure version (e.g., 19c, 21c).

When this alert is triggered, it indicates that a recent scan has detected a deviation in your ASM environment. Common causes for a single new failure include: Disk Path Issues asm health checker found 1 new failures

The GET_RUN_REPORT output will contain sections like 'Run Findings And Recommendations', which will show the specific failure (e.g., a specific datafile or disk), its priority, and a descriptive message.

If your monitoring dashboard flags this error, follow these structured steps to isolate and fix the root problem:

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."

Ensure the asm , mysql , and tomcat processes are running correctly using the command bigstart status . Heavy traffic causing the ASM engine to respond

It turned out a routine disk add operation from earlier that morning had gone sideways. A subtle corruption on had been lying in wait. When the ASM rebalance operation hit that specific block, the Health Checker—a silent guardian that usually stays in the background—spotted the anomaly and pulled the emergency brake to prevent further data loss.

Once you have applied the fix, you need to verify that the ASM cluster is fully healthy and clear the alert.

: Corruption in the ASM metadata blocks, which can happen during intensive operations like rebalancing. Configuration Issues

To resolve the issue, follow these step-by-step instructions: The or log snippet surrounding the failure

Fix the underlying hardware, multipathing (MADP, PowerPath), or permission issues at the OS level. Once the OS sees the disk again, online it in ASM: ALTER DISKGROUP ONLINE DISK ; Use code with caution. Scenario B: Disk Space Exhaustion (Corrupted or Full)

If a storage block device's metadata tracks are overwritten or dropped, the disk header becomes unreadable. When the ASM instance periodically re-scans disk paths, it marks the incomplete or corrupted disk as an active failure. 4. Severe Redundancy Imbalances

: Physical corruption of the disk header can prevent ASM from identifying the disk as a "MEMBER" of a group. Investigative Steps