My Oracle Support Banner

Sharing Archive Redo Log Between Two Physical Standby Databases (Doc ID 833364.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.2 [Release 10.1 to 11.2]
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
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 05-APR-2011***


Goal

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:

Primary database db_unique_name - chicago on Host-I
Physical Standby db_unique_name - boston on Host-II
Physical Standby db_unique_name - newyork on Host-III

Directory location - /u01/app/oracle

************************

If two standby databases exist in the same host and share the same h/w, then primary can choose to send the archived redo logs to only one standby. The other standby will recover the database using the same archived redo log received by the first standby. This reduces network bandwidth and disk space usage.

Solution

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
Goal
Solution

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