Have you encountered an unusual "1 new failure" not covered here? Share your specific error message—solutions vary by Oracle version (11.2 to 23ai) and storage vendor.
Disk group redundancy failures (e.g., if a disk fails in a normal redundancy group, it checks if the partner mirror is healthy).
The alert itself is a summary. To fix the issue, you must find the specific failure code. Log into the BIG-IP Configuration Utility (GUI). Navigate to Security > Overview > Health Reports. asm health checker found 1 new failures
Once you’ve identified the Failure ID in ADRCI , you can ask Oracle for a repair advice: advise failure ; Use code with caution.
When a physical disk or storage network pipeline exhibits anomalies, the health checker records a localized failure. It handles these using several specific operations: Have you encountered an unusual "1 new failure"
If only one new failure exists, this yields exactly one row with actionable details.
| Area | Requirement | |-------|--------------| | Performance | Comparison must complete in < 100ms | | State persistence | Store previous health state (e.g., Redis, SQLite, S3) | | Idempotency | Rerunning same check should not trigger duplicate alerts | | Configurability | Ability to ignore certain failure types from “new failure” detection | The alert itself is a summary
Before jumping into fixes, you must identify what failed. The alert in the alert log usually provides a link or reference to a more detailed trace file. A. Check the Alert Log
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."
Monitor Memory: Keep an eye on the "Management" memory allocation. ASM is memory-intensive.