Asm Health Checker Found 1 New Failures [2026]

SELECT name, path, mount_status, header_status, state FROM v$asm_disk; Use code with caution. Copied to clipboard

This documentation aids future troubleshooting and contributes to your organization's collective operational intelligence.

Monitor Memory: Keep an eye on the "Management" memory allocation. ASM is memory-intensive.

Out-of-sync MySQL tables or disk space exhaustion. asm health checker found 1 new failures

If the CHECK command reports inconsistencies, you can often resolve it by adding the REPAIR clause.

Finding Name : Datafile is old Type : FAILURE Priority : HIGH Message : Datafile 2: 'H:\PATH\UNDO.DATA1' needs media recovery

Run the following command to see the specific failure identified: list failure Use code with caution. ASM is memory-intensive

WARNING: Offline of disk 3 (LOGA2) in group 2 failed on ASM inst 1. ERROR: ORA-15130: diskgroup "LOG" is being dismounted. ASM Health Checker found 1 new failures. Use code with caution. 2. Storage Heartbeat Failures and Timeouts

ALTER DISKGROUP <disk_group_name> CHECK;

💡 Pro-tip: If the health checker shows "1 failure" but everything seems fine, it might be a "stale" alert. Clear it by clicking "Reset" in the GUI Health Report or restarting the statsd daemon. If you'd like to dive deeper, let me know: Your (e.g., v15.1 or v16.1) If you see any MySQL errors in the logs If this happened during a config sync or a software upgrade Finding Name : Datafile is old Type :

Database Integrity: Issues with the MySQL backend where policies are stored.

Suggested action: Run asm health fix --check tls_expiry

When this alert surfaces in your alert log or monitoring dashboard (like Enterprise Manager), it means ASM has identified a specific issue that could potentially impact the availability or performance of your storage layer.

If your monitoring dashboard flags this error, follow these structured steps to isolate and fix the root problem:

Because the initial alert does not specify the exact nature of the failure, you must collect diagnostic details using Oracle’s command-line utilities. Check the Grid Infrastructure Alert Log