Asm Health Checker Found 1 New Failures -

Ensure you have an interface VPC endpoint ( com.amazonaws.region.secretsmanager ) configured for your VPC.

If the health checker found a disk failure, check the OS-level connectivity. lsdsk (within ASMCMD) or fdisk -l (Linux).

Because the initial alert does not specify the exact nature of the failure, you must collect diagnostic details using Oracle’s command-line utilities. Check the Grid Infrastructure Alert Log

To minimize the likelihood of ASM health checker failures:

: If the ASM disk group hosts the Cluster Registry (OCR) or Voting Disks, a failure can cause node evictions or cluster instability. Storage Latency/I/O Timeouts asm health checker found 1 new failures

Check operating system performance metrics using iostat or OSWatcher . If a specific physical disk exhibits high service times relative to peers, coordinate with your storage vendor to replace the underlying hardware. Step 3: Verifying the Fix and Clearing the Alert

The message itself is generic, but the underlying causes generally fall into several categories:

: One of the disks in a "Normal Redundancy" disk group has failed, putting the group in a "degraded" state. Parameter Mismatches : An ASM instance parameter (like ASM_POWER_LIMIT

For a failing disk group, run a manual consistency check to identify specific metadata corruption. Ensure you have an interface VPC endpoint ( com

ALTER DISKGROUP <disk_group_name> CHECK;

When the health checker reports a new failure, the underlying issue almost always falls into one of four categories:

This will generate a report explaining the impact and recommending a script or manual action to fix it.

Configure proactive alert thresholds within Oracle Enterprise Manager (OEM) to notify administrators when disk write endurance or space utilization reaches 85%. Because the initial alert does not specify the

The failure relates to performance bottlenecks, slow I/O response times, or asymmetrical disk sizes within a disk group.

Suggested action: Run asm health fix --check tls_expiry

The correct resolution depends on the findings from the previous steps.

The alert itself is generic. To find out what actually failed, you need to query the ASM instance.

If a path to a physical disk is lost (due to HBA failure or cable issues), ASM might mark the disk as "OFFLINE." If the diskgroup is still mounted but missing a member, the Health Checker will flag it.