When this failure hits your system, prioritize stabilization and diagnostic isolation to avoid database downtime.
Log into the ASM instance using SQL*Plus as SYSASM to evaluate the structural integrity of your diskgroups:
The AHF framework flags the issue, but the ultimate truth lies within the ASM instance alert log. Navigate to your Diagnostic Destination to read the log: asm health checker found 1 new failures
Failures can occur if a monitored service is down or flapping.
This is the most frequent partner error. If the storage layer loses connectivity to a device for even a few seconds, Oracle ASM may drop the disk or force a complete dismount of the disk group to protect against data corruption. In your log, it will typically look like this: When this failure hits your system, prioritize stabilization
: If your diskgroup uses external redundancy and a disk fails, the group will likely dismount immediately, potentially crashing your database. Intermediate States
To fix the error, you must first uncover exactly what the Health Checker discovered. Follow this step-by-step triage workflow. Step 1: Locate the Diagnostic Report This is the most frequent partner error
If your secret uses a resource-based policy, ensure it does not contain a explicit Deny block that inadvertently catches the health checker's IAM role. 3. Audit AWS KMS Key Permissions
Check your OS system logs ( /var/log/messages or dmesg ) for SCSI timeout errors or multipath path failures. Adjust your disk timeout configurations if your SAN fabric is experiencing transient load spikes. 4. Post-Resolution Verification
"Sid": "AllowSecretDecryption", "Effect": "Allow", "Principal": "AWS": "arn:aws:iam::account-id:role/HealthCheckerRole" , "Action": "kms:Decrypt", "Resource": "*" Use code with caution. 4. Test Network and VPC Endpoints
Note the , Disk Name , and the specific OS Error Codes ( osderr ) provided in the trace. 2. Verify Diskgroup and Disk Statuses