This specific warning indicates that the internal Oracle background monitoring engine has detected an issue affecting the state, configuration, or performance of an ASM disk group or its underlying physical storage components. What is the ASM Health Checker?
-- 1. Identify the recent health checks SET LINESIZE 200 PAGESIZE 100 COLUMN name FORMAT a20 COLUMN check_name FORMAT a30 COLUMN start_time FORMAT a30 COLUMN end_time FORMAT a30 SELECT run_id, name, check_name, TO_CHAR(start_time, 'YYYY-MM-DD HH24:MI:SS') AS start_time, TO_CHAR(end_time, 'YYYY-MM-DD HH24:MI:SS') AS end_time, status FROM v$hm_run WHERE check_name LIKE '%ASM%' OR name LIKE 'HM_RUN_%' ORDER BY start_time DESC;
At first glance, a single failure might seem trivial. After all, modern ASM configurations are built on pillars of redundancy: normal redundancy, high redundancy, and robust failure groups. A single disk slowing down or a single network path intermittently dropping packets could be masked by the system’s inherent self-healing capabilities. However, the health checker is not an alarmist. It is a sentinel. The designation of “1 new failure” implies a delta from a previous state of health. Something, somewhere, has crossed a threshold from acceptable to aberrant. That one failure is the canary in the coalmine.
Locate the exact timestamp of the error in the ASM alert log. Look for preceding errors like ORA-15130 (diskgroup being dismounted) or specific path-related I/O errors. asm health checker found 1 new failures
Process Crashes: Vital daemons like 'bd' or 'asm_config_server' failing to respond.
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 output will contain specific "Findings" that list the failure type, its priority (e.g., CRITICAL or HIGH ), and the exact object it affects. A sample finding might look like this: This specific warning indicates that the internal Oracle
Symptoms: Errors mentioning "mysql" or "table marked as crashed."
Firmware Updates: Many health check bugs are resolved in newer Engineering Hotfixes (EHF).
The hum of the server room was usually a comforting white noise for Leo, the lead DevOps engineer. But at 3:00 AM, that hum sounded more like a low-pitched warning. Identify the recent health checks SET LINESIZE 200
: Run the following query in your ASM instance to check for offline or missing disks: name, group_number, path, state, header_status v$asm_disk; Use code with caution. Copied to clipboard Investigate the Incident : Oracle’s Fault Diagnosability Infrastructure
Would you like me to extend this into: