Data Guard Transport and Real Time Apply Configuration

Hello,
I'm configuring a Data Guard configuration using Oracle 12.1.0.2 and I have observed that in a máximum perfomance configuration, that is the default.
The system upgrade to a SYNC configuration.
DGMGRL> show configuration
Configuration - DRSolution
Protection Mode: MaxPerformance
Members:
orcl - Primary database
    STBY - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS   (status updated 53 seconds ago)
SQL> show parameters log_archive_Dest_2
NAME                                 TYPE        VALUE
log_archive_dest_2                   string      service="stby", ASYNC NOAFFIRM
                                                  delay=0 optional compression=
                                                 disable max_failure=0 max_conn
                                                 ections=1 reopen=300 db_unique
                                                 _name="STBY" net_timeout=30, v
                                                 alid_for=(online_logfile,all_r
                                                 oles)
However, if I insert 1 row in a test table at primary database and commit, immediately I see the change in the standby database.
If this behavior new in this versión?
How can I revert to the classic max performance configuration, where only send the archive when it is full.
Thanks
Arturo

>How can I revert to the classic max performance configuration, where only send the archive when it is full.
That is ARCH shipping. The default in 11.2 and above LGWR shipping. So LGWR ships the redo immediately. The only thing with ASYNC is that it doesn't wait for the Standby to acknowledge before it returns a COMMIT to the user. In a low-load environment, if the standby can apply the redo fast enough, ASYNC is virtually the same as SYNC. That is MaximumPerformance becomes the same as MaximumAvailability. Only when the redo load is higher than the available bandwidth or the speed at which the Standby can apply it , will you see a lag in the Standby. (To force an explicit lag, there is a separate DELAY parameter).
ARCH shipping is deprecated.

Similar Messages

Enabling the Active Dataguard and Real Time Apply

11.2.0.2 on AIX
I gather that , to enable Active Dataguard, you need to execute
STARTUP ; ----not startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;The above commands will enable both Active Dataguard (Real Time QUERY) and Real Time Apply. Right?
To enable just 'Real Time Apply' , I need to
startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;Am I right ?
Question on 'WITH SESSION SHUTDOWN' clause
While googling I've come across the following variant with an additonal 'WITH SESSION SHUTDOWN' clause
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE WITH SESSION SHUTDOWN;What difference does this clause bring ?
Is this claused used to enable Active Dataguard feature or 'Real Time Apply' or both ?

I gather that , to enable Active Dataguard, you need to execute
STARTUP ; ----not startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
The above commands will enable both Active Dataguard (Real Time QUERY) and Real Time Apply. Right? Yes, It will be in both recovery / realtime + Read only mode, Also you can use
To enable just 'Real Time Apply' , I need to
startup mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;Am I right ?Yes. It will be in just recovery/real time mode.
Question on 'WITH SESSION SHUTDOWN' clause
While googling I've come across the following variant with an additonal 'WITH SESSION SHUTDOWN' clause
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE WITH SESSION SHUTDOWN;What difference does this clause bring ?
Is this claused used to enable Active Dataguard feature or 'Real Time Apply' or both ?It has multiple options based on startup type
For this example check link of Julian Dyke.
http://juliandyke.wordpress.com/2010/10/14/oracle-11gr2-active-data-guard/

11gr2 Dataguard Active Standby - Unable to get Real-Time apply working

As above, I am unable to get real time apply to work WITHOUT it switching my standby back to MOUNT state. There does not seem to be anyting obvious from the broker, or alert logs.
On the Standby:
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database open read only;
Database altered.
SQL> select open_mode from v$database;
OPEN_MODE
READ ONLY
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
SQL> select open_mode from v$database;
OPEN_MODE
MOUNTED
Primary:-
SQL> SELECT status, recovery_mode FROM v$archive_dest_status where dest_name = 'LOG_ARCHIVE_DEST_2';
STATUS RECOVERY_MODE
VALID MANAGED REAL TIME APPLY
Edited by: Imran on Apr 17, 2012 10:56 PM

