Asm Health Checker Found 1 New Failures -
If this guide helped you resolve the issue, please share your experience or let others know which specific fix worked for you in the comments below.
Detect and notify when the ASM (Application Security Management / Assembly / depending on context) health checker identifies that weren’t present in the previous check.
: The ASM instance freezes the global resource directory to isolate the broken component.
The "ASM Health Checker found 1 new failures" line is rarely generated in isolation. It is usually surrounded by a sequence of catastrophic errors inside the alert_+ASM.log file. A standard failure log footprint mirrors this pattern: asm health checker found 1 new failures
Verify that the security group attached to the VPC endpoint allows inbound HTTPS (port 443) traffic from the health checker's security group.
Physical drive dropouts, bad sectors, SAN controller faults, or Fibre Channel/iSCSI network interruptions.
Look for lines containing SQL> select * from v$asm_health_check or health_check_summary . You will see a failure line like: "Check: Disk Path Accessibility, Status: FAIL, Details: Disk DATA_0002 path /dev/mapper/asm_data2 is not readable" If this guide helped you resolve the issue,
[ASM Health Checker] 🚨 1 new failure detected
When a "new failure" is reported, Oracle has logged a diagnostic entry into its . The alert doesn't tell you the problem directly; it tells you that a report is waiting for your review. 2. Immediate Diagnostic Steps
If your health checker runs inside a private VPC subnet, it cannot access the public AWS Secrets Manager endpoint without proper routing. The "ASM Health Checker found 1 new failures"
) has been changed and no longer aligns with recommended settings. Offline Disks
When it reports a "new failure," it means a specific "check" (such as disk connectivity, metadata consistency, or space usage) has moved from a PASS to a FAIL state. 2. Immediate Step: Identify the Failure
Oracle Automatic Storage Management uses localized, automated checking subroutines to monitor disk integrity, read/write timeouts, and consistency across failure groups. The runs continuously or is automatically triggered during crucial storage events, such as: An intentional or accidental storage reconfiguration . The initiation of a diskgroup rebalance operation.
The of the affected disk group (External, Normal, High).
asmcmd checkset -g DATA