Cascaded Standby Databases in Oracle 12c (Doc ID 1542969.

1)

In this Document
Purpose
Details
Real-Time Cascading
Prerequisites
Setup
Far Sync Standby Database
Data Guard Broker and Cascaded Standby Database
References
APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later

Information in this document applies to any platform.
***Checked for relevance on 13-Jul-2015***
PURPOSE

This Documents explains the Enhancements for Cascaded Standby Databases in Oracle
12c.

DETAILS

There are new Possibilities for cascading Standby Databases in Oracle 12c. The main
Differents between Oracle 12c and the previous Releases are:

Real-Time Cascading
Far Sync Standby Database
Data Guard Broker now supports cascaded Standby Database

However, you can still only cascade a Standby Database from a Physical Standby
Database. It is not supported to cascade a Standby Database from a Logical Standby
Database.

Real-Time Cascading

It is now possible to forward Redo in Real-Time Mode from the first to the cascaded
Standby Database. So the Redo Record is forwarded to the cascaded Standby Database
once written into a Standby RedoLog of the first Standby Database.

Non Real-Time Cascading means that the whole Log Sequence is transferred to the
terminal Standby Database(s) after a Log Switch on the Primary Database.

Prerequisites

First (Cascading) Standby must be a Physical or Far Sync Standby Database

Standby RedoLogs must be in Place and used at least on the Cascading Standby
Database
Active Data Guard Option must be licensed
Primary, Cascading and Cascaded Standby Database db_unique_name must be present in
the dg_config of log_archive_config on all the Databases

Setup

First of all setup a Data Guard Environment as usual to the cascading Standby
Database. The Log Transport Method should be ‘SYNC’ and Standby RedoLogs must be
configured on the cascading Standby Database. Once you created the cascaded Standby
Database you can now setup the cascading Log Transport Services. Here are some
Hints for correct Setup:

Primary, Cascading and Cascaded Standby Database db_unique_name must be present in

the dg_config of log_archive_config on all the Databases
Setup log_archive_dest_n on the cascading Standby Database to serve the cascaded
(terminal) Standby Databases using the Attribute
‘valid_for=(STANDBY_LOGFILES,STANDBY_ROLE)’
You can toggle between Real-Time and Non Real-Time Cascading using the Log
Transport Method.
ASYNC = Real-Time Cascading

SYNC = Non Real-Time Cascading

You can only use log_archive_dest_1 until log_archive_dest_10 for Non Real-Time
Cascading Destinations where all log_archive_dest_n’s can be used for Real-Time
Cascading on the Cascading Standby Database
The Cascading Standby Standby can be in any Protection Mode
A Cascading Standby Database can serve one or multiple terminal Standby Databases
FAL_SERVER on the cascading Standby Database should be set to the Primary or any
other Standby Database served by the Primary Database directly
FAL_SERVER on the terminal Standby Database should be set to the cascading Standby
Database or the Primary Database

Far Sync Standby Database

A Far Sync Standby Database is a cascading Standby Database which acts as a Redo
Log Repository for a Terminal Database. It does not contain any Datafiles. Only Log
Transport Services are active on a Far Sync Standby Database. The Advantage of a
Far Sync Standby Database is that it can be a local ArchiveLog Repository for the
Primary Database acting in Maximum Protection Mode where the Physical or Logical
Standby Database can be on a far remote Site. See

Note 1565071.1: Data Guard 12c New Feature: Far Sync Standby

for further Details and Setup of a Far Sync Standby Database.

Data Guard Broker and Cascaded Standby Database

There is a new Data Guard Broker Property called ‘RedoRoutes’ used to build and
implement a cascaded Data Guard Broker Configuration. It has the following Format:

RedoRoutes = ‘(<Redo Source> : <Redo Destination>)’

Redo Source: This is the Source the Redo is coming from. It can be a db_unique_name
or the ‘LOCAL’-Keyword which is an Alias for the local Database Name (Cannot be
used for a Far Sync Standby Database)

Redo Destination: This is the Destination where the Redo is shipped to from this
Database. It can be one or more (comma separated) db_unique_name’s or the ‘ALL’-
Keyword which is an Alias for all possible Destinations inside the Data Guard
Broker Configuration. Optional you can also specify the Transport Method to be used
to the Destination. This can be

SYNC: corresponds to log_archive_dest_n Attributes ‘SYNC AFFIRM’

or Non Real Time Cascade
ASYNC: corresponds to log_archive_dest_n Attribute ‘ASYNC’ or Real
Time Cascade
FASTSYNC : corresponds to log_archive_dest_n Attributes ‘SYNC NOAFFIRM’

Example:

Primary Database: prim

Cascading Standby Database: local_stdby

Cascaded (terminal) Standby Database: remote_stdby

We want to serve the local Standby Database with ‘SYNC NOAFFIRM’ and the remote
Standby Database in Real-Time Cascade Mode. So the Setting would be:

Primary Database (prim)

RedoRoutes = ‘(LOCAL : local_stdby FASTSYNC)’

-> So the Primary Database only ships Redo to the local Standby Database, but has
Archive Destination to the remote Standby Database

Local Standby Database (local_stdby)

RedoRoutes = ‘(prim : remote_stdby ASYNC)’

-> Here we configure that the Redo coming from ‘prim’ is forwarded in Real-Time
Cascade (ASYNC) to the remote Standby Database

REFERENCES

NOTE:1565071.1 - Data Guard 12c New Feature: Far Sync Standby

Was this document helpful?

Yes
No

Document Details

Email link to this documentOpen document in new windowPrintable Page

Type:
Status:
Last Major Update:
Last Update:
Language:
BULLETIN
PUBLISHED
Apr 25, 2014
Jul 13, 2015

Related Products

Oracle Database - Enterprise Edition

Information Centers

Information Center: Overview Database Server/Client Installation and

Upgrade/Migration [1351022.2]

Index of Oracle Database Information Centers [1568043.2]

Information Center: Overview of Database Security Products [1548952.2]

Document References
Data Guard 12c New Feature: Far Sync Standby [1565071.1]

Recently Viewed

Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2

or 12cR1 database . [1585343.1]

Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)

[556610.1]

Actions For DST Updates When Upgrading To Or Applying The 11.2.0.2 Patchset
[1201253.1]

Troubleshooting Assistant: Oracle Database/Client Upgrade - Downgrade

[1561791.2]

Complete Checklist for out-of-Place Manual Upgrade from Previous 11.2.0.N

Version to the Latest 11.2.0.N Patchset [1276368.1]

Show More

Didn't find what you are looking for?Ask in Community...