Creating a Physical Standby Database for 11g Through 19c Databases
(Doc ID 2275154.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - 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 of this Document
This document serves as the master note for Creating a Standby Database and the recommended options in an Oracle Database version 11.2, 12c or beyond environment integrating the Maximum Availability Architecture (MAA) Oracle Data Guard configuration best practices.
This document applies to Oracle Server versions 11.2.0.x thru 19c and higher.
Maximum Availability Architecture
The Maximum Availability Architecture (MAA) defines Oracle’s most comprehensive architecture for reducing downtime for scheduled outages as well as preventing, detecting and recovering from unscheduled outages. Real Application Clusters (RAC) and Oracle Data Guard are integral components of the Database MAA reference architectures and solutions.
More detailed information, such as a discussion of the purpose of MAA and the benefits it provides, can be found on the Oracle Technology Network (OTN) at https://www.oracle.com/database/technologies/high-availability/maa.html
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
|MAA Recommended Instantiation Methods|
|1. RDBMS Version 12c through 19c with Optimizations for Very Large Databases|
|2. RDBMS Version 11.2 and lower|