Run the following command to see the specific failure identified: list failure Use code with caution.
When it reports a "new failure," it means a specific "check" (such as disk connectivity, metadata consistency, or space usage) has moved from a PASS to a FAIL state. 2. Immediate Step: Identify the Failure
This guide explains what this error means, how to diagnose it, and the steps to resolve the issue to ensure your Oracle database remains highly available and data-safe. What is the ASM Health Checker? asm health checker found 1 new failures
to ensure you haven't hit a "disk full" state.
Rare, but serious. Corruption in the file directory ( KFD ) or allocation tables can cause "stale metadata" errors. Often seen after abnormal cluster shutdowns. Run the following command to see the specific
This error indicates that an automated health check—typically executed via an AWS Lambda function, an Amazon Route 53 health check, or a synthetic monitoring tool—attempted to validate the accessibility, rotation status, or integrity of a secret and failed. Direct Root Causes
Once you have fixed the underlying physical or logical issue, the Health Checker should automatically update during its next run. However, if the status remains "Failed" in the views, you can manually trigger a re-run of the health check or use ADRCI to purge the alert. Summary Checklist Immediate Step: Identify the Failure This guide explains
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."