If you manage Oracle Grid Infrastructure (GI) or a standalone Automatic Storage Management (ASM) instance, one notification can send a chill down your spine:
-- Mount the disk group with repair option (requires downtime) ALTER DISKGROUP DATA MOUNT RESTRICT; -- Run ASM Check (from OS) $GRID_HOME/bin/asmcmd md_check DATA -- If errors found: ALTER DISKGROUP DATA CHECK REPAIR; ALTER DISKGROUP DATA DISMOUNT; ALTER DISKGROUP DATA MOUNT; asm health checker found 1 new failures
SELECT * FROM V$ASM_INSTANCE;
SELECT name, path, mount_status, header_status, state FROM v$asm_disk; Use code with caution. Copied to clipboard If you manage Oracle Grid Infrastructure (GI) or
By following these best practices and resolving the issue reported by the ASM Health Checker, you can ensure the health and performance of your ASM infrastructure and prevent future failures. If left unaddressed, this could cascade into: Check
Currently, the failure is isolated to a single check. If left unaddressed, this could cascade into:
Check which home is reporting the error (usually the ASM home):