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;

Similar Messages

  • How to check data in physical standby database?

    Hi!
    I'm maintaining physical standby database system. everyday, i must check tranfer and apply progress. I known, it operate very good. No archive gap is found.
    But i want to check data in physical standby database that there is consistant with primary database, there isn't? What method do I use? How to do?
    thankS

    I hope the following will help
    Verifying the Physical Standby Database
    ==========================================
    Once you create the physical standby database and set up log transport services, you may want verify that database modifications are being successfully shipped from the primary database to the standby database.
    To see the new archived redo logs that were received on the standby database, you should first identify the existing archived redo logs on the standby database, archive a few logs on the primary database, and then check the standby database again. The following steps show how to perform these tasks.
    Step 1 Identify the existing archived redo logs.
    On the standby database, query the V$ARCHIVED_LOG view to identify existing archived redo logs. For example:
    SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
    2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
    9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
    10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
    3 rows selected.
    Step 2 Archiving the current log.
    On the primary database, archive the current log using the following SQL statement:
    SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
    Step 3 Verify that the new archived redo log was received.
    On the standby database, query the V$ARCHIVED_LOG view to verify the redo log was received:
    SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
    2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
    9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
    10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
    11 11-JUL-02 17:51:03 11-JUL-02 18:34:11
    4 rows selected.
    The logs are now available for log apply services to apply redo data to the standby database.
    Step 4 Verify that the new archived redo log was applied.
    On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log was applied.
    SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    2 ORDER BY SEQUENCE#;
    SEQUENCE# APP
    8 YES
    9 YES
    10 YES
    11 YES
    4 rows selected.

  • How to open a "manual" Physical standby database in read/write mode

    Hi,
    I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
    I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
    The standby database is started this way :
    startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
    alter database mount standby database;
    Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
    The thing is, if I shutdown immediate the database, then do just startup :
    shutdown immediate;
    startup;
    The database opens with no error messages, but is still in read-only mode...
    I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
    Thanks,
    Mat

    Hello,
    There're features which allows you to open a Standby database in Read/Write mode but for all I know
    it needs Entreprise Edition.
    In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
    a way by using flashback database so as to rolling backward the database and avoiding to recreate
    the Standby.
    In Standard Edition I'm afraid that you'll have to recreate your Standby database.
    Best regards,
    Jean-Valentin

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

  • 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

  • How to stop and cancel physical standby database (ORACLE 10g)

    Dear All,
    I have physical standby setup and I want stopped for the time being that to use the database as an normal DB (standalone inestance).
    Kindly advise and show me how do I do that.
    Regards,

    executing below query on primary db stops log shipping to standby.......i think this is sufficient for disabling your physical standby setup temporary
    alter system set log_archive_dest_state_2=defer scope=both;
    In future if you want your dataguard setup back..............you can rebuild the standby and enable the log_archive_dest_state_2 parameter.
    Edited by: Veeresh.S on Nov 14, 2012 5:45 PM

  • Physical Standby Database (Protection Mode)?!!

    Hi,
    I have configured a physical standby database to use Real-time Apply, but i noticed that the protection mode of the database has been changed from "Maximum Performance" to ''Maximum Availability"..
    log_archive_dest_3='service=phystby OPTIONAL LGWR SYNC AFFIRM reopen=120 valid_for=(online_logfiles,primary_role) db_unique_name=phystby'
    Any body to explaine??
    Regards,

    LGWR SYNC AFFIRM
    These are the options are used in maximum protection  mode ,in which oracle will write the information in both the server(primary and standby) and this write occurs at same time.
    oracle write the information in online redo logfile of both the server simultaneously.
    and this option ensure no data loss will occurs if primary will fail.
    SYNC related with Network transmission mode.
    AFFIRM related with disk write option.
    LGWR describe Redo archival process.
    Thanks
    Kuljeet                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Redologs in physical standby database

    The MRP process is started and the standby database is physical standby, which is running under managed standby. My Question is as below
    1. Under managed recovery mode do we require the redo logs created on the physical standby database.
    2. How does oracle keep the database in sync when there are no redo logs are created on the standby database.

    The output is as below
    SQL> select status, pid, sequence# from v$managed_standby where process like 'MRP%';
    STATUS PID SEQUENCE#
    WAIT_FOR_GAP 29710 88576
    SQL>
    The contents of alertlog ; i Just restarted the managed recovery to capture the information
    RFS[1]: Archived Log: '/u02/archive/1_88817_665420030.dbf'
    Sun Apr 18 18:34:26 2010
    RFS[2]: No standby redo logfiles created
    RFS[2]: Archived Log: '/u02/archive/1_88818_665420030.dbf'
    Sun Apr 18 18:44:26 2010
    RFS[3]: No standby redo logfiles created
    RFS[3]: Archived Log: '/u02/archive/1_88819_665420030.dbf'
    Sun Apr 18 18:54:26 2010
    RFS[4]: No standby redo logfiles created
    RFS[4]: Archived Log: '/u02/archive/1_88820_665420030.dbf'
    Sun Apr 18 18:56:32 2010
    alter database recover managed standby database cancel
    Sun Apr 18 18:56:50 2010
    MRP0: Background Media Recovery cancelled with status 16037
    Sun Apr 18 18:56:50 2010
    Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_29710.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Recovery interrupted!
    Sun Apr 18 18:56:51 2010
    Waiting for MRP0 pid 29710 to terminate
    Sun Apr 18 18:56:51 2010
    Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_29710.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Sun Apr 18 18:56:51 2010
    MRP0: Background Media Recovery process shutdown (rmdp3)
    Sun Apr 18 18:56:52 2010
    Managed Standby Recovery Canceled (rmdp3)
    Completed: alter database recover managed standby database cancel
    Sun Apr 18 18:57:19 2010
    alter database recover managed standby database disconnect
    from session
    Sun Apr 18 18:57:19 2010
    Attempt to start background Managed Standby Recovery process (rmdp3)
    MRP0 started with pid=19, OS id=2123
    Sun Apr 18 18:57:19 2010
    MRP0: Background Managed Standby Recovery process started (rmdp3)
    Managed Standby Recovery not using Real Time Apply
    Sun Apr 18 18:57:24 2010
    Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Sun Apr 18 18:57:24 2010
    Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Clearing online redo logfile 1 /u03/redologs/rmdp3/redo01.log
    Clearing online log 1 of thread 1 sequence number 88818
    Sun Apr 18 18:57:24 2010
    Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Sun Apr 18 18:57:24 2010
    Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
    Clearing online redo logfile 1 complete
    Media Recovery Waiting for thread 1 sequence 88576
    Fetching gap sequence in thread 1, gap sequence 88576-88675
    FAL[client]: Error fetching gap sequence, no FAL server specified
    Sun Apr 18 18:57:25 2010
    Completed: alter database recover managed standby database disconnect
    from session
    Sun Apr 18 18:57:54 2010
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 88576-88675
    DBID 440735188 branch 665420030
    FAL[client]: All defined FAL servers have been attempted.
    Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
    parameter is defined to a value that is sufficiently large
    enough to maintain adequate log switch information to resolve
    archivelog gaps.
    Edited by: user11982297 on Apr 18, 2010 10:58 AM

  • Issue with physical standby database not in sync with primary

    Hi,
    I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
    SQL> select thread#,max(sequence#) from v$log_history group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 7
    PROCESS STATUS THREAD# SEQUENCE#
    ARCH CONNECTED 0 0
    ARCH CONNECTED 0 0
    RFS OPENING 1 12
    ALERT LOG :
    Tue Mar 20 07:31:32 2012
    alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:32 2012
    Attempt to start background Managed Standby Recovery process (PRIMARY)
    MRP0 started with pid=18, OS id=16370
    Tue Mar 20 07:31:32 2012
    MRP0: Background Managed Standby Recovery process started (PRIMARY)
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 8 processes
    Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
    Tue Mar 20 07:31:39 2012
    Completed: alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:54 2012
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 9677325080303
    Tue Mar 20 07:31:54 2012
    MRP0: Media Recovery Complete (PRIMARY)
    Tue Mar 20 07:31:55 2012
    MRP0: Background Media Recovery process shutdown (PRIMARY)
    Thanks,
    Rakesh

    HI CKPT,
    Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
    SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
    Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
    Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
    Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
    Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
    Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
    36 rows selected.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /oracle/STDBY/arch/
    Oldest online log sequence 13
    Next log sequence to archive 0
    Current log sequence 14
    SQL> ho ls -ltra /oracle/STDBY/arch/
    total 3754456
    drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
    -rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
    -rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
    -rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
    -rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
    -rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
    -rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
    -rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
    -rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
    -rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
    -rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
    -rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
    drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
    SQL>

  • Will logical standby database be replaced by physical standby database?

    Will logical standby database be deprecated or replaced by physical standby database because of Real Time Query?
    As far as I know, because of the emergence of Real Time Query, physiacl standby database is easier to work than logical standby database. There are so many restrictions on using logical standby database.
    Will logical standby database be deprecated in the future?
    Message was edited by:
    frank.qian

    Good question - you are right that with the advent of Real Time Query, physical standby databases can provide the 'reporting database' functionality that you used to have to use a logical standby database for.
    But remember that logical standby databases allow additional schema objects, like materialized views and indexes, that you can't have with a physical standby (for the reasons Hans mentions). For example, you could have a index-light primary database for OLTP style workload, and an index-heavy logical standby, with MVs and dimensions for reporting, DW, etc.
    For this reason I don't expect logical standby will become deprecated.

  • 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

  • Issue on physical standby database

    Hi
    I've a problem on standby database.
    I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
    I get following message in my alert log
    WARNING! Recovering data file 88 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
    how can I fix this now.
    We keep physical standby database 2 day behind, and apply logs manually.
    Physical standby database is maintained manually.
    Could someone help me in getting out of this problem.
    Oracle 9.2.0.7
    solaris

    Versus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
    From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
    6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
    In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
    Note:
    If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
    Specifying a Time Delay
    You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
    Canceling a Time Delay
    You can cancel a specified delay interval as follows:
    For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
    For logical standby databases, specify the following SQL statement:
    SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
    These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
    Section 12.8, "Using a Physical Standby Database with a Time Lag"
    Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement

  • Backups on Physical standby database?

    I am using dataguard and a physical standby database.How to assign backups on physical standby database to reduce the load on Primary database.
    environment: windows
    Database version:11.2.0.1.0
    What are the pro and cons on assigning RMAN backups jobs to physical standby database?

    Is it better to assign the RMAN backups on standby?i am using the RMAN catalog.Yes, Already mentioned to reduce contention on primary. You can register even standby.
    Do i need to change the setting to backup archive logs from standby database? If i won't backup the archive logs on Primary the FRA will be full and i can't access it ?You can include even archive logs with your database backup.
    How to assign the archive logs backups,full backup on standby database?Same script will work, Before that cancel MRP and after backup start MRP. That should be fine.
    Recently i tested backup from standby and restore, Please see below log.
    =================================================================================================
    Backup Scrpts:-
    =================================================================================================
    RMAN> run
    2> 3> ALLOCATE CHANNEL dev11 type disk;
    4> backup as compressed backupset
    5> format '/home/oracle/backup/DBF_FULLCOLD_BKP_%s'
    6> filesperset 30
    7> (database);
    backup current controlfile format
    8> 9> '/home/oracle/backup/CTL_FULLCOLD_BKP_%s';
    RELEASE CHANNEL dev1;
    RELEASE CHANNEL dev2;
    10> 11> 12> }
    using target database control file instead of recovery catalog
    allocated channel: dev11
    channel dev11: SID=1 device type=DISK
    Starting backup at 03-FEB-13
    Starting implicit crosscheck backup at 03-FEB-13
    Finished implicit crosscheck backup at 03-FEB-13
    Starting implicit crosscheck copy at 03-FEB-13
    Crosschecked 4 objects
    Finished implicit crosscheck copy at 03-FEB-13
    searching for all files in the recovery area
    channel dev11: starting compressed full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: starting compressed full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: finished piece 1 at 03-FEB-13
    piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_23 tag=TAG20130203T192535 comment=NONE
    channel dev11: backup set complete, elapsed time: 00:03:57
    channel dev11: starting compressed full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    including current control file in backup set
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: finished piece 1 at 03-FEB-13
    piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_24 tag=TAG20130203T192535 comment=NONE
    channel dev11: backup set complete, elapsed time: 00:00:02
    Finished backup at 03-FEB-13
    Starting backup at 03-FEB-13
    channel dev11: starting full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    including current control file in backup set
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: finished piece 1 at 03-FEB-13
    piece handle=/home/oracle/backup/CTL_FULLCOLD_BKP_25 tag=TAG20130203T192939 comment=NONE
    channel dev11: backup set complete, elapsed time: 00:00:03
    Finished backup at 03-FEB-13
    released channel: dev11
    =================================================================================================
    Backup Files:-
    =================================================================================================
    [oracle@oracle-stby backup]$ ls -ltr
    total 364572
    -rw-r----- 1 oracle oinstall 361684992 Feb  3 19:29 DBF_FULLCOLD_BKP_23
    -rw-r----- 1 oracle oinstall   1163264 Feb  3 19:29 DBF_FULLCOLD_BKP_24
    -rw-r----- 1 oracle oinstall  10092544 Feb  3 19:29 CTL_FULLCOLD_BKP_25
    [oracle@oracle-stby backup]$
    =================================================================================================
    Restore CONTROL FILE:-
    =================================================================================================
    RMAN> restore controlfile from '/home/oracle/backup/CTL_FULLCOLD_BKP_25';
    Starting restore at 03-FEB-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=/u02/app/oracle/oradata/orcl/control01.ctl
    output file name=/u02/app/oracle/flash_recovery_area/orcl/control02.ctl
    Finished restore at 03-FEB-13
    RMAN> sql 'alter database mount';
    sql statement: alter database mount
    released channel: ORA_DISK_1
    RMAN>
    =================================================================================================
    Restore Database:-
    =================================================================================================
    RMAN> restore database;
    Starting restore at 03-FEB-13
    Starting implicit crosscheck backup at 03-FEB-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    Crosschecked 2 objects
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
    Sun Feb 03 19:37:47 2013
    Checker run found 4 new persistent data failures
    Sun Feb 03 19:38:40 2013
    Full restore complete of datafile 3 /u01/app/oracle/oradata/orcl/undotbs01.dbf.  Elapsed time: 0:00:56
      checkpoint is 1595132
      last deallocation scn is 1519218
      channel ORA_DISK_1: piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_23 tag=TAG20130203T192535
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:07
    Finished restore at 03-FEB-13
    RMAN>
    =================================================================================================
    Open Database:-
    =================================================================================================
    SQL> alter database open resetlogs;
    Database altered.
    SQL> select open_mode,database_role from v$database;
    OPEN_MODE            DATABASE_ROLE
    READ WRITE           PRIMARY
    SQL>Edited by: CKPT on Feb 21, 2013 11:24 PM

  • Problem in switchover to physical standby database

    Hi All,
    I am doing switchover from primary to physical standby database. Physical standby is in 'managed recovery' mode using real time apply and is in mount mode. I executed alter database commit to switchover to physical standby with session shutdown command. Now i am waiting for standby mrp to exit after processing eor record, but it seems mrp was hanged.
    Below is the content from standby database:
    Recovery of Online Redo Log: Thread 1 Group 5 Seq 620 Reading mem 0
    Mem# 0: /oracle/app/oracle/dbrac/th1-redo5a.log
    Resetting standby activation ID 749049115 (0x2ca5951b)
    Media Recovery End-Of-Redo indicator encountered
    Media Recovery Continuing
    Media Recovery Waiting for thread 1 sequence 621
    Archived Log entry 14 added for thread 1 sequence 620 ID 0x2ca5951b dest 1:
    Need some help to resolve.
    Thanks
    Sandy.

    Hello;
    After after you issue ( successfully ) a :
    alter database commit to switchover to physical standby with session shutdownYou need to :
    Shutdown the former primary and mount as a standby databaseCheck out my step by step :
    http://www.visi.com/~mseberg/data_guard/Data_Guard_switchover.html
    Read everything ( all the steps ) before you proceed.
    Best Regards
    mseberg

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

Maybe you are looking for