One user reported a scenario where a disk originally from one ASM disk group was accidentally added to a new disk group, leading to corruption and the "ASM Health Checker found 1 new failures" message appearing in the logs.
ALTER DISKGROUP data ONLINE DISK data_0003;
A DBA was analyzing the ASM alert log and saw: "ASM Health Checker found 1 new failures" . The DBA then ran ALTER DISKGROUP DATA CHECK; and discovered that there was indeed an inconsistency in the disk group metadata—an orphaned extent map entry. After confirming that the database was still operational, the DBA ran ALTER DISKGROUP DATA CHECK ALL REPAIR; . The command completed successfully, the health checker alert cleared, and a subsequent health check reported zero failures.
To proactively detect such issues, Oracle includes a diagnostic framework known as . For ASM, this manifests as the ASM Health Checker —a set of low‑level diagnostic routines that run automatically in the background. These health checks validate various layers of the ASM instance, including:
If you can provide the from your alert log, I can help you identify the exact cause. Alternatively, tell me if this is a single-node or RAC setup, and I can give you more specialized commands to fix the issue. asm health checker found 1 new failures updated
RMAN> RESTORE DATAFILE '<file name>'; RMAN> RECOVER DATAFILE '<file name>';
A physical disk has failed, and its status is OFFLINE or MISSING .
SELECT group_number, name, path, state, failgroup, mode_status FROM v$asm_disk WHERE state != 'NORMAL';
For a targeted analysis, run the following command to check a specific disk group (replace <disk group name> with the actual disk group name): One user reported a scenario where a disk
This view will show you the FILE_NUMBER , DISK_NUMBER , and ERROR_CODE related to the identified failure. 3. Resolution Strategies
If you are dealing with a critical corruption, it is highly recommended to contact Oracle Support to assist with the investigation.
Often, the health checker finds a "failure" simply because a storage array is too slow. Monitor your OS-level tools like iostat or sar .
The phrase is precise. It communicates three key pieces of information: After confirming that the database was still operational,
Likely root causes (examples)
Connect to your ASM instance using sqlplus / as sysasm and run the following diagnostic queries:
And review the ASM alert log for any earlier signs of deterioration.
