Check the KMS Key Policy. The health checker's IAM role must have permission to use the key for decryption:
ASM disks must be owned by grid:asmadmin (or oracle:asmadmin in older setups) with 660 permissions. If udev rules or ASMLIB configuration changes, the checker flags a failure.
The hum of the server room was usually a comforting white noise for Leo, the lead DevOps engineer. But at 3:00 AM, that hum sounded more like a low-pitched warning.
-- 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
Schedule routine CHECK ALL executions during off-peak maintenance windows to uncover hidden media corruptions early.
Configure proactive alert thresholds within Oracle Enterprise Manager (OEM) to notify administrators when disk write endurance or space utilization reaches 85%.
If Oracle provides a repair script, you can run: repair failure; Use code with caution. Check the KMS Key Policy
The failure can be related to various aspects of ASM, such as:
The Health Checker warning is an aggregate flag. To find the specific culprit, inspect the ASM alert log located under your Oracle Diagnostic Destination:
The most frequent culprit. One disk in a disk group has been taken offline due to: The hum of the server room was usually
SELECT * FROM V$ASM_OPERATION;
This utility bundles the relevant ASM traces and structural reports to pinpoint exactly which disk or file allocation unit tripped the health checker. Step 2: Common Root Causes and Solutions
ALTER DISKGROUP DATA SET ATTRIBUTE 'compatible.asm' = '12.2';