Asm Health Checker Found 1 New Failures Updated -

Schedule weekly manual checks using:

ALTER DISKGROUP data CHECK ALL;

And review the ASM alert log for any earlier signs of deterioration.

If the disk is still NORMAL but shows path errors:

If a disk was accidentally taken offline or lost connectivity but is now accessible: asm health checker found 1 new failures updated

ALTER DISKGROUP data ONLINE DISK data_0003;

Wait for the recovery to complete (monitor via v$asm_operation). Once done, the health checker will automatically clear the failure and log a corresponding "failure cleared" message.

When you see "ASM Health Checker found 1 new failures updated" in the ASM alert log, follow this systematic diagnostic procedure.

Connect to your ASM instance using sqlplus / as sysasm and run the following diagnostic queries: Schedule weekly manual checks using: ALTER DISKGROUP data

A. Check disk group overall health:

SELECT name, state, type, total_mb, free_mb, offline_disks 
FROM v$asm_diskgroup;

If offline_disks > 0, you have confirmed physical disk failures.

B. Identify failing disks:

SELECT group_number, disk_number, name, path, state, mode_status, failgroup 
FROM v$asm_disk 
WHERE state != 'NORMAL';

Disks in FORCING state (attempting recovery) or OFFLINE state are the culprits.

C. Check for I/O errors (recent history):

SELECT * FROM v$asm_disk_iostat 
WHERE read_errs > 0 OR write_errs > 0 OR bytes_read = 0;

D. Examine ASM operations:

SELECT * FROM v$asm_operation;

Look for active rebalancing or recovery operations that may have been triggered by the failure.

ls -la /dev/oracleasm/disks/
# or
ls -la /dev/mapper/