Asm Health Checker Found 1 New Failures __top__ 95%
When this message occurs, it indicates that a health check—either triggered automatically by an incident or run manually—has identified a problem that could compromise your storage. Common triggers include:
Compare the parameters across all cluster nodes using SQL*Plus.
Verify that the security group attached to the VPC endpoint allows inbound HTTPS (port 443) traffic from the health checker's security group.
Though less common due to ASM mirroring, if you are running an EXTERNAL REDUNDANCY disk group (relying entirely on hardware RAID) and a bad sector corrupts an essential metadata block, the health routine will flag it instantly. Step-by-Step Diagnostic and Resolution Workflow
:Use the ADR Command Interpreter (ADRCI) to list the details of the specific failure. adrci> list failure Use code with caution. Copied to clipboard asm health checker found 1 new failures
The asm health checker found 1 new failures alert is Oracle’s way of saying: "Something in your storage stack is not perfect." In most cases, it's a disk path issue or an offline disk that can be fixed with a few commands. However, ignoring even one failure invites gradual degradation.
In RAC, if the Cluster Synchronization Service (CSS) heartbeat is delayed, the ASM health checker may interpret this as an ASM instance failure.
Leverage the Automatic Diagnostic Repository Command-Line (ADRCI) utility to view detailed incident reports associated with the health check failure. Recommended Remediation
In a Real Application Clusters (RAC) environment, a rolling upgrade or manual DBA change left an initialization parameter (like ASM_DISKSTRING or ASM_POWER_LIMIT ) inconsistent across nodes. How to Fix: When this message occurs, it indicates that a
: SELECT operation, state, est_minutes FROM v$asm_operation; Common Remediation Steps KB88485 - My Oracle Support
When any test returns a "FAIL" status, the health checker logs a failure count increment. The message asm health checker found 1 new failures means exactly that: since the last run, the checker identified one more problem than before.
When you encounter the "ASM Health Checker found 1 new failures" message, follow this structured approach to identify and resolve the underlying issue. The process involves confirming the failure, pinpointing its source, performing an initial repair, and verifying the result.
ALTER DISKGROUP <disk_group_name> CHECK; Though less common due to ASM mirroring, if
To resolve the issue, follow these step-by-step instructions:
Ensure your health checker script doesn't alert on transient network blips. Implement a retry mechanism using standard AWS SDK configurations.
Recently, you may have encountered an alert or message indicating that the "ASM health checker found 1 new failure." This message can be concerning, especially if you're not familiar with what it means or how to resolve it. In this article, we'll explore what this message means, the possible causes, and step-by-step instructions on how to resolve the issue.
The ASM Health Checker runs automatically and reports any issues or failures it detects. The checker runs at regular intervals, which can be configured using the ASM_CHECK_INTERVAL parameter.