Rare, but serious. Corruption in the file directory ( KFD ) or allocation tables can cause "stale metadata" errors. Often seen after abnormal cluster shutdowns.
This will provide a , the severity (CRITICAL or HIGH), and a brief description of what went wrong. 3. Common Causes for ASM Failures
A repair operation can sometimes trigger an automatic rebalance of the disk group to restore its optimal state. Monitor the progress using the V$ASM_OPERATION view. asm health checker found 1 new failures
Run the health checker in verbose mode to identify exactly which assertion failed.
Oracle's Health Monitor records every automatic and manual health check. Use the V$HM_RUN view to confirm the execution of the health checker that triggered the alert and to get its specific run ID. Rare, but serious
: Physical corruption of the disk header can prevent ASM from identifying the disk as a "MEMBER" of a group. Investigative Steps
The message itself is generic, but the underlying causes generally fall into several categories: This will provide a , the severity (CRITICAL
If the failure is related to "Insufficient Space," rebalance the disk group or add new disks immediately.