Asm Health Checker Found 1 New Failures

Once you have the log, you need to identify the specific failure within your ASM instance. Oracle provides powerful SQL queries to interrogate the Health Monitor directly.

: SELECT operation, state, est_minutes FROM v$asm_operation; Common Remediation Steps KB88485 - My Oracle Support

asmcmd checkset -g DATA

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" asm health checker found 1 new failures

: A disk group may have been forced to dismount due to lost connectivity or multiple disk failures in a failure group. Disk Header Corruption

Run the following command to see the specific failure identified: list failure Use code with caution.

The error message "ASM Health Checker found 1 new failures" typically appears in the Oracle ASM alert logs when the system detects an issue with a disk or disk group Once you have the log, you need to

When it reports a "new failure," it means a specific "check" (such as disk connectivity, metadata consistency, or space usage) has moved from a PASS to a FAIL state. 2. Immediate Step: Identify the Failure

ALTER DISKGROUP <disk_group_name> CHECK;

flowchart TD A[ASM Alert Log Message "ASM Health Checker found 1 new failures"] --> B(Step 1: Run Diagnostic CHECK) B --> CCheck V$ASM_OPERATION C --> D[Step 2: Generate Health Check Report] D --> E[Step 3: Analyze Failure] E --> FCorruption Found? F -- Yes --> G(Step 4: Execute CHECK ALL REPAIR) G --> H[Step 5: Monitor Rebalance] H --> I[Step 6: Re-validate & Verify] I --> J[Step 7: Document & Prevent] F -- No --> K[False Positive? Engage ASM Team] Disk Header Corruption Run the following command to

This command checks and attempts to repair the found corruption, which typically resolves the alert.

A common cause of sudden failures is "policy drift"—where a security administrator tightens policies, accidentally breaking automated systems.

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