To resolve the issue, follow these steps:
Oracle's ASM command-line utility ( asmcmd ) offers a powerful alternative for troubleshooting and repairing disk groups. The chkdg command can be used to check and optionally repair disk group metadata without using SQL:
For a targeted analysis, run the following command to check a specific disk group (replace <disk group name> with the actual disk group name): asm health checker found 1 new failures updated
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 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: To resolve the issue, follow these steps: Oracle's
: Schedule weekly orachk cron jobs to catch silent degradation before it triggers critical system alerts.
SQL> SELECT name, path, state, mode_status, header_status, total_mb, free_mb FROM v$asm_disk; If the corruption affects specific database files—such as
The health checker might run many times successfully, but a previously latent corruption (for example, a block that was never read) becomes discovered. In this case, the message “found 1 new failures” may be the first indication of a problem that has existed for weeks.
Most instances of this specific health check failure trace back to three main infrastructure issues.
Corruption within the ASM diskgroup metadata, often resolved by ALTER DISKGROUP ... CHECK commands.