New Failures: Asm Health Checker Found 1

Fix: Force a manual sync from the device group settings or perform a "Sync-Only to Group" operation. Step 3: Restarting the ASM Engine

While the "1 new failure" could technically be anything, it usually falls into one of these three categories: A. Disk Corruption or Metadata Inconsistency

"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 asm health checker found 1 new failures

When any test returns a "FAIL" status, the health checker logs a failure count increment. The message asm health checker found 1 new failures means exactly that: since the last run, the checker identified one more problem than before.

This is the most common cause. Like a standard file system, ASM disk groups have metadata that can become inconsistent. This can happen due to incomplete rebalance operations, unexpected instance crashes, or software bugs. Fix: Force a manual sync from the device

If the disk remains offline, drop it and add a replacement:

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 This is the most common cause

Loss of connectivity due to faulty Fiber Channel cables, bad switches, or host bus adapter (HBA) path failures.

: The health checker may trigger a failure if it waits too long (e.g., >15 seconds) for I/O operations to complete on a specific disk. Oracle Forums Recommended Troubleshooting Steps

Note the exact timestamp to correlate the failure with AWS CloudTrail audit logs. 2. Verify IAM and Resource Policies