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

Similar Messages

Can we patch Applications(ADPATCH) with no downtime using physical standby

Hi ,
As I know I can user Physical standby database for upgrade database with minimal downtime . Can I use the same with patching Oracle application using adpatch.
In other words can we patch Application (using Adpatch) with no downtime using physical standby .
Thanks in advance .
Best Regards,

In other words can we patch Application (using Adpatch) with no downtime using physical standby . No.
Business Continuity for Oracle Applications Release 11i, Database Releases 9i and 10g [ID 216212.1] -- Section 4: Applying an Applications Patch
Business Continuity for Oracle Applications Release 12 on Database Release 10gR2 - Single Instance and RAC [ID 452056.1] -- Procedure 4.4 - E-Business Suite Patch Application
Business Continuity for Oracle E-Business Release 12 Using Oracle 11g Physical Standby Database [ID 1070033.1] -- Section 7: Oracle E-Business Suite Maintenance with Standby Database
Thanks,
Hussein

How Real Time Apply works while physical standby is open in Read Only mode

Hi,
With Active data guard option, we can open physical standby DB in read only mode, while redo log are being applied. (Real Time Query)
Standby Redo log (SRL) enables Real Time Apply (with "USING CURRENT LOGFILE" clause in recover database command on standby DB)
I am interested to know, how Real Time Query works ?
What is the mechanism with allows us to open physical standby DB in read only mode while redo logs are being applied continuously ?
Regards,
Sujit

Dear user7419391,
That is a new feature in Oracle Database 11g. MRP can use the real time apply in 10g but the concept here is different.
Taken from the following document;
http://www.ascent.co.za/documents/oracle/Oracle%20databse%2011g%20Active-Data-Guard%20datasheet.pdf
*Unique Advantages of Oracle Active Data Guard*
+Active Data Guard is an evolution of Data Guard technology, providing unique+
+performance advantages while leveraging all other enhancements included in Oracle+
+Data Guard 11g. For example, any Data Guard 11g physical standby database can+
+be easily converted to a Snapshot Standby. A Snapshot Standby is open read-write+
+and is ideally suited as a test system, able to process transactions independent of the+
+primary database. A Snapshot Standby maintains protection by continuing to receive+
+data from the production database, archiving it for later use. When tests are+
+complete, a single command discards changes made while open read-write and+
+quickly resynchronizes the standby database with the primary.+
The other link in the previous post is excellent and you really have to read it to understand the active data guard aspects.
Regards.
Ogan

Standby Redolog Creation for Physical standby

I want to migrate my primary database from one server X to standby database which i want to create on other server Y. once Primary and standby will get SYNC , i will do Fail over to make standby as primary and divert current application on standby considering as full functional Primary.
Is it mandatory to create SRL ( Standby redo log)? or I can create physical standby without SRL? If Yes, on which side (primary or standby) i need to create SRL?
Appreciate your help..

Hello,
Now, My standby database has configured. Since i had restore and recover standby database from standby controlfile instead of RMAN Duplicate. I had done following step:
ON standby side:
$rman target /
RMAN> restore standby controlfile from '/app/oracle/standbyctl.ctl'
RMAN> sql 'alter database mount standby database';
RMAN> restore database;
RMAN> list backup of archive log all;
RMAN> RMAN> recover database until sequence 1670;
SQL> alter database recover managed standby database disconnect from session;
• On Primary:
SQL> alter system set log_archive_dest_state_2=ENABLE;
• On Standby:
SQL> select sequence#,applied from v$archived_log order by sequence#;
I am at this stage now. My primary and standby database in synchronization. As per my first thread above, we will have planned outage to move application to standby database and make it full functional primary database. once application will move on new server( standby database). we will not use current primary database anymore.
what are the procedure i need to do on primary side and standby side when migrate application on new server.? rightnow my standby database in MOUNT mode and archive log is shipping from primary to standby. we have no dataguard broker configuration. i need to do it manually using SQL command.

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

Problem in recover physical standby database(Data Guard) by rman

Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS
would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PM

hi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks

Data Guard - MRP stuck issues on a physical standby database

