When the ASM health checker detects a problem, it logs an error message indicating that a failure has been detected. The message may look like this:
This command checks and attempts to repair the found corruption, which typically resolves the alert.
Power outages or improper storage provisioning can corrupt the primary sector (Block 0) of an ASM disk. asm health checker found 1 new failures
This command performs a comprehensive, read-only analysis of the disk group's consistency and reports any findings in the alert.log file. Executing this command confirmed the initial alert in a real-world case, validating that a genuine inconsistency existed.
To manage ASM health effectively, consider using these Oracle tools: When the ASM health checker detects a problem,
If your monitoring dashboard flags this error, follow these structured steps to isolate and fix the root problem:
The Health Checker warning is an aggregate flag. To find the specific culprit, inspect the ASM alert log located under your Oracle Diagnostic Destination: This command performs a comprehensive, read-only analysis of
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.
Often, the health checker will detect corruption that can be automatically fixed. The ALTER DISKGROUP command is the primary tool for this task.
chown grid:asmadmin /dev/sdg chmod 660 /dev/sdg -- If persistent across reboot, fix udev rules: vi /etc/udev/rules.d/99-oracle-asm.rules -- Add: KERNEL=="sdg", OWNER="grid", GROUP="asmadmin", MODE="0660"
ALTER DISKGROUP DATA SET ATTRIBUTE 'compatible.asm' = '12.2';