Cascading standby

I was following the note 409013.1 to set the Cascading standby. (11.2.0.3 on Linux)
Primary - Boston Standby - Chicago Cascading standby - Denver.
I see that Primary(Boston) is directly transferring the Archive log to Denver ( C-standby). (LOG_ARCHIVE_DEST_2).
Ideally, it should go from the Chicago to Denver. We have a value for (LOG_ARCHIVE_DEST_3) for this as well on Chicago.
I tried the same setup, by deferring the LOG_ARCHIVE_DEST_2, but chicago never casacdes the standby to Denver.
If i stop Denver and restart, it pulls and applies all the pending archives, but never applies the fresh ones.
When i ENABLE dest 3 on primary, it ships directly to denver.
There is no error in any of the alert log,V$MANAGED_STANDBY,v$dataguard_status etc.

Hi,
How long did you wait after deferring dest_2?
As per the note,
A cascaded destination will therefore always have a greater redo transport lag, with respect to the primary database, than the cascading standby database.
Check below.
Redo Transport Services
Thank you!!

Similar Messages

Switchover scenario in a cascaded standby setup

Hi,
I have a setup of primary and standby databases in three locations A, B, C as below:
Database version: 11.1.7.0
In location A I have the primary database that ships redo log to a physical standby at location B alone.
In location B I have a physical standby that replicates to site C.
In site C I have the final physical standby that receives its redo logs directly from site B. In essence, this is a cascaded standby database.
My question is about the switchover:
Currently, both the instances in sites A and B have the LOG_ARCHIVE_DEST_3 set to point to site C and this is valid for standby role alone.
Which means in case the two sites - A & B reverse roles, site C will continue receiving redo logs from either A or B, depending on which one is the new standby.
However, the doubt comes in if site C were to become the new primary instance. I suspect that I would need to add two parameters LOG_ARCHIVE_DEST_2 and LOG_ARCHIVE_DEST_3 and point them to sites A and B respectively, and make them valid only for the primary role. In this case, if site C becomes the new primary, then both sites A and B can continue receiving redo logs from site C.
Anyone who has ever implemented this?
Regards,
dula

The scenario in the doc. may also help you:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/cascade_appx.htm#i638620
Example E-1 Sample Use of Initialization Parameters in Cascaded Destinations
Boston Database (Primary Role)
DB_UNIQUE_NAME=boston
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
LOG_ARCHIVE_CONFIG='DG_CONFIG=(chicago,boston,denver)'
LOG_ARCHIVE_DEST_1='LOCATION=/arch1/boston/ VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=boston'
LOG_ARCHIVE_DEST_2= 'SERVICE=denver VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=denver'
LOG_ARCHIVE_DEST_3= 'SERVICE=chicago VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=chicago'
Chicago Database (Standby Role)
DB_UNIQUE_NAME=chicago
LOG_ARCHIVE_CONFIG= 'DG_CONFIG=(chicago,boston,denver)'
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
LOG_ARCHIVE_DEST_1= 'LOCATION=/arch1/chicago/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=chicago'
LOG_ARCHIVE_DEST_2= 'SERVICE=denver VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=denver'
LOG_ARCHIVE_DEST_3= 'SERVICE=boston VALID_FOR= (ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=boston'
Denver Database (Standby Role)
DB_UNIQUE_NAME=denver
LOG_ARCHIVE_CONFIG= 'DG_CONFIG=(chicago,boston,denver)'
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
LOG_ARCHIVE_DEST_1= 'LOCATION=/arch1/denver/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=denver'
LOG_ARCHIVE_DEST_2= 'LOCATION=/arch2/denver/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=denver'
Both the Boston primary database and the Chicago physical standby database define the LOG_ARCHIVE_DEST_2 initialization parameter as SERVICE=denver VALID_FOR=(STANDBY_LOGFILES, STANDBY_ROLE). Hence, even if the Boston and Chicago databases switch roles, the redo data will continue to be forwarded to the Denver database. Remember, as part of the original setup of the physical standby database, you should define a local destination, VALID_FOR=(ALL_LOGFILES, PRIMARY_ROLE), that will be used for local archiving when the physical standby database transitions to the primary role.

