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
Similar Messages
-
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 -
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 -
ORACLE 11G "real time apply" not work?????
we have a database original on ORACLE 10.2.0.4 and we upgrade it to 11.1.0.7.
after that we create standby database and tried to use "real time apply" feature.
Primary database can transfer log files to standby database and standby database also can apply logs. The problem is it can NOT work on "real time apply".
Ant ideal what wrong?
=== procedures ====== (standby database)
SQL> startup mount;
ORACLE instance started.
Total System Global Area 2087780352 bytes
Fixed Size 2161272 bytes
Variable Size 1795163528 bytes
Database Buffers 251658240 bytes
Redo Buffers 38797312 bytes
Database mounted.
SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
SQL> select PROTECTION_MODE, PROTECTION_LEVEL, DATABASE_ROLE, SWITCHOVER_STATUS, OPEN_MODE, GUARD_STATUS from v$database;
PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE SWITCHOVER_STATUS
OPEN_MODE GUARD_S
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PHYSICAL STANDBY NOT ALLOWED
MOUNTED NONE
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
ARCH CONNECTED
ARCH CONNECTED
RFS IDLE
MRP0 APPLYING_LOG
6 rows selected.
========== Primary database init.ora file setup =====
### for DG use
db_unique_name = DBPMY
log_archive_config='dg_config=(DBPMY,DBSBY)'
log_archive_dest_1='LOCATION=/Archive/DBPMY/arch/arch MANDATORY'
log_archive_dest_2='service=DBSBY valid_for=(online_logfiles,primary_role) db_unique_name=DBSBY LGWR ASYNC=20480 OPTIONAL REOPEN=15 NET_TIMEOUT=30'
*.log_archive_format='DBPMY_%r_%t_%s.arc'
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enableThere are a couple of things to look at.
1. Real time apply requires standby redo logs on the standby database. On the standby database run this query:
SELECT * FROM v$logfile where type = 'STANDBY';
if you get 0 rows back you'll need to create standby logfiles
The general guideline is to size them exactly like your redo logs but add one additional standby log to ensure it doesn't cause a bottleneck.
2. Get the size of your logfiles:
SELECT GROUP#, BYTES FROM V$LOG;
3. For example if you have 3 redo logs that are 50 MB in size, create 4 standby redo logs 50 MB each and don't multiplex them.
ALTER DATABASE ADD STANDBY LOGFILE ('/Archive/DBSBY/onlinelog/slog1.rdo') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE ('/Archive/DBSBY/onlinelog/slog2.rdo') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE ('/Archive/DBSBY/onlinelog/slog3.rdo') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE ('/Archive/DBSBY/onlinelog/slog4.rdo') SIZE 50M;
4. Cancel recovery on standby
recover managed standby database cancel;
5. Restart recovery using real time apply
recover managed standby database using current logfile disconnect;
6. To validate that real time is working you can check a few places.
-It will say in the database alert log on standby that it's using real time apply
OR
-Check primary
SELECT status, recovery_mode FROM v$archive_dest_status where dest_name = 'LOG_ARCHIVE_DEST_2';
If the recovery_mode is "MANAGED REAL TIME APPLY" then real time apply is working, if it's anything else then we'll need to check more things.
NOTE that if you are going to allow your current primary to switch roles and become a standby then you'll want to create standby redo logs on primary as well
Sometimes recovery gets "stuck" and simply resetting the destination parameters can resolve it:
alter system set log_archive_dest_2='service=DBSBY valid_for=(online_logfiles,primary_role) db_unique_name=DBSBY LGWR ASYNC=20480 OPTIONAL REOPEN=15 NET_TIMEOUT=30';
There are some other things we can check next but let's start with the easiest fixes first. -
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.
-
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?
ThanksDear 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 -
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 PMHello;
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 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,
jayHi,
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 cascaded logical standby database
Hi
I have a primary database orcl
Pysical standby database orcl_std
Cascaded logical standby database orcl_tri which receives archivelogs from orcl_std
Real time apply is enabled both in orcl_std (physical standby) and orcl_tri (logical standby)
When I create a table in primary orcl, I am unable to see it on orcl_tri (Although real time apply is enabled)
However, when I switch log in primary, I can see the new table on orcl_tri.
My question is, why realtime apply is not working in my scenerio ?
orcl_std : ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION USING CURRENT LOGFILE;
orcl_tri: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Oracle 11.2.0.3.0Hi mseberg,
Thanks for your reply.
There is no load or network issue as I`ve just created these databases for the experiement.
I have the same output from standby and primary databases.
SQL> select bytes/1024/1024 from v$standby_log;
BYTES/1024/1024
10
10
10I can see below output in standby alertlog
Fri Nov 16 08:39:51 2012
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
ALTER DATABASE START LOGICAL STANDBY APPLY (orcl)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Fri Nov 16 08:39:51 2012
LSP0 started with pid=37, OS id=16141
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 1953318, ResetLogScn 995548
LOGMINER: summary for session# = 1
LOGMINER: StartScn: 0 (0x0000.00000000)
LOGMINER: EndScn: 0 (0x0000.00000000)
LOGMINER: HighConsumedScn: 1955287 (0x0000.001dd5d7)
LOGMINER: session_flag: 0x1
LOGMINER: Read buffers: 16
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=30 OS id=16145 sid=49 started
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=39 OS id=16149 sid=44 started
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=40 OS id=16153 sid=50 started
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
LOGMINER: End mining logfiles during commit scan for session 1
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
LOGMINER: End mining logfile for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
Fri Nov 16 08:40:04 2012
LOGSTDBY Analyzer process AS00 started with server id=0 pid=41 OS id=16162
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS03 started with server id=3 pid=45 OS id=16175
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS04 started with server id=4 pid=46 OS id=16179
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS01 started with server id=1 pid=42 OS id=16167
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS05 started with server id=5 pid=47 OS id=16183
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS02 started with server id=2 pid=44 OS id=16171Do you think real-time apply wasnt setup properly ? -
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 -
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/ -
Hello
I have some doubts about real time apply.
If a transaction occurs in production, lgwr will automatically write this transaction to standby redologs in standby database.
Is this transaction applied to standby database immediately or wait for standby redolog switch and applied as soon as standby log is archived ?Thanks Uwe.
Eventhough you mentioned this before, I just want to ask last time to confirm:
Regarding real time apply;
When a transaction occurs in production, this transaction is not applied directly to standby database.
It is first transferred to standby redolog( by the log writer of primary) and from there to standby database immediately. (I dont know which background proces is responsible for this)
Is this right?By default, the archives are transferred(on completion) to standby database server using ARCH process and received by Remote File Server process (RFS) on standby database server. Optionally, you may choose to do the same using standby redo logs instead of archive log files (LGWR and LNS processes comes into picture). The standby redo logs are compulsory for real time apply regardless of protection mode.
If you're using SRL, then redo data is transferred to SRL and once the SRL is archived the changes are written to the database using Managed Recovery Process (MRP) and hence minimizes the data loss in case of failover and minimizes the time in case of switchover and failover.
If you're using Real Time Apply, then the standby redo log data is directly written to the database using LSP or MRP without waiting for SRL to be archived.
Regards,
S.K.
Edited by: Santosh Kumar on Sep 22, 2009 3:53 PM -
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,
SujitDear 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 -
When to use Real Time Apply for Logical standby..!!
Hello All,
I have been trying many ways to speed up the archival on primary and improve sql apply on logical standby, but still we are getting about 45-50 mins of delay between primary and logical standby.
We wanted to have our transactions applied on logical standby within couple minutes. Which i guess wont be possible in async mode.
That's why i am planning to implement Real Time apply between primary and logical standby.
Now since both our databases are too far away from each other (Primary is in US and logical is in India) would it be recommended to implement real time apply in such scenario? And if implemented would it affect Primary DB Performance?
Also if there might be some packet loss or network hitch would Primary will try again and keep logical DB in Sync with Primary?
Any help or suggestions would be great.
Thanks.yes, real time apply is recommended in your scenario.
however due to the geographical distance between your primary and standby; I would suggest to keep your standby in current mode - max performance ; ASYNC- itself. It would not affect the performace of the primary.
As long as you set the FAL parameters and configure tnsnames properly and ensure proper deletion policy for archivelog cleanup in primary ( so that it's not deleted before shipping if need be), you shouldn't find any problem with primary & standby synching.
Good Luck.
Cheers.
Maybe you are looking for
-
I am a new Mac user so this will be a basic question and real easy to answer. When using a PC in the past I would use Control C to copy and Control V to paste. How is that done on my Mac Book Pro?
-
After i update my iphone to iso6 but the maps app is working very bad.
after i update my iphone 4 s to ios 6, my apps maps is working very bad.
-
Mini display incompatible with older ADC-displays?
I have no problem connecting my 23" aluminum bezel display in my office to my new 13" MBP, but when I wanted to hook up my older model 20" Cinema Display (plastic grey bezel) at home, the display was not recognized. Does anybody know if this is indee
-
Instances stuck in running state--please help
Hi, We have a composite with all synchronous processes with synchronous calls. We have a lot of running instances in the EM console and when we check the audit trail and the flow of many instances, the flow is completed successfully but the instances
-
Download to file (.xls) problem
I am running my application in 2004s Environment. It is throwing ClassCastException with the below code. Class IWDModifiableBinaryType is deprecated. Is there any way i can get the same functionality. IWDAttributeInfo mAttInfo = wdContext.g