Hi,
Oracle 11.2.0.3 DG running. When i do a switchover the physical standby database has error with following error
ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance <primaryDB> - Archival Error
On standby DB
SQL>select process, thread#, sequence#, status from v$managed_standby where process='MRP0';
PROCESS THREAD# SEQUENCE# STATUS
MRP0 1 548 APPLYING_LOG
So according to Oracle support link i executed following
SQL>recover managed standby database cancel;
SQL>recover automatic standby database;
The above seems to resolve the issue. What is causing is this?

Hello again;
Those both look perfect. I combed through my notes and found nothing like this for your version.
Yes, I would open an SR since it appears you have done everything correct.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1]
The "Known Bugs" section of the above has a few 11.2.0.3 entries.
Generally the MRP gets stuck because data Guard thinks there's a GAP, you run out of room in the FRA on the Standby, or redo logs are too small and the system is switching very fast.
Best Regards
mseberg
Later
Never asked you but this "log_archive_max_processes" can be set as high as 30.
Edited by: mseberg on Jul 16, 2012 8:01 PM
h2. Still later
Found this which is closer :
Bug 13553883 - Archiver stuck but no ORA-19xxx error in alert log (messages need changing) [ID 13553883.8]

Applying patches to physical standby node(Data Guard 10.2.0.3)

Hello,
I have a data guard 10.2.0.3 environment (1 primary and 1 physical standby on a separate node) on solaris 10 and i want to document the procedure in applying patches to this environment.
I saw the article in Metalink Note 278641.1 which describes the procedure in applying a patchset to both nodes. It looks like both nodes need to be down before applying the oracle patchset.
Can we not apply the patches on only the standby while the primary stays up and running? My guess is you can't if the patches are significant i.e. it changes versions of the oracle binaries. But i want to confirm this.
Also, if we are applying solaris patches, i.e. nothing related to Oracle, we should be able to just apply them to the standby while keeping the primary up and running right?
The following has worked so far but i wanted to find some documentation that confirms it's ok.
1. shutdown oracle on standby node.
2. apply solaris patches...
3. restart oracle on standby node and put in managed recovery mode.
Any comments are appreciated.
Thanks.

Hi
Did you get an answer for your question yet? I have the same problem with one of our databases. Would be very nice, if you could tell me.
Regards
Felix

Data Guard Archive Latency with Physical Standby

I'm trying to get a latency number that tells me how long it took ARCH to move an archive file from the Primary instance to the physical standby instance and "apply it". I see lots of numbers but I can't make heads or tails of them. Does a metric such as this exist in a log file, a V$ view, or can it possibly be calculated or extrapolated?
Thanks
Steve ([email protected])

This is how calculated the same in a test env.
1. stop standby listener
2. shutdown standby
3. perform a data load (import)
4. start the standby listener. This will cause arch files to be shipped to the standby. Monitor the files being shipped and time it
5. start the standby db in recovery mode
6. repeatedly execute the following query while timing the log apply services:
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

Data Guard Archive Log Latency Between Primary and Physical Standby

How can I get the time it takes (latency) for the primary instance to get an archive log over to the physical standby instance and get it "archived" and "applied". I have been looking at the V$ARCHIVED_LOG view on each side but the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY" and no timestamp. I thought the DATE datatype include data and time. Any ideas on how I can get the latency info I'm looking for?
Thanks
Steve

the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY"
and no timestamp. Did you try using TO_CHAR ? e.g.
to_char(completion_time,'dd/mm/yyyy hh24:mi:ss')

About Data Guard - Physical Standby Database

Dear All,
I have read many documents regading Data Guard.
I am about to setup Data Guard in our current environment but want to clear few tings.
I have a confusion between physical and logical standby database.
What I have read from different documents is:
-Physical Standby Database in (11g)
1) It is the most efFicient
2) I can be either in mount or open state
3) Select queries and reporting can be done to improve performance of the primary database.
4) Schema on primary and standby database is always the same
-- Logical Standby Database
1) You can create additional tables, indexes, etc.
2) Always in open mode
3) Select queries and reporting can be done to improve performance of the primary database
Now our scenerio is, that we have one server at the moment, OS is linux and operating system is 11g. We want to setup an other server in another country, will also be 11g on Linux in a way that it acts as standby/backup server. Schema and data is always the same. In case due to unavailability of primary server, standby server acts as the primary server (This has to be automated). The reason for unavailability could be any like maintenance work on primary server, network or hardware failure at primary server. The last and the most important thing is that users from this country where we will setup standby database will insert/update data on the primary server BUT queries and reporting will be done from this newly created standby data.
Kindly recomend the best Data Guard in this scenerio and kindly correct me where I am wrong.
Thanks, Imran

