In a High Availability (HA) cluster, the health checker often fails if the security policies are out of sync between the active and standby units. Symptoms: "Sync failure" or "Generation ID mismatch."
If you are managing an Oracle Database environment using Automatic Storage Management (ASM), encountering the alert can be a jarring experience. This message is usually triggered by the Oracle Health Monitor (HM), a framework designed to detect and analyze components within the database and ASM instances.
Grep the ASM logs for the timestamp of the failure.
[ALERT] ASM Health Checker Detected 1 New Failure - Immediate Investigation Required
Run lsdg to confirm that all disk groups are properly mounted, displaying the correct usable capacity and balanced allocation units. asm health checker found 1 new failures
ALTER DISKGROUP <disk_group_name> CHECK;
The execution role used by the health checker lost its secretsmanager:GetSecretValue or secretsmanager:DescribeSecret permissions.
Sometimes the failure is not about the disks themselves, but about the ASM instance’s ability to manage them—such as running out of processes or memory in the SGA. 4. How to Resolve the Failure
The ASM Health Checker runs automatically and reports any issues or failures it detects. The checker runs at regular intervals, which can be configured using the ASM_CHECK_INTERVAL parameter. In a High Availability (HA) cluster, the health
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.
Any SAN, multipath, or OS upgrade should trigger a manual health check:
ALTER DISKGROUP DATA SET ATTRIBUTE 'scrub.mode'='AUTO'; ALTER DISKGROUP DATA SET ATTRIBUTE 'scrub.interval'='7d';
If dd fails with "Input/output error", the disk is physically failing. Grep the ASM logs for the timestamp of the failure
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.
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
SET LONG 100000 SET LONGCHUNKSIZE 1000 SELECT DBMS_HM.GET_RUN_REPORT('HM_RUN_1061') FROM DUAL;