SELECT group_number, name, state, type, total_mb, free_mb FROM v$asm_diskgroup; Use code with caution.
What the message means
: Changes to initialization parameters or clusterware settings that don't align with Oracle's Recommended Best Practices Troubleshooting Steps
The instance logs an explicit ORA-15130 (Diskgroup being dismounted) error, followed immediately by the ASM Health Checker found 1 new failures summary event. 4. Dirty Detach Execution asm health checker found 1 new failures updated
The Oracle ASM Health Checker is an automated diagnostic tool that continuously verifies the integrity of your ASM disk groups and the data within them. Think of it as a security guard for your database storage. Without being asked, it regularly checks for issues like data block corruption, disk metadata inconsistencies, and physical disk errors.
Mirrored disks going offline due to controller issues, which can force a disk group to dismount to prevent data loss. Unbalanced I/O:
[Insert Date] Host/Cluster: [Insert Environment Name] Severity: Warning / Critical (as applicable) Dirty Detach Execution The Oracle ASM Health Checker
When an underlying hardware or connectivity issue disrupts the storage fabric, the ASM Health Checker works in tandem with the Rebalance ( RBAL ) and Group Monitor ( GMON ) background processes. The process typically unfolds across four technical milestones: 1. Persistent Storage Timeout
The alert message is just the "headline." You need to find the specific error code (like ORA-15032 or ORA-15078).
SQL> ALTER DISKGROUP <disk_group_name> DROP DISK 'disk_name'; SQL> ALTER DISKGROUP <disk_group_name> ADD DISK '/dev/oracleasm/disks/disk_path'; Mirrored disks going offline due to controller issues,
Look for errors like ORA-15080 (synchronous I/O fail), ORA-15195 (disk group corruption), or messages referencing ASM health check failure . 1.2 Identify the Failing Component
: ASM may force a dismount if too many disks in a failure group are lost, exceeding the redundancy limit.
The ASM Health Checker constantly monitors background storage components. When it logs an error update, it is usually triggered by one of the following scenarios:
A rebalance operation failed or was interrupted, leaving the disk group in a "degraded" state.