If the health checker finds a mismatch in the v$asm_check_failure metadata, the might be necessary, or in severe cases, using ASMCMD to mend the metadata. Try to rebalance: ALTER DISKGROUP REBALANCE POWER ; Use code with caution.
There are several possible causes for ASM health checker failures, including:
Follow this structured workflow to safely clear the failure and restore redundancy. Fix Disk Redundancy Issues asm health checker found 1 new failures updated
In this example, --repair tells ASMCMD to automatically fix any errors it encounters in the data disk group. The chkdg command is particularly useful when you need a quick, command-line-driven verification of a disk group's health.
More importantly, this message serves as a crucial reminder that proactive maintenance is the cornerstone of a resilient database environment. Regular monitoring, automated health checks, and well-tested backups will ensure that when the health checker does find a failure, it's merely a minor bump in the road rather than a catastrophic event. If the health checker finds a mismatch in
And review the ASM alert log for any earlier signs of deterioration.
Verify physical hardware or multipathing configurations to ensure the device path (e.g., /dev/sdg1 ) is still visible to the OS. Fix Disk Redundancy Issues In this example, --repair
If the corruption affects specific database files—such as data files or control files—you may need to restore them from a backup. Use RMAN to restore the affected files:
SELECT * FROM v$asm_disk_iostat WHERE read_errs > 0 OR write_errs > 0 OR bytes_read = 0;
This alert is frequently triggered when a disk fails, a path is lost, or a corruption occurs that the ASM metadata cannot immediately repair. Common Causes for ASM Health Checker Failures
A prior error (like an IO error) forced a dismount, triggering this health check finding [Per 2.2.4]. Step-by-Step Resolution Guide 1. Identify the Affected Diskgroup