Asm Health Checker Found 1 New Failures Jun 2026

The execution role used by the health checker lost its secretsmanager:GetSecretValue or secretsmanager:DescribeSecret permissions.

Fix: Clear out old UCS files or decrease the log storage period in your logging profile. Use df -h in the CLI to verify space. 3. ASM Policy Synchronization

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. asm health checker found 1 new failures

The "1 new failure" wasn't a death sentence, but it required surgery. Leo had to:

The ASM Health Checker typically reports errors falling into one of three operational categories. 1. Missing or Dropped Disks (Redundancy Issues) The execution role used by the health checker

: ASM takes disks offline if it cannot complete a write operation, which can lead to a disk group failure if redundancy is lost. Insufficient Redundancy

The "failure" wasn't a system collapse—it was the system getting confused by its own shadow. If you share with third parties, their policies apply

def detect_new_failures(previous_results, current_results): previous_fail_set = item.id for item in previous_results if item.status == "fail" current_fail_set = item.id for item in current_results if item.status == "fail" new_failures = current_fail_set - previous_fail_set