Asm Health: Checker Found 1 New Failures
: If your diskgroup uses external redundancy and a disk fails, the group will likely dismount immediately, potentially crashing your database. Intermediate States
: Corruption in ASM metadata blocks (typically within the first 250 blocks) detected during routine operations or rebalancing.
Look for specific Oracle error codes (such as ORA-15032 , ORA-15075 , or ORA-27063 ) generated at the exact timestamp of the Health Checker alert. Step 3: Check Grid Plug and Play (GPNPD) and CSS Logs
: Physical corruption of the disk header can prevent ASM from identifying the disk as a "MEMBER" of a group. Investigative Steps asm health checker found 1 new failures
Loss of physical fiber channel paths, faulty host bus adapters (HBAs), or incorrect multipathing layers ( multipathd ) will drop the physical storage paths. ASM detects this loss of communication as a failed disk heartbeat. 3. Disk Header Mutilation
Look for disks with a state of FAILED , FORCING , or HUNG . An unhealthy disk is a common cause of the alert.
Physical drive dropouts, bad sectors, SAN controller faults, or Fibre Channel/iSCSI network interruptions. : If your diskgroup uses external redundancy and
Check free space: SELECT name, free_mb, total_mb, usable_file_mb FROM v$asm_diskgroup; 5. Clearing the Alert
:Use the ADR Command Interpreter (ADRCI) to list the details of the specific failure. adrci> list failure Use code with caution. Copied to clipboard
By understanding the causes of ASM health checker failures and taking proactive steps to prevent them, you can ensure the reliability and performance of your Oracle database storage infrastructure. Step 3: Check Grid Plug and Play (GPNPD)
A physical disk or LUN has lost connectivity to the OS due to a faulty SAN switch, cable, or storage controller. ASM has taken the disk offline and started the timer to drop it. How to Fix: Check the status of the disks in the disk group:
— End —
SELECT name, path, header_status, mode_status FROM v$asm_disk; Use code with caution.