Best Practice : Corruption in Oracle ASM Header

Posted by PDSERVICE on Apr 09, 2020 In

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later

Oracle Database Cloud Schema Service - Version N/A and later

Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later

Oracle Database Exadata Express Cloud Service - Version N/A and later

Information in this document applies to any platform.

PURPOSE

The purpose of this note is to provide a summary of Best Practices to be adopted while handling Corruption in ASM Header

SCOPE

This note applies to Grid Infrastructure for both Clustered and Standalone ASM environment.

DETAILS

I. My Oracle Support Document: How To Restore/Repair/Fix An Overwritten (KFBTYP_INVALID) ASM Disk Header (First 4K) 10.2.0.5, 11.1.0.7, 11.2 And Onwards

Document:1088867.1: This document provides an example about “how to restore/repair/fix an overwritten ASM Disk Header (first 4K) on 11.1.0.7 and Onwards”.

II. My Oracle Support Document: ASM Corruption: Case #1: How To Fix The ASM Disk HEADER_STATUS From FORMER or PROVISIONED to MEMBER

Document: 1448799.1: This document explains, in detail, the steps required (with an example) to fix the ASM disk header from FORMER or Provisioned to MEMBER under the below scenarios:

A) Diskgroup was dropped by accident using the "SQL> drop <DG name> diskgroup;" statement.

B) Or under strange situations as described in the next bug:

Bug:13331814 ASM DISKS TURNED INTO FORMER WHILE DISKGROUP IS MOUNTED.

REFERENCES

NOTE:1088867.1 - How To Restore/Repair/Fix An Overwritten (KFBTYP_INVALID) ASM Disk Header (First 4K) 10.2.0.5, 11.1.0.7, 11.2 And Onwards

NOTE:1448799.1 - ASM Corruption: Case #1: How To Fix The ASM Disk HEADER_STATUS From FORMER or PROVISIONED To MEMBER.

You are here

Best Practice : Corruption in Oracle ASM Header

Best Practice : Corruption in Oracle ASM Header