Cascaded standby database

Hi,
I've seen a lot of documentation about cascaded standby setup, but none have defined how to build the second standby. The link below only describes how to configure the second standby for cascaded setup. Can anyone please elavorate how to create the second standby? Should we just build it just like the way we build the first standby, and then configure it as cascaded? OR should we build it using the first standby?
http://emrebaransel.blogspot.com/2010/08/dataguard-cascade-standby-database.html
Primary -> First standbyu -> Second Standby
Edited by: user13489456 on May 28, 2013 4:07 AM

user13489456 wrote:
Hi,
I've seen a lot of documentation about cascaded standby setup, but none have defined how to build the second standby. The link below only describes how to configure the second standby for cascaded setup. Can anyone please elavorate how to create the second standby? Should we just build it just like the way we build the first standby, and then configure it as cascaded? OR should we build it using the first standby?
http://emrebaransel.blogspot.com/2010/08/dataguard-cascade-standby-database.html
Primary -> First standbyu -> Second Standby
Edited by: user13489456 on May 28, 2013 4:07 AMWhat is the version you are using?
Creating another standby is same as how you create first standby database i.e RMAN duplicate/RMAN restore/HOT backup/Cold backup method , Here only configuration changes to configure redo transport and other parameters.
Here you can use either backup of primary or standby, it doesnt make any difference.

Cascading standby databases

Hi All,
Can anyone please throw some light on cascading standby databases, I needed to implement it, but dont have an idea as to how to go ahead with it. All I could find was the following metalink Id: 409013.1. Any help from you guys would be really appreciated.
Thanks,
Ajinkya

