Asm Health Checker Found 1 New Failures Updated

Subject: ASM Health Check Report – New Failures Detected

Date: [Insert Date] Host/Cluster: [Insert Environment Name] Severity: Warning / Critical (as applicable)

Step 2: Query ASM Using SQL Commands

Connect to your ASM instance using sqlplus / as sysasm and run the following diagnostic queries:

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. asm health checker found 1 new failures updated

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. Subject: ASM Health Check Report – New Failures

2. Identify the failing disk(s)

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

The Headline

System administrators are urged to investigate immediate storage integrity issues following an automated alert indicating that the ASM Health Checker has detected a new failure within the storage subsystem.

Typical Scenarios & Actions

| Scenario | Recommended Action | |----------|--------------------| | Planned disk maintenance | Ignore if expected; check after maintenance. | | Single disk failure | Replace or re-add disk: alter diskgroup DATA online disk 'DATA_0001'; | | Multiple disks in same failure group | Investigate storage/LUN path issues urgently. | | After power/storage event | Run asmcmd health check again; verify redundancy. |

close