When the health checker encounters these physical corruptions during its integrity checks, it will log the failure.
Alternatively, dynamically add a new disk to the group to trigger an automatic rebalance.
Share public link
This error typically appears when the ASM instance performs an internal check and encounters an issue that could lead to a disk group being forced to dismount. Why Did This Happen? asm health checker found 1 new failures updated
Remember: a healthy ASM instance is the bedrock of a healthy Oracle database. Treat the ASM Health Checker as your most vigilant storage guardian.
The "1 new failure" usually falls into one of four categories: Failure Category Common Root Cause Typical Error Code Lost paths to storage (Mpath/SAN failure) ORA-15032 , ORA-15080 Metadata Corruption Power outage, abrupt shutdowns, bugs ORA-15130 , ORA-15042 Space Exhaustion Archive logs or backups filling up disk groups ORA-15041 Permission/Ownership Misconfigured /dev/oracleasm or Udev rules ORA-15025 Step 3: Run Manual Verification Commands
If the failure is directly related to storage, the ASM instance alert log will pinpoint the disk or group: $GRID_BASE/diag/asm/+asm/+asm1/trace/alert_+asm1.log Use code with caution. Step 2: Identify Common Causes of ASM Failures Why Did This Happen
The ASM Health Checker constantly audits the storage environment's structural and operational integrity. When it logs an updated failure count, it is usually responding to one of four common architecture failures:
SELECT group_number, name, path, state, failgroup, mode_status FROM v$asm_disk WHERE state != 'NORMAL';
If the failure indicates a physical disk failure ( STATE = 'OFFLINE' or MODE_STATUS = 'OFFLINE' ), you must replace it. ALTER DISKGROUP OFFLINE DISK ; Use code with caution. Replace the physical disk at the storage level. Online the disk (rebalance will occur automatically): ALTER DISKGROUP ONLINE DISK ; Use code with caution. Scenario C: Metadata Corruption (Critical Action) The "1 new failure" usually falls into one
[Your Name/Role] Status: Awaiting resolution
DBMS_HM.GET_RUN_REPORT('HM_RUN_361') Basic Run Information Run Name : HM_RUN_361 Run Id : 361 Check Name : DB Structure Integrity Check Mode : REACTIVE Status : COMPLETED Start Time : 2011-11-13 11:02:11.067000 -05:00 End Time : 2011-11-13 11:02:19.989000 -05:00 Error Encountered : 0 Source Incident Id : 0 Number of Incidents Created : 0 Run Findings And Recommendations Finding Finding Name : System datafile is old Finding ID : 362 Type : FAILURE Status : CLOSED Priority : CRITICAL Message : System datafile 1:'H:\<PATH.\SYSTEM.DATA1' needs media recovery Message : Database cannot be opened Finding Finding Name : Datafile is old Finding ID : 368 Type : FAILURE Status : CLOSED Priority : HIGH Message : Datafile 2: 'H:\<PATH>\UNDO.DATA1' needs media recovery
Automatic Storage Management (ASM) is a crucial component of Oracle databases, providing a robust and efficient storage management system. However, like any complex system, ASM can encounter issues that impact database performance and security. To identify and address these issues, Oracle provides the ASM Health Checker, a utility that monitors ASM's overall health and alerts administrators to potential problems. In this essay, we will discuss the importance of ASM Health Checker, its functionality, and what it means when it reports "Found 1 new failures updated."