Hi Santosh,
The previous thread was abt one of the issue which I faced and I thought of uodating all about the reason why it happened. This thread was created so that I can gather more info abt cascading standby db, thought both of them are absolutely diff topics to discuss on,hence 2 diff threadsThat's Ok, Ajinkya. My point was, you're facing problem while performing log switch, people were co-operating you and you suddenly concluded that thread without achieving any result. Your thread may be beneficial for others.
My protection mode is maximium performance. ***************************************************************************************
Maximum Performance
This protection mode provides the highest level of data protection that is possible without affecting the performance of a primary database. This is accomplished by allowing transactions to commit as soon as all redo data generated by those transactions has been written to the online log. Redo data is also written to one or more standby databases, but this is done asynchronously with respect to transaction commitment, so primary database performance is unaffected by delays in writing redo data to the standby database(s).
This protection mode offers slightly less data protection than maximum availability mode and has minimal impact on primary database performance.
Reference: http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/protection.htm#CHDDAHJD
N.B.: the above statement is assuming that you're using standby redo logs. If not using SRL then local archiving will happen first and then that archive will be transferred to standby database. Please observe the functioning in the following diagram carefully.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1265592
Now ,the database following the diagram while transferring the redo data, will slow down the whole system not only the database. Here is the problem, you need to investigate at this point. Are you using any anti-virus which performs blockwise check while write/read? This may result in slow performance. Can you afford disabling your anti-virus for some time and check? :) .
And the general idea of going for cascaded standby was that my primary faces performance issue due to the network latency between the production and DR servers. So instead of my primary hampers till the archives are sent to the remote db, y cant I send those archives to a standby db on LAN, and from there I can send it to the remote server. Example:
A -- My primary
B -- My standby on LAN
C -- My standby on remote destiantion.
So now instead of A sending archives to C, it would send archives first to B which in turn will send it to C. In this way my dependency of A on C reduces which in result doesnt hamper my performance of A. and then B in turn would send the archives to C.
Regards,
AjinkyaThat seems ok to me. the above link is enough for setting up a cascaded setup (It's nothing but cascading the archive destination).
Regards,
S.K.

Cascading standby database on 9i

Hi,
PrimaryDB -> Archivelog Repository -> Physical Standby.
Archivelog repository is just holding redologs and pushing them to standby. Is this feature available in 9iR2?. I realize that it is available in 10G.
Thanks
Rajesh

Yes, check out the section "Cascaded Redo Log Destinations" in Oracle Data Guard Concepts and Administration in the 9iR2 docs.

Create cascading standby

Hi all,
Any one have experience with creating a cascading logical standby?
Currently we have a primary and a physical standby databases. We want create another logical standby which will be receiving archive logs from the existing standby to reduce the overhead on production.
My question is , can I use the backup of primary database to build the standby, or I have to copy the datafiles from the existing standby to the new one?
Thanks in advance.
Sharon

can I use the backup of primary database to build the standby, or I have to copy the datafiles from the existing standby to the new one?
Yes, you can use the backup of primary database to build the standby

Can read-only standby be cascaded from another DR physical standby

we are going to have one two-node RAC database in the primary site (site A), one Data Guard maintained standby database in the DR site (site B) and one ACTIVE Data Guard maintained read-only database for reporting (site C, on the same subnet as site B). My question is what is the best practice for the data guard configuration in terms of the redo log transportation, Is it possible to set up relay of redo log transport from one physical standby to another (database version 11gR2, data guard in Maximum Performance Mode):
1)     A->B->C (minimum overhead to primary site A, maximum delay to report site C)
2)     A->C->B (minimum overhead to primary site A, maximum delay to DR site C)
3)     A->B; A-C (maximum overhead to primary site A, minimum delay to site B and C)
Are all three configuration possible, which one would you recommend?
Any discussion document or white paper about the above configuration you can point to for me (I gather the scenario may be rare, but multiple physical standby instances set up are not uncommon, if to ignore active data guard part) ?
Edited by: user10786648 on 24/07/2012 17:40
Edited by: user10786648 on 24/07/2012 17:47
Edited by: user10786648 on 24/07/2012 23:36

Hello;
Welcome to the forum.
minimum overhead to primary site A, maximum delay to report site - ( I don't believe in emergency reports, Primary should rule. )
Will refer to these white papers :
Data Guard Redo Transport & Network Best Practices
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10gr2-dataguardnetworkbestpr-134557.pdf
And
Rapid Oracle RAC Standby
http://www.oracle.com/technetwork/database/availability/maa-wp-11g-racone-standby-501088.pdf
And of General interest
Oracle Data Guard with Oracle Database 11g Release 2
http://www.oracle.com/technetwork/database/features/availability/twp-dataguard-11gr2-1-131981.pdf
Oracle Data Guard Technical White Papers
http://www.oracle.com/technetwork/database/features/availability/data-guard-technical-info-152834.html
http://grokbase.com/t/freelists.org/oracle-l/11c18th65t/active-dataguard-ndash-ndash-cascade-standby-or-not
Best Regards
mseberg
Edited by: mseberg on Jul 24, 2012 7:55 PM

One primary and two physical standby database creation

hi
i want to create two standby (physical) and one primary dataguard.
so please tell me what is sequence for db_file_name_convert and db_file_name_convert.
i mean how i will give database name or path in this parameter.

Hello;
One option is Data Guard Cascading Standby.
Here are my complete test notes if it help :
http://www.visi.com/~mseberg/Data_Guard_Cascading_Standby_Setup_and_Test.pdf
Best Regards
mseberg

Use of arc processess in standby location

Hi,
What is the use of archive processes in standby database when the log shipping is done by arch process.

Sekar_BLUE4EVER wrote:
Hi,
What is the use of archive processes in standby database when the log shipping is done by arch process.Standby redo logs must be archived before the data can be applied to the standby database. The standby archival operation occurs automatically, even if the standby database is not in ARCHIVELOG mode. However, the archive process must be started on the standby database. Note that the use of the archiver process (ARCn) is a requirement for selection of a standby redo log.
Source:http://www.orafaq.com/node/957
...archive processes are responsible for archiving the ORL files as they become full and for resolving gaps in the redo stream to a standby database and on a standby database they are responsible for archiving the SRL files and forwarding the archive logs to a cascaded standby database.
Source:http://www.datadisk.co.uk/html_docs/oracle_dg/physical_setup.htm
Please read above lines at least 2 times, but slowly...
Regards
Girish Sharma

Can a physical standby propagate data to a logical standby?

Here is my situation. I have a RAC database that currently has a physical standby (also RAC cluster) for disaster recovery (DR) and I am about to create an additional logical standby for real-time reporting. My customer is asking if I can also create a logical standby for reporting that resides in the DR environment that would be available in a disaster. My question is can a physical standby propagate data to a logical standby? Is there any special configuration that would be required and what might it be if this is possible?
Thanks.

Hi,
Welcome. Yes it's possible, example in 11.2 :
A cascading standby database can cascade primary database redo to up to 30 cascaded destinations, each of which can be a physical, logical, or snapshot standby database.
http://download.oracle.com/docs/cd/E11882_01/server.112/e17022/log_transport.htm#SBYDB5122
Best regards
Phil

More than One Physical Standby Database

Hi All!
Is it possible to have more than one physical standby database? Does the procedure on how to create a single physical standby is the same as creating more than one? How about the configuration of the Primary database? Im planning this because I want the other physical standby to be used for read only access for our testing environment.
Please enlighten me.
Regards,
cmadiam

Think about it.
Q. What's the crux of Dataguard setup?
A. Redo transfer from primary to standby
Q.Which is the parameter you use to direct the redo transfer
A. LOG_ARCHIVE_DEST_n
Q. How many LOG_ARCHIVE_DEST_n parameters can be set?
A. 10; LOG_ARCHIVE_DEST_1 to LOG_ARCHIVE_DEST_10
Of the 10 LOG_ARCHIVE_DEST_n, one of them should be LOCAL destination, which means you can have 9 other REMOTE destinations ~~ 9 standby database. Physical or logical or mix of both.
Cheers.
Note: Each of the 9 standby database can cascade redo transfer to 9 other cascaded standby databases. WOW! now you do the math.

Steps for Data Guard with one primary and 2 standby

Hi,
Database :10.2.0.4, 11.2.0.1
Os: Windows , Unix
A ----------------> Primary database
B ----------------> Standby Database 1
C ----------------> Standby Database 2
I want to configure *2 standby* databases for single primary database.
Lets take, A ,B and C are my machines.My data guard configuration will be like,*archive logs will be moving* from A to B and A to C.
If i do any switchover in between A and B , now B is primary and remaining A and C are standby databases.At this stage also , archive logs should move from B to A and B to C. Also, same should happen from C to A and C to B,If i do switchover in between B and C.If everything is fine , then i will do switchback to main Primary database(A).
How do i have to mention PFILE in all machines ,the parameters like
LOG_ARCHIVE_DEST_1=LOCATION=<PATH> -- LOCAL ARCHIVE PATH
LOG_ARCHIVE_DEST_2=SERVICE=
LOG_ARCHIVE_DEST_3=SERVICE=
FAL_SERVER=
FAL_CLIENT=
STANDBY_FILE_MANAGEMENT=
In my tnsnames.ora , primary,standby1 and standby2 are my service entries and these are same in all of my machines.
Please suggest me , how do i can configure my pfiles in all machines ?.
Thanks,
Sunand

Not yet, but now you have me interested.
Please consider Flashback.
I still have to test but here's my take:
PRIMARY SETTINGS
*.FAL_SERVER=STANDBY
*.FAL_CLIENT=PRIMARY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=PRIMARY
*.LOG_FILE_NAME_CONVERT='STANDBY','PRIMARY'
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_DEST_STATE_3=ENABLE
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY 1 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_2='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY2 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY2
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY2
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY2'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY2'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
Edited by: mseberg on Nov 29, 2010 9:39 AM
The first test slapped me. Looking at 409013.1 Cascaded Standby Databases
Edited by: mseberg on Nov 29, 2010 12:49 PM

DR for a logical standby

Friends,
Oracle version 10.2.0.4:
On the primary site, we have one non-rac primary database P1. We will create a logical standby (L1) on primary site to be used for reporting. This logical standby L1 will have its own additional indexes and materialized views.
On the Disaster recovery site, which is at a remote location, a physical standby P2 will protect the primary database P1. What should be done such that the logical database L2 on the disaster recovery site remains in sync with L1? Also, if we were to lose the primary site, what should be done such that L2 gets fed by P2 after P2 takes over as primary?
Is such a configuration possible?
thanks for any thoughts.

Hi,
If you setup a physical standby L2, which will be sync with L1 this will be a cascaded configuration.
P1 --> L1 (logical) --> L2 (physical)
But this configuration is not supported. (It used to be, but not now... ) From my blog post about cascade standby databases: (http://emrebaransel.blogspot.com/2010/08/dataguard-cascade-standby-database.html)
The Layer1 standby database cannot be a logical standby where Layer2 can be. (Oracle mentions about Layer1 logical standby configuration on 10gR2 doc, and indicates that a Layer1 logical standby will generate and transmit redo information which won’t be identical with the one between primary and Layer1 standby. As a result "Layer2 physical standby databases created from a logical standby database will be a block-for-block copy of the logical standby database and a logical copy of the original primary database.”
But it is indicated that information in Metalink bulletin 409013.1 replaces Appendix E Cascaded Destinations, of Oracle Data Guard Concepts and Administration 10g Release 2 document. Metalink bulletin 409013.1 and 11gR1 doc says that “A logical standby database cannot forward redo to another standby database” and specifies that Layer1 logical standby configuration is not supported.
A logical standby database cannot forward redo to another standby database
At the end, this means you're not able to keep a copy of L1 logical standby.
But you can have this:
P1 --> P2 (physical) --> L2 (logical)
L2 will be sync with primary (P1). In a case of disaster it will still be sync with new primary (P2). But you need to maintain its own additional indexes and materialized views.

Help with setting a 2nd Standby Database

Hi,
I have an active DataGuard 11gR2 with a physical standby actively running on Linux.
Now, I need to add a 2nd physical Standby database (for reads only) to this environment, can someone please point to a resource/document which discusses the steps which are involved?
Thanks much
-Sravan

Hello;
One option is to setup a Cascading Standby. I tested this last spring and I'm happy to share my setup notes.
www.visi.com/~mseberg/Data_Guard_Cascading_Standby_Setup_and_Test.pdf
Also worth noting if you have Active Data Guard you don't need a second Standby, ( license for active Data Guard required ).
Best Regards
mseberg
Edited by: mseberg on Nov 22, 2011 7:09 AM
For additional information see :
Data Guard Concepts and Administration
12.1.3 Configuring Both Physical and Logical Standby Databases ( Oracle document B14239-05 )
In this case you could use the Logical Standby as you "Reader" database.

Create multiple standby databases of primary database

Hi,
I have to create 2 standby databases of a single primary database,
where can i get the stpe for the same?
Thanks

user10745179 wrote:
What about FAL_CLIENT parameters in primary?
how to set the values of the above parameter in priamry for second standby database.?
Thanks,In your case do need setting FAL_CLIENT/SERVER in primary database,set these parameter correctly in your standby database.Refer below note
*FAL_SERVER And FAL_CLIENT Settings For Cascaded Standby [ID 358767.1]*

Cascading standby

Similar Messages

Maybe you are looking for