A logical standby has various limitations on things like data types. It's also a much more complex architecture, which makes it more likely that something will break periodically and require attention. Applying redo to a physical standby is code that has been around forever and is as close to bullet-proof as you'll get. And you would generally prefer to fail over to a physical standby-- if you do things like create new objects in the logical standby, you may have to get rid of those objects during a failover to get acceptable OLTP performance.
Justin

Data Guard Physical Standby Failover

I need clarification on Physical Standby Failovers. Say I have a Primary db (A) and a physical standby (B), (A) fails and (B) is now the primary, can (A) be setup to become a standby of (B)? I've read 2 different statements in Oracle 10g Data Guard Concepts and Admin
"During failovers involving a physical standby database: In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration."
vice
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
Much thanks.

In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration.
TRUE ! But this doesn't mean that you cannot make your failed primary a new standby database !.
You can achieve this using FLASHBACK DATABASE option:
From the documentation:
After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.
Read the following documents:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#sthref995
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
In addition to this I'd like to mention that you can achieve the same with doing an incomplete recovery instead of using FLASHBACK DATABASE.
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
TRUE. If you enable Fast-Start Failover:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDFFEC
Cheers!

Can I configure capture process of streams on physical standby

we have high oltp system that has dataguard setup with physical and logical. We are planning to build a datawarehouse and have streams setup for data feeding into the datawarehouse. Instead of taxing the primary, i was wondering if i could set up the physical standby as the source for my streams (basically configure the capture process on physical standby).
Appreciate your help in advance!
Thanks

Thanks for the reply Tekicora
This means then On the primary, I will have another destination that I send the archives to (In addition to Physical) that will be my source database for streams where I can configure capture process. if this understanding is right, then i have the following questions
1) Can i use cascaded standby to relieve my primary from having another log destination and use that database for the source
2) Do you know if PSB can be used as source in 11g? because we are planning to move to 11g soon.
Thanks
Smitha

Can't create physical standby

I am running on a Sun Solaris Unix 64bit. Oracle is 10.2.0.3 when trying to create a physical standby I get the Data Guard screen and at the top an Error SQL Exception: Closed Connection.
Can anyone help me with this?

Seems to be some issue with setup configuration. Could you please tell how you have setup the env?

Difference between physical standby database and Data Guard

Hi guys,
Today I attended one interview. They asked me a difference between the Oracle Physical Standby database and Oracle Dataguard?
Upto my knowledge Oracle Physical Standby Database is one type of Standby Database can be configured using Oracle Databaguard Feature.
Can you people calrify me on this.
Regards,
Vijayaraghavan K

hello,
yes you are right upto some extent...here is para form oracle doc
Oracle Data Guard is the most effective and comprehensive
data availability, data protection, and disaster recovery solution
for enterprise databases. It provides the management, monitoring,
and automation software infrastructure to create and maintain one
or more synchronized standby databases to protect data from failures,
disasters, errors, and corruptions.
Data Guard standby databases can be located at remote disaster
recovery sites thousands of miles away from the production data center,
or they may be located in the same city, same campus,
or even in the same building. If the production database
becomes unavailable because of a planned or an unplanned outage,
Data Guard can switch any standby database to the production role,
thus minimizing downtime and preventing any data loss.oracle data guard is maximum availiblity solution which maintain physical standby databases and in case of failure of production can switch production role to and standby database.
read it here
http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html
thanks and regards
VD
Edited by: Dixit on Aug 31, 2009 1:35 AM
Edited by: Dixit on Aug 31, 2009 1:36 AM

Can a physical standby propagate data to a logical standby?

Similar Messages

Maybe you are looking for