Hello;
This is expected.
Works the same exact way on my system. How Redo Data is applied is set when the database is MOUNTED.
See - 6 Redo Apply Services
Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-0
The document is vague on this at best, but think about the error you get if you try to start apply twice.
Data Guard Real-Time Apply FAQ [ID 828274.1]
Best Regards
mseberg
Edited by: mseberg on Apr 17, 2012 10:04 AM
h1. Test
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
SQL> select open_mode from v$database;
OPEN_MODE
READ ONLY WITH APPLY
SQL> So I get different results ??
Edited by: mseberg on Apr 17, 2012 10:40 AM
h2. Still more
I would like to change my answer. Based on my test and queries as shown below I believe REAL TIME apply is working. Note the last log says NO because its in progress.
Checking last sequence in v$archived_log
STANDBY               SEQUENCE# APPLIED    COMPLETIO
STANDBY                     343 YES        16-APR-12
STANDBY                     344 YES        16-APR-12
STANDBY                     345 YES        16-APR-12
STANDBY                     346 YES        16-APR-12
STANDBY                     347 YES        17-APR-12
STANDBY                     348 NO         17-APR-12
6 rows selected.
----------------Last log on Primary--------------------------------------|
MAX(SEQUENCE#)
           348
1 row selected.Yes, I doubled check and it works on mine. I guess I read what I wanted to read.
All my Standby redo are setup correctly ( size and numbers )
READ ONLY WITH APPLYYour answer my be the Uwe answer at the end of this thread :
Enabling the Active Dataguard and Real Time Apply
Best Regards
mseberg
Edited by: mseberg on Apr 17, 2012 10:50 AM

Real time apply

Hello
Oracle 10.2.0.1
I have dataguard configuration with standby file management auto and real time apply
SQL> SELECT DEST_ID, RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS
where dest_id=2;
DEST_ID RECOVERY_MODE
2 MANAGED REAL TIME APPLY1-) I create a table in primary database
2-) I cancel recovery in standy database (recover managed standby database cancel;)
3-) I open standby database in read only
Since real time apply is enabled why I cannot see my new created table in standby database?

Khurram;
When I change the protection mode, I got the below alerts, therefore I couldnt open the database:
LGWR: Primary database is in MAXIMUM PROTECTION mode
LGWR: Destination LOG_ARCHIVE_DEST_2 is not serviced by LGWR
LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
LGWR: Minimum of 1 LGWR standby database required
Mon Sep 28 20:19:15 2009
Errors in file /oracle/u01/admin/orclprod/bdump/orclprod_lgwr_29882.trc:
ORA-16072: a minimum of one standby database destination is required
Mon Sep 28 20:19:15 2009
Errors in file /oracle/u01/admin/orclprod/bdump/orclprod_lgwr_29882.trc:
ORA-16072: a minimum of one standby database destination is required
LGWR: terminating instance due to error 16072
Instance terminated by LGWR, pid = 29882

Data guard real time apply vs archived log apply on physical standby

Dear DBA's,
last week i configuared DR , now the phyiscal stanby database is archive apply mode,
i want to confirm is it better to apply the archived log or should i cahnge it to real time apply .
give me sugesstions.
Thanks and Regards
Raja...

One question are you using ARCH transport to move the redo? or have you configured standby redo logs and logwr transport (either async or syncronous), if you are using the archiver to transport the logs then you can not use real time apply.
If you are using log writer to transpor the redo the realtime apply reduces the recovery time required if you need to failover as trher should be less redo to apply to bring the standby up to date, which mode you use to transport redo will depend on what is acceptable in terms of data loss and the impact on performance.

RMAN in active data guard with real time apply ON without a catalog DB

I would like to know whether I can take RMAN backups (both level 0 & incremental) in active data guard with real time apply ON without a catalog database. version is 11.2.0.3.2. Will it make difference in the control file of standby syncing with primary? Can I use these backups on primary to restore and recover the database(including control file backup)?

Thank you very much msberg. Could you please answer the below queries as well?
Should I cancel Real Time Apply before starting RMAN?
Will it make difference in the control file of standby syncing with primary? Is it possible to use these backups on primary to restore and recover the database(including control file backup)? If possible, how will I do that?

