Asm Health Checker Found 1 New Failures 【PREMIUM — ROUNDUP】

Often, the health checker will detect corruption that can be automatically fixed. The ALTER DISKGROUP command is the primary tool for this task.

often generates an incident report when this occurs. Use the tool to view the incident details: show incident show tracefile (for the specific process like +ASM_rbal_xxxx.trc Monitor Rebalance/Repair : If a disk is just offline and you have redundancy, check the REPAIR_TIME

Troubleshooting Guide: ASM Health Checker Found 1 New Failure

Oracle Automatic Storage Management (ASM) is the backbone of database storage performance and availability. When the Oracle Grid Infrastructure Health Checker (or Autonomous Health Framework) alerts you that the it means a critical metric has drifted outside of safe operating parameters. asm health checker found 1 new failures

He remoted into the terminal. The ASM dashboard, usually a sea of serene green, had a solitary, angry red dot pulsing on the Database Latency "Strange," Leo muttered. "The DB cluster is healthy."

: A physical disk or a storage path (LUN) has become inaccessible. Forced Dismounts

💡 Pro-tip: If the health checker shows "1 failure" but everything seems fine, it might be a "stale" alert. Clear it by clicking "Reset" in the GUI Health Report or restarting the statsd daemon. If you'd like to dive deeper, let me know: Your (e.g., v15.1 or v16.1) If you see any MySQL errors in the logs If this happened during a config sync or a software upgrade Often, the health checker will detect corruption that

Look for MOUNTED state but with disks OFFLINE or UNUSABLE .

Navigate to the log group associated with your health checker (e.g., /aws/lambda/SecretsManagerHealthChecker ).

Log into your ASM instance via SQL*Plus as SYSASM to assess the cluster-wide operational health of your storage: Use the tool to view the incident details:

If the failure is related to "Insufficient Space," rebalance the disk group or add new disks immediately.

The output will contain specific "Findings" that list the failure type, its priority (e.g., CRITICAL or HIGH ), and the exact object it affects. A sample finding might look like this:

Based on standard ASM operational patterns, the failure is likely attributed to one of the following scenarios: