|
||||||
|
|
||||||
|
If the diskgroup is still mounted, run a metadata check to find internal inconsistencies: ALTER DISKGROUP CHECK; Use code with caution. Copied to clipboard
While the "1 new failure" could technically be anything, it usually falls into one of these three categories: A. Disk Corruption or Metadata Inconsistency asm health checker found 1 new failures
Use the following SQL command in the ASM instance to identify disks with red flags (e.g., OFFLINE , CLOSED , or MISSING ): If the diskgroup is still mounted, run a
sqlplus / as sysasm EXEC DBMS_SCHEDULER.RUN_JOB('SYS.ASM_HEALTH_CHECK_JOB'); -- Or manually: SELECT * FROM table(asm_health_check()); If the diskgroup is still mounted
If the diskgroup is still mounted, run a metadata check to find internal inconsistencies: ALTER DISKGROUP CHECK; Use code with caution. Copied to clipboard
While the "1 new failure" could technically be anything, it usually falls into one of these three categories: A. Disk Corruption or Metadata Inconsistency
Use the following SQL command in the ASM instance to identify disks with red flags (e.g., OFFLINE , CLOSED , or MISSING ):
sqlplus / as sysasm EXEC DBMS_SCHEDULER.RUN_JOB('SYS.ASM_HEALTH_CHECK_JOB'); -- Or manually: SELECT * FROM table(asm_health_check());