Configuration Prerequisites and Operational Steps for Higher Availability for a RECO disk group or Fast Recovery Area Failure
(Doc ID 2059780.1)
Last updated on MARCH 22, 2019
Applies to:Oracle Exadata Storage Server Software - Version 184.108.40.206.0 and later
SPARC SuperCluster T4-4 - Version All Versions to All Versions [Release All Releases]
Oracle Exadata Hardware - Version 220.127.116.11 and later
Information in this document applies to any platform.
Oracle recommends using High Redundancy Disk groups to provide the highest level of storage data protection and availability for mission critical applications. On Exadata, the default Exadata deployment is HIGH redundancy DATA and normal redundancy RECO and DBFS_DG where DATA contains all the data files, log files, control files, spfiles, OCR and possible voting files (if 5 cells or more otherwise OCR and voting files reside in DBFS_DG with optional quorum disks). With this Exadata deployment, RECO or the Fast Recovery Area (FRA) normally will contain archive logs, flashback logs and possible incremental backups. For non-Exadata, customers normally use ASM with external redundancy and provide additional redundancy to the DATA disk group versus RECO disk group.
This document describes the configuration prerequisites and operational steps required to keep the database running if you lose your RECO or FRA. It uses the Exadata best practice case where a customer chooses the new default Exadata deployment of high redundancy DATA and normal redundancy RECO as an initial configuration, but applies to any configuration with RECO deployed with normal redundancy. It describes the operational best practices after losing RECO (the default FRA on Exadata) and DBFS_DG disk groups at a later stage. This description can be generally applicable to non-Exadata.
The information in this document applies to Exadata Storage Server Software 11g Release 2 (11.2) and higher, Oracle Grid Infrastructure 11g Release 2 (11.2) and higher and Oracle RDBMS 11g Release 2 (11.2) and higher. Although it is recommended that earlier releases follow the same guidelines, behavior and error messages can be different in those earlier releases.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Section A: Configuration Prerequisites|
|Section B: Operational Steps after losing RECO|
|Section C: Operational Steps after losing DBFS_DG|
|Section D: Data Guard or GoldenGate implications|