My Oracle Support Banner

Data Guard Transport Considerations on Oracle Database Machine (Exadata) (Doc ID 960510.1)

Last updated on FEBRUARY 02, 2022

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Exadata Hardware - Version and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


In a typical Data Guard configuration, the primary database uses the same network to transmit redo to the standby database as client connections use to connect to the primary database. For example, both client connections and Data Guard redo transport traffic use the eth1 Ethernet interface. In configurations that place high demand on the network, combining both types of traffic on the same network can impact performance. Also, business availability requirements may mandate that Data Guard traffic be on a separate network from client connections.

Move Data Guard network traffic to a separate network interface
This approach to eliminate contention between the different types of network traffic is to move Data Guard redo transport to a separate network. For example, client connections continue to use the eth1 Ethernet interface, but Data Guard redo transport instead uses the eth3 Ethernet interface to access a dedicated disaster recovery network.  It is not recommended to use Infiniband for Data Guard transport as it becomes a single point of failure.

The remainder of this document explains how to direct Data Guard network traffic through a different network than what is used for client connections to the database. 

NOTE: In the images and/or the document content below, the user information and environment data used represents
fictitious data from the Oracle sample schema(s),Public Documentation delivered with an Oracle database product or
other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental
and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example
to describe the procedure:

Database Name  = adgprod
DB Unique =  adgprod, adgprodstby
Services = adgprodstby1,adgprodstby2,


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
 Configuration for 11.2
 Configuration for 11.1
 Sending Redo to Specific Standby Instances

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.