Data Guard Redo transport with cold failover clusters
(Doc ID 1119807.1)
Last updated on DECEMBER 27, 2019
Applies to:Oracle Database - Enterprise Edition
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
This note provides DBAs the information necessary to configure Data Guard redo transport when primary or standby databases are also deployed on cold failover clusters (also referred to as active/passive clusters).
Data Guard redo transport configuration for Cold Failover Clusters.
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 = BOSTON,CHICAGO
SQL Net Alias / Service = BOSTON,CHICAGO
Host / VIP = chicago_host_VIP,boston_host_VIP,chicago_host1ip,chicago_host2ip,boston_host1ip,boston_host2ip
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
|Configuring Data Guard Redo Transport|
|Restarting the Apply at the Standby Database|