Redo apply Vs real time apply

Hi all ;
I have some confusion regarding  redo apply Vs real time apply.
When applying redo data  in standby site , how do we find whether it was done by redo apply or real time apply ?
Please discuss in detail. I need some clarification about this.
Thanks in advance ..

Hi baris ,
Thanks .. again little confusion. NO documents to find answer.
If a logical corruption occurs on your primary by a human mistake such as truncate table, wrong delete etc,
so a delayed standby is more appropriate. Furthermore you can configure flashback database feature
on your standby database when you use real time apply.
Is this possible ?
1) Do you mean flashback will be enabled only in standby database except primary database ?
What are the changes  made in primary that only transfer to standby  if so ,
2) How do we recover deleted objects in standby ?
FYI : I have a  doubt with time delay option, we will discuss this things in new thread. please do NOT mind it.

Similar Messages

  • Data Guard: redo apply vs. real-time apply?

    Hi all-
    Anyone know what the difference is between redo apply (i.e., ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;) and realtime apply (i.e., ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;)? I'm using maximum protection mode (log_archive_dest includes LGWR SYNC AFFIRM), and I'm not seeing any difference between redo apply and realtime apply. In either case, if I update the primary, the transaction gets recorded in both primary and standby online redo logs. Any thoughts?
    Thanks!
    Rob

    Thanks... it appears, however, that max availability and max protection are not (necessarily) determined by which of the ALTER DATABASE RECOVER... commands (above) are specified:
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> alter database recover managed standby database using current logfile disconnect;
    Database altered.
    SQL> select protection_mode, protection_level from v$database;
    PROTECTION_MODE PROTECTION_LEVEL
    MAXIMUM PROTECTION MAXIMUM PROTECTION
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> alter database recover managed standby database disconnect;
    Database altered.
    SQL> select protection_mode, protection_level from v$database;
    PROTECTION_MODE PROTECTION_LEVEL
    MAXIMUM PROTECTION MAXIMUM PROTECTION
    SQL>
    I specified the protection level from the primary when I first set data guard up, with "alter database set standby database to maximize protection," so maybe the two commands are synonymous but there for backward compatibility?
    Rob

  • 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 = enable

    There 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.

  • 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.

  • 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

  • Logical standby real time apply problem

    Hi all,
    The real time apply for logical standby on my Oracle 10.2 DB is not working
    SELECT SEQUENCE#, FIRST_TIME, APPLIED
    FROM DBA_LOGSTDBY_LOG
    ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TI APPLIED
    2113 07/10/09 NO
    2115 07/10/09 NO
    2116 07/10/09 NO
    There is no error inside alert log.
    Any help
    Thanks

    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

  • 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

  • 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

  • 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

  • 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 to identify that my physical standby database in use real time apply?

    Hi,
    Can any one give me the SQL to identifiy that my physical standby database is in real time applying redo logs?
    Its urgen please....
    Thanks.

    You could just look at the alert log. Look for "Recovery of Online Redo Log"
    Or you could select from v$standby_apply_snapshot to see if the standby is up-to-date.
    select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
    to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
    to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;

  • 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

  • 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.

Maybe you are looking for

  • Cant download itunes, because ' there is an error with windows installer package' please help?

    cant download itunes, because ' there is an error with windows installer package' please help?

  • Tables and field names

    hiiii,right now we are developing dash boards for manufacturing industry,and we are trying to get the actual table names  and field names that where exactly these will appear ex.long term assets,cogs invoiced ,in which table it apperas.wht is grr3 an

  • Park invoices

    Hi there, Some weird thing is happening when posting park invoices... Standard WF 00400004 has the triggering event CREATED from BO FIPP activated, and when I test it running SWUE, everything goes ok, and the WF starts. But when posting a park invoic

  • Delete a vip mailbox

    I deleted an email in a vip mailbox before deselecting the star so the vip mailbox remains in the Mail sidebar. Is there a way to delete this vip mailbox in the Mail application sidebar? I followed the support instructions Lion Mail: Delete mailboxes

  • Help importing JPEGS

    Since upgrading to Lightroom 5.6 the JPEG files in folders will not import, only RAW files. Are there adjustments I need to make in Lightroom so that JPEGS will import?