My Oracle Support Banner

Changing the network used by the Data Guard Broker Version 10.2 for redo transport (Doc ID 730361.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version to [Release 10.1 to 10.2]
Information in this document applies to any platform.


NOTE: If you are using Oracle Database version or higher please refer to Note 960510.1 - This note is only for Oracle Database version 10.2


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 Unique Name: STDB2_GAL,STDB2_INV
Instance Name:  STDBY2
Disk Group Names: +FRA01


Prior to Oracle Database 11g you can see from the Data Guard Broker documentation states the following in regards to the redo archiving destinations in a broker configuration:

On the standby database, the broker registers a special service name db_unique_name_XPT with the standby listeners for redo transport services. On the primary database, the broker extracts the listener address from the LOCAL_LISTENER initialization parameter, and uses the service name db_unique_name_XPT and the value of INSTANCE_NAME to construct the connect descriptor so that redo transport services transmit archived redo log files to the standby apply instance.

How do you change the redo transport network configuration when a Data Guard configuration is in place, from the public network interfaces currently used to a network dedicated to redo transport?

 The Scenario in more detail:

Currently we have a listener accepting connections through the public IP/hostnames shown below




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
 Overview of the process
The Steps to implement the listener/network changes:

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