Starting a Physical Standby DB which is configured with real-time apply

Hi,
I wanted to get clarification on the correct procedure for starting and stopping a physical standby database. The Dataguard documentation states the following:
1. Start and mount the database:
SQL> STARTUP MOUNT;
2. Start log apply services:
To start Redo Apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> DISCONNECT FROM SESSION;
To start real-time apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
My configuration is using real-time apply based on the information provided by the RECOVERY_MODE column of the V$ARCHIVED_DEST_STATUS view. Should I execute both ALTER statements or just the second one. If only the second one, how will the database re-synchronize, especially after a long down time. Also, must I do anything on the primary database prior to starting up the physical standby?
I'm using Oracle 10g SP1 on a linux server.

No. But you can recover until the last arch file generated on the primary, then you cancel the recovery and then use query#2 to start applying real-time. Refer to Note:343424.1 on Metalink.

How can I make Recover_Mode Is Real Time Apply in Data Duard

Hi Experts
I have Primary and Standby Databases I need to know how can I change the recover mode to Real Time Apply?
I run the following queury in Primary Site:
SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS WHERE DEST_ID=2;
RECOVERY_MODE
MANAGED
I have oracle 11g R2 / Windows Server 2008 R2!
Logs generated and transfered successfully!

Hello;
Cancel recovery on the standby and then.
SQL
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
Note: You should have Standby redo at both the Primary and Standby sites.
Best Regards
mseberg

11gR2 Real Time Apply / open read only

Hi,
I have a single instance primary database with a physical standby. The release is 11.2.0.1.0.
Max Availability mode
LGWR SYNC transport
Data Guard Broker configuration enabled
Both the primary and standby database are registered with the Grid Infrastructure (Standalone installation on each server, no cluster)
When I stop and start the standby database it seems to default to open read only using Managed Real Time Recovery.
SQL> SELECT DEST_ID, RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS
2> WHERE DEST_ID=2;
DEST_ID RECOVERY_MODE
2 MANAGED REAL TIME APPLY
I do not want to Active Data Guard on this particular database. So I removed and added the database again using srvctl this time supplying the -s mount flag. Now when I stop/start the standby it opens in mount mode and MANAGED recovery which is OK.
My question is why did the standby automatically get opened in read only. Is the a change in behaviour introduced along with Active Data Guard? Is the default behaviour for a database registered with Grid Infrastructure to simply start the database in open mode and becuase this is 11.2 standby this means open read only?
Thanks

Dear user234564,
This has been introduced in Oracle Database 11g Data Guard New Features and it is called the Active Data Guard. With the new release you can open the physical standby database in read only mode and the real time apply will continue as it is on the mount stage. This ability has not been granted on 10g. So i think it could be the normal behaviour.
11g physical standby database will be opened and the MRP process will still apply the archivelogs to the standby database. You can simply have it tested.
Please refer;
http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/manage_ps.htm#CHDGJEFF
Let me give you a quick hint but it is off topic;
The number of standby databases that a primary database can support is increased from 9 to 30 in this release.
The capability to create 30 standby databases, combined with the functionality of the Oracle Active Data Guard option, allows the creation of reader farms that can be used to offload large scale read-only workloads from a production database.Hope That Helps.
Ogan

Real-time apply in Maximum Performance Mode Not Working

