To understand the gravity of this alert, one must dissect what ASM protects. ASM is not merely a volume manager; it is the nervous system of an Oracle database environment, striping and mirroring data across physical disks. A failure here is not isolated. The one failure could be a physical disk beginning to show sector reallocation counts, an offline ASM disk that has exhausted its repair timer, or a consistency issue in the disk group’s metadata. In a normal redundancy configuration with two failure groups, the loss of one disk is survivable. But if that “one new failure” is the prelude to a second—say, a controller failure on the partner disk—the entire disk group could dismount, bringing critical databases to an abrupt halt. Thus, the health checker’s finding is a warning that the margin of safety has just narrowed.
The alert " ASM Health Checker found 1 new failures " is a critical notification typically found in Oracle Automatic Storage Management (ASM) alert logs. It indicates that the GMON (Group Monitor) asm health checker found 1 new failures
The new ASM health check failure is isolated and classified as . Immediate intervention is not critical, but prompt remediation will restore full redundancy and prevent potential escalation. To understand the gravity of this alert, one
Note: Always back up your metadata and ensure you have a valid backup before running automated repair scripts on production storage. 5. Clearing the Alert The one failure could be a physical disk
Regularly back up ASM metadata to recover from logical corruption without losing disk groups:
Identify if the secret uses the default AWS managed key ( aws/secretsmanager ) or a Customer Managed Key (CMK).
Potential traffic disruption or security bypass 🛠️ Recommended Action Steps