Scribd
Upload
225 views4 pages

Oracle Dataguard Redo Route Setup Forward Log Shipping

This document discusses setting up Oracle Dataguard redo route configuration to have a primary database ship logs to an active dataguard database, which then ships the logs to three physical standby databases. The primary database is RAC with 2 nodes shipping to the active dataguard RAC with 2 nodes, which then ships to the 3 physical standby databases, each which are RAC with 2 nodes. Redo routes are used to configure the primary to ship to the active dataguard, and the active dataguard to ship to the three physical standbys.

Uploaded by

Khansex Shaik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
225 views4 pages

Oracle Dataguard Redo Route Setup Forward Log Shipping

This document discusses setting up Oracle Dataguard redo route configuration to have a primary database ship logs to an active dataguard database, which then ships the logs to three physical standby databases. The primary database is RAC with 2 nodes shipping to the active dataguard RAC with 2 nodes, which then ships to the 3 physical standby databases, each which are RAC with 2 nodes. Redo routes are used to configure the primary to ship to the active dataguard, and the active dataguard to ship to the three physical standbys.

Uploaded by

Khansex Shaik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Oracle Dataguard Redo Route Setup

Forward log shipping

The intention here is to have 4 copies of the database. The Primary ships logs to Active
Dataguard and the ADG further forward ships the redo logs to downstream 3 physical standby
database.

The setup used in this scenario is

• Primary database (RAC 2 nodes) → Active standby Dataguard (RAC 2 nodes)


➔ 3 Physical standby database ( RAC , 2NODES)

We are using this setup so there is no overhead on the primary to ship redo logs to multiple
destinations

We are using the concept of “RedoRoute” to route the Log shipping , below is the simple
architecture in this scenario
DGMGRL configuration of all databases before changes
DGMGRL> show configuration

Configuration - ORADB

Protection Mode: MaxPerformance


Members:
ORADB - Primary database
ORADB_ADG - Physical standby database → Active Standby
Dataguard
ORADB1_STBY - Physical standby database
ORADB3_STBY - Physical standby database
ORADB2_STBY - Physical standby database

Value before setting up RedoRoute

DGMGRL> show database ORADB redoroutes


RedoRoutes = '' → No Redo route setup currently

To setup RedoRoute according to the architecture diagram

. oraenv=ORADB1

dgmgrl /

1.) Primary to Active Dataguard setup

edit database ORADB set property


redoroutes='(LOCAL:ORADB_ADG)(ORADB:ORADB1_STBY,ORADB2_STBY,ORADB3_STB
Y)';

Status of Dataguard after setting up redo route

DGMGRL> show database ORADB redoroutes


RedoRoutes = '(LOCAL:ORADB_ADG )'

2.) ADG to 3 Standby setup

DGMGRL> edit database ORADB_ADG set property redoroutes=


'(ORADB:ORADB1_STBY,ORADB2_STBY,ORADB3_STBY)';
Property "redoroutes" updated
DGMGRL> show configuration

Configuration - ORADB

Protection Mode: MaxPerformance


Members:
ORADB - Primary database --> Primary forwarding to ADG
ORADB_ADG - Physical standby database --> ADG forwarding to 3 snapshot db's
ORADB1_STBY - Physical standby database (receiving archived redo)
ORADB2_STBY - Physical standby database (receiving archived redo)
ORADB3_STBY - Physical standby database (receiving archived redo)

Fast-Start Failover: Disabled

Configuration Status:
SUCCESS (status updated 52 seconds ago)

Logs applied successfully after the changes and in current with the
primary

DGMGRL> show database ORADB_ADG ;

Database - ORADB_ADG

Role: PHYSICAL STANDBY


Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 0 seconds ago)
Apply Lag: 0 seconds (computed 0 seconds ago)
Average Apply Rate: 192.00 KByte/s
Real Time Query: ON
Instance(s):
ORADB1 (apply instance)
ORADB2

Database Status:
SUCCESS

DGMGRL> show database ORADB1_STBY ;

Database - ORADB1_STBY

Role: PHYSICAL STANDBY


Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 1 second ago)
Apply Lag: 0 seconds (computed 1 second ago)
Average Apply Rate: 298.00 KByte/s
Real Time Query: OFF
Instance(s):
ORADB1 (apply instance)
ORADB2
Database Status:
SUCCESS
DGMGRL> show database ORADB3_STBY ;

Database - ORADB3_STBY

Role: PHYSICAL STANDBY


Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 1 second ago)
Apply Lag: 1 second (computed 0 seconds ago)
Average Apply Rate: 139.74 MByte/s
Real Time Query: OFF
Instance(s):
ORADB3

Database Status:
SUCCESS

DGMGRL> show database ORADB2_STBY;

Database - ORADB2_STBY

Role: PHYSICAL STANDBY


Intended State: APPLY-ON
ORADB2_STBY Transport Lag: 0 seconds (computed 0 seconds ago)
Apply Lag: 0 seconds (computed 1 second ago)
Average Apply Rate: 25.50 MByte/s
Real Time Query: OFF
Instance(s):
ORADB2

Database Status:
SUCCESS

You might also like