How to Setup Active DataGuard on Exadata
(Doc ID 1580796.1)
Last updated on SEPTEMBER 28, 2021
Applies to: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
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Purpose of this article is too provide step by step instructions for deploying Active DataGuard Configuration within an Exadata Environment.
Transport methods within an Exadata Environment depending upon how the environment is architected can utilize one of 3 transport methods -->
1). Standard Client Network which would be used by SCAN/VIP Network, typically 1gE
2). IB/SDP Protocol Deployment, this is only applicable if the Primary/Standby are connected via Spine Switch's. Located in the same data center physically connected to each other.
3). High Speed Transport using 10gE Interface SFP Module over LAN or WAN
Article assumes that Primary and Standby sites are both running on Exadata Hardware.
This does not need to be exact Exadata Image release however following best practices ideally we would be running the exact same image.
With respect too Oracle Enterprise Linux release this can differ again though not ideal.
Pre-requisite is that Grid Insfrastructure is the same version and the Oracle RDBMS must be the same version and release at both primary/standby sites.
Software is already installed at both Primary/Standby environments with the same Exadata Bundle Patch's applied to both GRID & RDBMS Oracle along with any required overlay patch's.
Verify this at both ends with 'opatch lsinventory'
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