When a physical disk or storage network pipeline exhibits anomalies, the health checker records a localized failure. It handles these using several specific operations:
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.
To minimize the risk of encountering this or similar alerts, implement these best practices:
Open an SR with Oracle and attach:
: If the ASM disk group hosts the Cluster Registry (OCR) or Voting Disks, a failure can cause node evictions or cluster instability. Storage Latency/I/O Timeouts
If your monitoring dashboard flags this error, follow these structured steps to isolate and fix the root problem:
Identify the name of the relevant health check (e.g., 'HM_RUN_361') and use it to generate the full diagnostic report. The report will pinpoint the exact nature of the failure. asm health checker found 1 new failures
If the ASM manages audit trails or session data, the database writer may have hit a connection limit. The health checker attempted to write a "heartbeat" record and timed out.
-- Check detailed status of all disks in all disk groups SELECT group_number, disk_number, name, path, state, mode_status, header_status, total_mb, free_mb FROM v$asm_disk;
: The metadata (headers) on one or more ASM disks may be corrupted or in a "FORMER" or "PROVISIONED" status instead of "MEMBER". Voting File Issues When a physical disk or storage network pipeline
Follow these diagnostics to isolate and address the exact storage failure: Step 1: Examine the ASM Alert Log
Connect to the ASM instance and run:
: Physical corruption of the disk header can prevent ASM from identifying the disk as a "MEMBER" of a group. Investigative Steps The health checker attempted to write a "heartbeat"
) will have created an HTML report. Locate this report to see the specific and description of the failure. Verify ASM Disk Status utility to check the status of your disks and disk groups: asmcmd lsdsk -t asmcmd lsdg Use code with caution. Copied to clipboard Look for disks with a status of Inspect the ASM Alert Log
This command checks and attempts to repair the found corruption, which typically resolves the alert.
When a physical disk or storage network pipeline exhibits anomalies, the health checker records a localized failure. It handles these using several specific operations:
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.
To minimize the risk of encountering this or similar alerts, implement these best practices:
Open an SR with Oracle and attach:
: If the ASM disk group hosts the Cluster Registry (OCR) or Voting Disks, a failure can cause node evictions or cluster instability. Storage Latency/I/O Timeouts
If your monitoring dashboard flags this error, follow these structured steps to isolate and fix the root problem:
Identify the name of the relevant health check (e.g., 'HM_RUN_361') and use it to generate the full diagnostic report. The report will pinpoint the exact nature of the failure.
If the ASM manages audit trails or session data, the database writer may have hit a connection limit. The health checker attempted to write a "heartbeat" record and timed out.
-- Check detailed status of all disks in all disk groups SELECT group_number, disk_number, name, path, state, mode_status, header_status, total_mb, free_mb FROM v$asm_disk;
: The metadata (headers) on one or more ASM disks may be corrupted or in a "FORMER" or "PROVISIONED" status instead of "MEMBER". Voting File Issues
Follow these diagnostics to isolate and address the exact storage failure: Step 1: Examine the ASM Alert Log
Connect to the ASM instance and run:
: Physical corruption of the disk header can prevent ASM from identifying the disk as a "MEMBER" of a group. Investigative Steps
) will have created an HTML report. Locate this report to see the specific and description of the failure. Verify ASM Disk Status utility to check the status of your disks and disk groups: asmcmd lsdsk -t asmcmd lsdg Use code with caution. Copied to clipboard Look for disks with a status of Inspect the ASM Alert Log
This command checks and attempts to repair the found corruption, which typically resolves the alert.