Asm Health Checker Found 1 New Failures Updated -
By following these best practices and resolving the issue reported by the ASM Health Checker, you can ensure the health and performance of your ASM infrastructure and prevent future failures.
At , the ASM (Application Service Manager / Audit Session Manager / Android Studio Metrics) Health Checker routine completed its scheduled run. The monitoring utility flagged 1 new failure within the environment.
Leo killed the ghost process, updated the health-check parameters to ignore the old server, and watched the red dot turn back to green. He leaned back as the silence of his apartment rushed in.
After the underlying issue is resolved (e.g., the disk is back online or the metadata is repaired), you need to "close" the failure in the ADR so the health checker stops reporting it. Inside ADRCI : asm health checker found 1 new failures
Check: Metadata Consistency, Status: FAIL, Detail: Orphaned file directory entry
2026-05-30T10:14:22.102555+01:00 WARNING: Write Failed. group:1 disk:2 AU:4 offset:4190208 size:4096 path:/dev/oracleasm/disks/DATA02 asynchronous result:'I/O error' 2026-05-30T10:14:22.155824+01:00 ORA-15130: diskgroup "DATA" is being dismounted 2026-05-30T10:14:22.193916+01:00 ASM Health Checker found 1 new failures 2026-05-30T10:14:22.201907+01:00 List of instances (total 1) : 1 My inst 1 2026-05-30T10:14:22.210482+01:00 NOTE: initiating dirty detach from lock domain 1 Use code with caution. The Sequence of Events
If the report indicates a datafile "needs media recovery," the underlying physical file may be missing or corrupted. Your course of action will depend on your backup and redundancy strategy. You may need to: By following these best practices and resolving the
Run an internal check and repair command within SQL*Plus as SYSASM : ALTER DISKGROUP CHECK ALL; Use code with caution.
In cases of severe block corruption where the database cannot be recovered via standard means, you may need to recreate the diskgroup and restore from backup.
[ASM Health Checker] 🚨 1 new failure detected Leo killed the ghost process, updated the health-check
if len(new_failures) > 0: send_alert( title="ASM Health Checker found 1 new failure", details=list(new_failures), count=len(new_failures) ) else: log.info("No new ASM failures detected")
This command provides a unique and a description of the problem.
Monitor Memory: Keep an eye on the "Management" memory allocation. ASM is memory-intensive.
The or log snippet surrounding the failure. Your Oracle Grid Infrastructure version (e.g., 19c, 21c).