We have configured physical standby database in maximum performance mode. It's working perfectly fine. Archive logs are being applied to the physical standby.
We can open the DB in read-only mode, but real-time apply is not working. Physical standby database is lagging behind the primary db by an archive log. As soon as primary database generates an archive log, it's transported over to the standby and applied immediately by the media recovery process. But real-time redo is not working. Standby redo logs have been configured.
On Physcial Standby:
SQL> alter database recover managed standby database using current logfile disconnect ;
Database Altered.
SQL> select group#, DBID, status,first_time, last_time from v$standby_log ;
GROUP# DBID STATUS FIRST_TIM LAST_TIME
4 UNASSIGNED UNASSIGNED
5 UNASSIGNED UNASSIGNED
6 UNASSIGNED UNASSIGNED
7 UNASSIGNED UNASSIGNED
SQL> select * from v$dataguard_stats ;
NAME
VALUE
UNIT TIME_COMPUTED
apply lag
+00 00:31:36
day(2) to second(0) interval 22-JUN-2010 08:42:06
transport lag
+00 00:31:34
day(2) to second(0) interval 22-JUN-2010 08:42:06
As you could see from the output above, value of transport and apply lag is equal to the elapsed time since last archive log switch.
********* Standby init.ora
db_name = CPRD
db_unique_name = CPRDS
instance_name = CPRD
service_names = hrDBSBY.WORLD
log_archive_format = CPRD%r%s.%t
log_archive_dest_1 = "location=f:\orarch\hresysprod"
log_archive_dest_2='service=hresysprod async db_unique_name=cprd valid_for=(primary_role,online_logfile)'
log_archive_config='dg_config=(cprd,cprds)'
fal_server=hresysprod
fal_client=hresysprods
standby_file_management=auto
log_archive_trace=1
log_file_name_convert = ('hresysprod','hresysprods')
db_file_name_convert = ('hresysprod','hresysprods')
remote_login_passwordfile = exclusive
******* Primary init.ora
log_archive_config='dg_config=(cprd,cprds)'
fal_server=hresysprods
fal_client=hresysprod
standby_file_management=auto
log_archive_format = CPRD%r%s.%t
log_archive_dest_1 = "location=f:\orarch\hrESYSPROD"
log_archive_dest_2='service=hresysprods async db_unique_name=cprds valid_for=(primary_role,online_logfile)'
log_archive_trace=1
remote_login_passwordfile = exclusive
Please advise.
Thanks,
jay

Hi,
In your case you are using ARC process for redo transfer as you have not specified any process in log_archive_dest_2 and default is arch.
I will suggest you to use LGWR to transfer the redo to standby and also check the size of standby redo logs on standby is same to the size of online redo logs on primary
Regards
Anudeep

Real time apply for logical standby

