Asm Health Checker Found 1 New Failures

| | 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] |

ALTER DISKGROUP <disk_group_name> CHECK;

The error is rarely an isolated software bug. Instead, it is a symptom of underlying infrastructural or physical disruptions:

process has detected an issue—often a disk failure or a forced dismount—that requires immediate attention What This Alert Means

When the checker encounters an anomaly, it registers a "failure" within the Oracle Cluster Health Advisor (CHA) or the Grid Infrastructure alert logs. The generic notification "found 1 new failures" acts as an umbrella warning, requiring manual inspection to uncover the exact root cause. Step 1: Locating the Failure Details asm health checker found 1 new failures

"Sid": "AllowSecretDecryption", "Effect": "Allow", "Principal": "AWS": "arn:aws:iam::account-id:role/HealthCheckerRole" , "Action": "kms:Decrypt", "Resource": "*" Use code with caution. 4. Test Network and VPC Endpoints

As with many complex systems, proactive prevention is far better than reactive repair. Implementing the following best practices can significantly reduce the likelihood of encountering this alert:

Troubleshooting AWS ASM: How to Fix "ASM Health Checker Found 1 New Failures"

If your health checker is event-driven, attach a DLQ (Amazon SQS) to capture failed invocations for deep debugging without losing event data. | | Component | Failure Description | Severity

"check_id": "asm_crypto_usage", "previous_status": "pass", "current_status": "fail", "detected_at": "2026-04-12T10:15:00Z", "severity": "medium", "component": "ASM policy engine"

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

⚠️ Warning: This will briefly interrupt traffic if you are not in an HA configuration. To restart only the ASM services: bigstart restart asm Best Practices for Prevention

Check for any explicit failure messages. If a rotation fails, the secret might be left with a AWSPENDING label that doesn't match the actual password on the target database, causing dependency checks to fail. Preventive Strategies asm health checker found 1 new failures

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

) identifies a configuration issue or a hardware fault that doesn't match the established "best practices" or previous healthy state What This Usually Means

— End —

After applying the fix, re-run the health check to confirm the issue is resolved.