Asm Health Checker Found 1 New — Failures _hot_

(Requires immediate investigation to prevent data loss or service disruption) Potential Causes & Findings Disk Group Dismount

If the failure coincides with a scheduled credential rotation, the rotation Lambda function may have failed mid-process.

Do you have the or the specific Failure ID from your logs? I can help you interpret the exact cause. asm health checker found 1 new failures

ALTER DISKGROUP DATA SET ATTRIBUTE 'scrub.mode'='AUTO'; ALTER DISKGROUP DATA SET ATTRIBUTE 'scrub.interval'='7d';

[Trigger Alert] -> Check ASM Alert Log -> Run ASMCMD/SQL -> Inspect OS Paths -> Rebalance/Remount Step 1: Trace the Associated Errors (Requires immediate investigation to prevent data loss or

# Check if device exists ls -l /dev/oracleasm/disks/ (if using ASMLIB) or ls -l /dev/mapper/ | grep asm

-- 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; ALTER DISKGROUP DATA SET ATTRIBUTE 'scrub

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

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]