Hi
Oracle 11.2.0.3.0
I have a primary database orcl and logical standby database orcl_std.
Real time apply is enabled. I have standby redologs in both primary and standby sides and I`ve started recovery with below command:
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
When I create a new table in primary database, I am unable to see it on standby database (Although real time apply is enabled)
However, when I switch log in primary, I can see the new table in standby database.
My question is, why realtime apply is not working in my scenerio ? I was expecting to see the new table immediately in standby database once it is created in primary database. Why am I supposed to wait for log switch in real time apply ?

Using Real-Time Apply to Apply Redo Data Immediately
http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_apply.htm#i1022881
1.What is compatible parameter, it should be 11.1
2.Try to check parameters mentioned in below link:
http://easyoradba.com/2011/01/10/real-time-apply-in-oracle-data-guard-10g/
Regards
Girish Sharma
Edited by: Girish Sharma on Nov 15, 2012 12:37 PM

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

Gap resolution is not always happening with real time apply

Hi
I noticed a strange behavior in one of my 10.2.0.4 dataguards , and I am wondering if anyone else has encountered it :
When there is an archive gap that need to be resolved , the gap is NOT always being identified and acted upon , when the recovery is started as such :
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION.
its just sitting there doing nothing, and nothing is written to the alert log regarding the gap and nothing is being transferred from the primary as needed.
However, if I restart the apply , omitting the 'USING CURRENT LOGFILE' clause , the gap is identified and acted upon, as such :
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION.
At first I thought its merely due to me stopping and starting the apply process ( nothing like a "reboot" , right ? ) , but that is not the case.
if I restart , but still use the USING CURRENT LOGFILE clause , the gap is still not being identified .
Anyone had this issue ? any theories as to why that happens ?

Using Real-Time Apply to Apply Redo Data Immediately
http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_apply.htm#i1022881
1.What is compatible parameter, it should be 11.1
2.Try to check parameters mentioned in below link:
http://easyoradba.com/2011/01/10/real-time-apply-in-oracle-data-guard-10g/
Regards
Girish Sharma
Edited by: Girish Sharma on Nov 15, 2012 12:37 PM

Recovery_mode managed vs managed real time apply

Hello All,
I am using Oracle 11.2.0.3
My primary database is an Oracle RAC 2 nodes database with ASM and my standby database is a single instance physical standby database on file systems.
My protection mode is MAXIMUM PERFORMANCE
What is the difference I do :
alter database recover managed standby database using current logfile disconnect; (managed real time apply)
and
alter database recover managed standby database disconnect; (managed)
Does managed real time apply have any performance impact or disadvantage?
Regards,

Does managed real time apply have any performance impact or disadvantage?
Performance i don't think will not be..
For the rest of the queries you have to deside what is real use of it..? I will so you path of pros and cons of it
Difference between real time apply and active dataguard
What are the pros and cons using Active Data Guard vs Data Guard?
redo apply Vs real time apply

Behaviour of v$standby_log; during real time apply...

hi,
i would like to understand the behaviour of this view, during REDO APPLY or real time apply using standby redo log configuration. as in my db, when there is a apply in progress i see the status column having value ACTIVE and DBID column has value of standby DBID where the apply is in progress and then status column goes to UNASSIGNED value and DBID column has no value inside it....i mean blank......why is this so? request you to please help me to understand this....following is the log
SQL> select * from v$standby_log;
GROUP# DBID THREAD# SEQUENCE# BYTES BLOCKSIZE USED ARC STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME LAST_CHANGE# LAST_TIME
7 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
8 3903727333 1 58534 104857600 512 338944 YES ACTIVE 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12
9 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
10 3903727333 2 38929 104857600 512 235008 YES ACTIVE 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12
11 UNASSIGNED 2 0 104857600 512 0 NO UNASSIGNED
12 UNASSIGNED 2 0 104857600 512 0 NO UNASSIGNED
6 rows selected.
SQL> /
GROUP# DBID THREAD# SEQUENCE# BYTES BLOCKSIZE USED ARC STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME LAST_CHANGE# LAST_TIME
7 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
8 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
9 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
10 UNASSIGNED 2 0 104857600 512 0 NO UNASSIGNED
11 UNASSIGNED 2 0 104857600 512 0 NO UNASSIGNED
12 3903727333 2 38931 104857600 512 5120 YES ACTIVE 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12

GROUP# DBID THREAD# SEQUENCE# BYTES BLOCKSIZE USED ARC STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
7 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
8 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
9 UNASSIGNED 1 0 104857600 512 0 NO UNASSIGNED
10 UNASSIGNED 2 0 104857600 512 0 NO UNASSIGNED
11 UNASSIGNED 2 0 104857600 512 0 NO UNASSIGNED
12 3903727333 2 38931 104857600 512 5120 YES ACTIVE 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12 2.3217E+10 05-JAN-12Here DBID would be same,
These standby redo log file groups can contain either of thread 1 or thread2, Multiple threads are used in RAC environment.
In general architecture, Once if any log switch (or) redo log is full then these will be dumped into archive log files, then it will assigned to new redo log files. Here in primary redo log file, you can see the status as Current, Active, Inactive so on.
During real time apply, whenever data written into primary redo log files, At the same time log writer will be active and that will be assigned to the one of the redo log file..not redo log file, you have to say standby redo log in standby database.
here unassigned means, this standby redo log file, can be used for next time, might earlier status as "active". Whenever standby redo log file is active then only DBID you can see.
If its in unassigned it will be idle, again if any new allocation then these will become active. its like chain/loop. It is very much normal behaviour.
UNASSIGNED - Online redo log has never been written to. This is the state of a redo log that was just added, or just after a RESETLOGS when it is not the current redo log.
ACTIVE - Log is active but is not the current log. It is needed for failure recovery. It may be in use for block recovery. It may or may not be archived.
HTH.

Data Guard Transport and Real Time Apply Configuration

Similar Messages

Maybe you are looking for