Asm Health Checker Found 1 New Failures !full! (Full • STRATEGY)

Verify if any groups show a state of DISMOUNTED . Next, query individual disk headers:

"Version": "2012-10-17", "Statement": [ "Sid": "AllowHealthCheckAccess", "Effect": "Allow", "Action": [ "secretsmanager:GetSecretValue", "secretsmanager:DescribeSecret" ], "Resource": "arn:aws:secretsmanager:region:account-id:secret:secret-name" ] Use code with caution.

Oracle ASM relies on internal health-checking daemons to continuously evaluate storage accessibility. These daemons screen disk groups, failgroups, and read/write response times. asm health checker found 1 new failures

Look for disks with a state of FAILED , FORCING , or HUNG . An unhealthy disk is a common cause of the alert.

In cases of severe block corruption where the database cannot be recovered via standard means, you may need to recreate the diskgroup and restore from backup. Verify if any groups show a state of DISMOUNTED

If compatible.asm , compatible.rdbms , or compatible.advm values are set incorrectly relative to the GI version, the health checker will report advisories as failures.

The error message indicates that the Oracle Automatic Storage Management (ASM) instance has detected a critical hardware or software problem, most commonly resulting in an unplanned disk eviction or forced diskgroup dismount . When this alert triggers in your ASM alert log, it usually means ASM can no longer read from or write to one or more physical storage devices. Immediate action is required to prevent a full Cluster Ready Services (CRS) crash or database downtime. What Causes the ASM Health Checker Failure? These daemons screen disk groups, failgroups, and read/write

This command will provide more detailed information about the failure.