Archive apply to standby

Hai all,
I confihgured physical standby and it is working fine.. but before making a switch over, oracle recommends to run this query inorder to Make sure the standby database is current with redo application. On each database server, run this query to see the which logs have been sent / received and applied
select sequence#, applied,
to_char(first_time, ‘mm/dd/yy hh24:mi:ss’) first
from v$archived_log
order by first_time;
Now when I execute this query,
SEQUENCE# APP FIRST
6508 NO 07/16/08 00:49:17
6508 YES 07/16/08 00:49:17
6509 NO 07/16/08 00:55:54
6509 YES 07/16/08 00:55:54
What does this indicate ?..
Is this applied successfully to the standby site ?
Thanks
Kai

You know,
I like to run the following query to tell me where my standby is at:
select * from V$dataguard_stats
NAME                    VALUE                    UNIT TIME_COMPUTED
apply finish time     +00 00:00:00.2      day(2) to second(1) interval 16-JUL-2008 14:05:49
apply lag               +00 00:00:19          day(2) to second(0) interval 16-JUL-2008 14:05:49
estimated startup time          36               second     16-JUL-2008 14:05:49
standby has been open          N                         16-JUL-2008 14:05:49
transport lag               +00 00:00:04     day(2) to second(0) interval 16-JUL-2008 14:05:49
This gives you a good indication of upto what archived log you have applied.
jason.
http://jarneil.wordpress.com

Similar Messages

  • Archive apply issue for standby database in Standard Edition.

    We have setup standby database in Oracle standard edition. the archive log cannot be send by oracle automatically. So we manually send the archive over. But do not see the database apply the archive log file. What could be wrong and where should we check on it?
    We also used following when finishing the standby DB after running "recover standby database;" for a few archive log file:
    alter database recover managed standby database disconnect from session;
    ======================================================================================
    This is the status:
    SQL> select OPEN_MODE, SWITCHOVER# ,REMOTE_ARCHIVE ,ARCHIVELOG_CHANGE#,SWITCHOVER_STATUS, DATABASE_ROLE from v$database;
    OPEN_MODE SWITCHOVER# REMOTE_A ARCHIVELOG_CHANGE# SWITCHOVER_STATUS DATABASE_ROLE
    MOUNTED 495550636 ENABLED 1.2201E+13 SESSIONS ACTIVE PHYSICAL STANDBY

    The DB version is 10.2.0.5
    I can do this to apply at standby DB:
    SQL> set autorecovery on
    SQL> recover standby database;
    Then I tried to run this to leave the session:
    alter database recover managed standby database disconnect from session;
    Do not seen any apply.
    =============================
    Here is the last lines of alert log:
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Clearing online redo logfile 1 /u02/cntus/redolog/redo01a.log
    Clearing online log 1 of thread 1 sequence number 10158
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    Clearing online redo logfile 1 complete
    Media Recovery Waiting for thread 1 sequence 10166
    Thu Sep 06 15:08:35 EDT 2012
    Completed: alter database recover managed standby database disconnect from session
    ======
    We have the directory /u02/cntus/redolog and /u03/cntus/redolog. But nothing in there. Should we create redo for it? Is this a separate issue?
    Thanks!

  • RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
    Check the below queries.
    Primary:-
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    Standby:-
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
    HTH.

  • Redo log files are not applying to standby database

    Hi everyone!!
    I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
    My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database.  I run the following command on the standby database.
                SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
    The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
    1. How to resolve this issue ?
    2.Is it compulsory to have Primary database open ?
    3. I have created standby  control file by using  command
              SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
    So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should  I have different database name for both or existing one is correct ?
    Can anybody help me to come out from this stuck ?
    Thanks & Regards
    Tushar Lapani

    Thank you Girish. It solved  my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
    I did following scenario.
    1.  Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
    2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
    3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
    So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
    Thanks

  • Changing the archive destination in standby database?

    My DB is running on Oracle 9.2.0.6.0. I have data guard for my primary database.
    Now i wanted to change the archive destination only standby database. What is the process? Any response or any link is appreicated. Thanks

    The standby database wouldn't generate archivelogs until and unless it is opened (eg in a failover). So, although there is a definition for the log archive destination in the standby's init.ora / spfile, it is used only to read archivelogs shipped from the primary.
    If you are talking of the destination that the primary's archivelogs are shipped to on the standby, technically once the archivelogs are applied on the standby, they are not required and can be deleted. You would be able to configure this.

  • How to delete archive log on standby site

    hi
    i configured dataguard on 10g. could anyone suggest how to delete archived log on standby site..

    Hi,
    There is no automatic feature out-of-the-box but you have the following views:
    1) Shows archive logs transfered:
    select sequence#, first_time, next_time from v$archived_log order by sequence#;
    2) Shows archive logs applied:
    select sequence#, archived, applied from v$archived_log order by sequence#;
    If you see your archivelogs applied you can safely remove archive log files from your disk. It is your decision if you keep or delete them completely.

  • Online Redolog Archiving on Logical Standby Databases!!

    Hi,
    Can I safely stop archiving on logical standby database? It has been inherited from primary database at the time of creation, but I don't see any reason why to keep it enabled while it's consuming unnecessary disk space on our server!!
    Any body can give a valid reason to keep it enabled??
    Thanks

    hi
    u dont need archiving on standby database as standby database reads archive files that come from primary database.its simply wastage of resource.stand by database was created from primary by taking a full backup.and to apply the archive files in case of failure u need atleast 1 backup of stand by database .and i assume u wont go for taking backup of standby database.
    just worry about the archives of primary database.
    kanchan
    OCP ( 9i,10g)

  • Clearing out archivelogs from Flash_recovery_area after applied on Standby.

    I set up a standby database using data guard in 11g. I used the flash_recovery_area to store archivelogs, but really the true destination of all my archivelogs should and is my standby database. I didnn't have any other backup(s) setup yet. After few days, my database stopped because it ran out of space in flash_recovery_area. I had to add more space to db_recovery_dest_size just to get the database back up. Then I set the archivelog deletion policy in rman to delete archivelogs after applied on all standby.
    Is that all I need to do keep my flash_recovery_are clean enough to prevent from locking my database again, or is there something else I need to do? This is just a dev box, and I'm trying to stay away from setting up rman backup process with delete option.
    Thanks in advance,
    Kyle

    Kyle;
    Sorry because I'm not answering the question you asked. But I had the same problem with a similar setup.
    What I decided was to use RMAN to backup the primary and have the RMAN script remove archive after a week.
    On the standby I created an RMAN script to remove archive only.
    There's not much to it and at the end I add a seperate remove empty folder script.
    echo "Starting RMAN..."
    $ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalogdb> << EOF
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
    exit
    EOF
    echo `date`
    echo
    echo 'End of archive cleanup on STANDBY'
    mailx -s ${MAILHEADER} $MAILTO < /tmp/rmandbarchstandby.out
    . /u01/app/oracle/dba_tool/bin/rmemptyfolders.sh ${DBNAME}
    # End of Script

  • Best way of deleting archive logs on standby when backup taken on primary

    Hello,
    I have a 11gr2 dataguard configuration without the broker.
    main problem in my particular situation arises from my FRA size on primary much more than on standby (90Gb vs 30Gb) and in some situations I'm constrained with FRA space on standby.... I'm going to align the FRAs but in the mean time....
    can anyone confirm that if I have configuration as in subject with maximum performance mode and I'm not using the broker I should consider a sort of "external" way for archive log deletion on the physical standby?
    In fact I'm setting on primary
    - retention policy = redundancy 1
    - archivelog deletion = applied on standby (without using any "backed up...." option)
    Considering the standby it seems from docs that:
    - retention policy always wins over deletion policy (so no archive eligible for deletion is deleted if retention is not satisfied)
    - I can set on standby archivelog deletion = applied on standby (without using any "backed up...." option)
    But it is not clear to me the effect of this config in case this is a standby itself and without any other cascade standby databases
    The manual says this has to be met:
    1) The archived redo log files have been applied to the required standby databases.
    ---> what does this mean in case the db is a standby.. met or not met as I have no other cascade standby dependant on this one?
    2) The logs are not needed by the BACKED UP ... TIMES TO DEVICE TYPE deletion policy. If the BACKED UP policy is not set, then this condition is always met.
    ---> I should be ok
    So the last question for standby is
    - what to set retention policy to?
    I have not understood if I set it to "NONE", this means no retention at all or retention for ever....
    sometimes I read that there is no policy; in other examples that files will be retained forever (because no file considered as obsolete).... or at least so I understood...
    I would like to have a sort of policy on standby where the archive logs can be deleted as soon as they are applied during the continuous media recovery phase...
    It seems I can't find a self contained set of configurations across the dataguard....
    Thanks in advance.
    Gianluca

    I agree with you.... It is a temporary contingency....
    I already stressed the fact that sizes between sites must be quite identical...
    we are going towards a production dataguard, migrating from a windows config (without it) to a Linux based config....
    but this contingency made me think about these considerations regarding policies and automatic dataguard operations
    I also stressed on equal size grow capability for both sites file systems, also for data tablespaces, so that for example in case of high fragmentation we have to avoid a limit situation where
    1) a file system full for DR datafiles causes abend of automatic media recovery
    2) this generates FRA growth in DR because archive logs are shipped but not applied any more
    3) FRA goes 100% in DR and primary cannot ship any more
    4) archive logs cannot be automatically deleted on primary because not already shipped
    5) FRA full on primary and DB hangs....
    Thanks anyway for input

  • Procedure to delete archive log from standby server

    Hi
    We are using oracle10g(10.2.0.3) and we configured dataguard .
    I want to know procedure to delete applied archive log from standby server?
    Thanks
    With Regards
    umair

    [Delete Applied Archivelogs on Standby Database |http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html]
    http://tinyurl.com/p2krga
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com
    [Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

  • Have i missed any archive log in Standby setup?, im unable to find

    Dear All,
    I setup standby in Oracle10g.
    In my Primary the archive log list shows as
    primary>archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination D:\STANDBY\Archive
    Oldest online log sequence 30
    Next log sequence to archive 32
    Current log sequence 32
    In my standby the archive log list shows as
    standby>archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination C:\PRIMARY\Archive
    Oldest online log sequence 31
    Next log sequence to archive 0
    Current log sequence 32
    Have i missed any archive log file?
    But in my archive location of the primary i found the archive files from ARC00002_0633898426.001,ARC00003_0633898426.001 to ARC00031_0633898426.001
    and in my archive location of the standby i found the archive files from
    ARC00002_0633898426.001,ARC00003_0633898426.001 to ARC00031_0633898426.001 and one more extra archive file ARC00032_0633898426.001.
    I am getting confused from where i got the archive file ARC00032_0633898426.001 in standby only which is not in primary?
    Please clarify this...

    Please let me know abiut the above issue, i will be thankful to you.

  • Logs not applying on Standby Database

    I am afraid I am back.
    I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
    Fri Jun 29 15:03:40 2012
    alter database recover managed standby database disconnect from session
    Attempt to start background Managed Standby Recovery process (SAPDS)
    Fri Jun 29 15:03:40 2012
    MRP0 started with pid=29, OS id=23272
    MRP0: Background Managed Standby Recovery process started (SAPDS)
    started logmerger process
    Fri Jun 29 15:03:45 2012
    Managed Standby Recovery not using Real Time Apply
    Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
    Rereading datafile 2 header failed with ORA-01206
    MRP0: Background Media Recovery terminated with error 1110
    Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01206: file is not part of this database - wrong database id
    Recovery Slave PR00 previously exited with exception 1110
    Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01206: file is not part of this database - wrong database id
    MRP0: Background Media Recovery process shutdown (SAPDS)
    Completed: alter database recover managed standby database disconnect from session
    My question therefore is how can I get out of this and get my logs to apply on standby?

    Hello again;
    Do you think if I tried to repeat the duplicate?
    Yes I think you should do this.
    Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
    I always cleanup the standby before trying another dup
    OVERVIEW
    Step 1 - Password file fro standby - Copy from primary and rename
    Step 2 - Directory Structure on the remote server - Make sure noting is missing
    Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
    Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
    Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
    Step 6 - Initialization Parameter File for the Auxiliary Instance
    Step 7 - Set SID for Auxiliary Instance
    Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
    Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
    Step 10 - Start RMAN and run the DUPLICATE Command
    SID_LIST_LISTENER Example from mine
    SID_LIST_LISTENER =
       (SID_LIST =
           (SID_DESC =
           (SID_NAME = PLSExtProc)
           (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
           (PROGRAM = extproc)
           (SID_DESC =
           (global_dbname = CLONE.hostname)
           (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
           (sid_name = CLONE)
    Prevent Timeouts
    Add these to both servers
    To listener.ora
    INBOUND_CONNECT_TIMEOUT_ = 120
    To sqlnet.ora
    SQLNET.INBOUND_CONNECT_TIMEOUT = 120
    Then stop and start the listener.
    RMAN
    $ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
    Connect should return something like this
    connected to target database: RECOVER9 (DBID=3806912436)
    connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
    INIT Extras
    To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
    Best Regards
    mseberg
    Edited by: mseberg on Jun 29, 2012 11:12 AM

  • Archive log registered,but showing as not applied in standby db + oracle 9i

    Hi all,
    In my standby database some of the archive log files are not applied.found through the following command
    SQL > select sequence#,applied from v$archived_log where applied='NO';
    sequence# APP FIRST_TIME
    18425 NO 05-FEB-10
    but when try to register manually
    SQL > alter database register logfile '/disk12/arch/A00123000018425.arc';
    ERROR at line 1
    ORA-16089:archive log has already been registered.
    "recover standby database" also asking for the new archive file. how will i apply that?
    any solutions?

    user11919409 wrote:
    I have did that so many times from 05-feb-10 onwards.
    even then only one archive gap???
    or only one is not applied? if yes may be archive file which exist at standby may be corrupt try to restore it from backup and recover.
    also check for some clues at logs at standby and primary.. what actually happen. if archive gap is huge and you have all archvies then you may have to do manual recovery then keep it back to auto recovery mode.
    Hope that may help you.
    Anil Malkai

  • Manually apply archived log to standby database.

    Hi all,
    I am working on oracle 10g EE(10.2.0.4).I am having a very difficult database switchover case in my hand.
    1.> There are two database .one primary(prim) and another standby(standby).
    2.> Initially both of them was configured as oracle data guard, where prim was primary and standby was standby using rman .(RMAN>duplicate target database for
    standby dorecover).
    3.>But the rate of generation of archivelog is very high( 20 archivelog per hour with 200mb each).
    4.> So automatic shipping of archivelog has been disabled from primary.(log_archive_dest_state_2=defer and nullifying the value of log_archive_dest_2).
    5> Now after a period of time archived logs are shipped to dr site manually and applied manually.(alter database recover automatic standby database;)
    6.> Now there is a hardware problem occured at primary..it will take 72 hours to come up.
    How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
    Is it possible to switchover and switch back these two database with such a configuration?

    How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
    Is it possible to switchover and switch back these two database with such a configuration?
    As of now you can perform failover your standby to primary database. you should have flashaback enabled, so you have to create a restore point.
    Then it can be opened in read & write mode, So once you finished again you can go back to that point.
    http://docs.oracle.com/cd/B19306_01/server.102/b14239/manage_ps.htm#i1017111
    The above case applicable if you ready to loose, But it doesnt make sense. But in your case this doesnt work. Because once you start use of Standby as primary, there would be live/production data, which you need very much.
    So there is lot of work to do.
    You have to rebuild standby database and then switchover back to same location. So its a little trip work.
    Have you enabled Dataguard Broker ?
    Edited by: CKPT on Mar 13, 2012 1:43 PM

  • Archive logs not applied on standby!!

    Hi Guys,
    I am trying to set up physical standby on windows 2003 server. I am using oracle 10.2.0.4.0. I get the following error in my alert file on standby
    Failed to request gap sequence
    Following is the results of some queries :
    SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    MR(fg) WAIT_FOR_GAP 1 10004 0 0
    SQL> select * from v$archive_gap;
    no rows selected
    SQL> select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    MESSAGE
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    FAL[client]: All defined FAL servers have been attempted.
    MESSAGE
    MRP0: Background Media Recovery cancelled with status 16037
    MRP0: Background Media Recovery process shutdown
    Managed Standby Recovery Canceled
    Media Recovery Start: Managed Standby Recovery
    Managed Standby Recovery not using Real Time Apply
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    FAL[client]: All defined FAL servers have been attempted.
    SQL>SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
    where applied= 'YES'
    no rows selected
    ##Modification to primary##
    *.log_archive_dest_2='SERVICE=STANDBY'
    *.fal_client='STUTEST'
    *.fal_server='STUSTANDBY'
    *.log_archive_config='DG_CONFIG=(STUTEST,STUSTANDBY)'
    ##Modification to standby##
    *.db_unique_name='STANDBY'
    *.log_archive_dest_2='SERVICE=STANDBY'
    *.log_archive_dest_state_2='ENABLE'
    *.Fal_server=STUTEST
    *.Fal_client=STUSTANDBY
    *.db_file_name_convert='H:\ORACLE\ORADATA\STUTEST\','I:\ORACLE\ORADATA\STUTEST\s_'
    *.log_file_name_convert='D:\oracle\oradata\STUTEST\','D:\oracle\oradata\STUTEST\s_'
    Nore: I used RMAN to create the standby database. The following are brief steps
    Below are the steps to accomplish the task :
    Step 1: Backup the database that includes backup of datafiles, archivelogs and controlfile for standby
    backup current controlfile for standby;
    Step 2: Move the backups to the standby server and restore control file from backup
    Step 3: Make changes in the parameter files of both primary and standby database
    Step 4: Do the restore and recover on standby database
    Step 5: Put the standby database in recover managed mode
    Thanks for help guys!!!!!

    Hi sb92075
    Alert log on standby
    alter database mount standby database
    Mon Jul 26 14:10:40 2010
    Setting recovery target incarnation to 1
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=21, OS id=6708
    ARC1 started with pid=22, OS id=3892
    ARC2 started with pid=23, OS id=4380
    ARC3 started with pid=24, OS id=4896
    ARC4 started with pid=25, OS id=6348
    ARC5 started with pid=26, OS id=5868
    ARC6 started with pid=27, OS id=6904
    ARC7 started with pid=28, OS id=4428
    ARC8 started with pid=29, OS id=5008
    Mon Jul 26 14:10:40 2010
    ARC0: Archival started
    ARC9 started with pid=30, OS id=5804
    Mon Jul 26 14:10:41 2010
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Mon Jul 26 14:10:41 2010
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC0: Thread not mounted
    Mon Jul 26 14:10:41 2010
    Successful mount of redo thread 1, with mount id 2477113436
    Mon Jul 26 14:10:41 2010
    Physical Standby Database mounted.
    Mon Jul 26 14:10:42 2010
    ARC1: Becoming the heartbeat ARCH
    Completed: alter database mount standby database
    Mon Jul 26 14:10:42 2010
    Errors in file c:\oracle\admin\stustandby\udump\stustandby_ora_6604.trc:
    Mon Jul 26 14:11:41 2010
    alter database recover managed standby database disconnect from session
    MRP0 started with pid=19, OS id=3696
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Mon Jul 26 14:11:46 2010
    Waiting for all non-current ORLs to be archived...
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    Mon Jul 26 14:11:47 2010
    Completed: alter database recover managed standby database disconnect from session
    Mon Jul 26 14:12:16 2010
    *FAL[client]: Failed to request gap sequence*
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    *FAL[client]: All defined FAL servers have been attempted.*
    Alert log on primary
    Mon Jul 26 13:50:11 2010
    db_recovery_file_dest_size of 40960 MB is 49.73% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Mon Jul 26 13:50:12 2010
    Successfully onlined Undo Tablespace 19.
    Mon Jul 26 13:50:12 2010
    SMON: enabling tx recovery
    Mon Jul 26 13:50:12 2010
    Database Characterset is WE8ISO8859P1
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 8
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=38, OS id=3776
    Mon Jul 26 13:50:14 2010
    Completed: ALTER DATABASE OPEN
    Mon Jul 26 13:51:10 2010
    Shutting down archive processes
    Mon Jul 26 13:51:15 2010
    ARCH shutting down
    ARCa: Archival stopped
    Mon Jul 26 14:11:47 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    *FAL[server]: DGID from FAL client not in Data Guard configuration*
    *FAL[server]: FAL request for destination STUSTANDBY was:*
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    Mon Jul 26 15:04:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    *FAL[server]: DGID from FAL client not in Data Guard configuration*
    *FAL[server]: FAL request for destination STUSTANDBY was:*
    GAP - thread 1 sequence 10004-10017 DBID 2422302575 branch 670594799

Maybe you are looking for

  • Does the warranty cover the headphones that comes with it ?

    so does it ? Because mine just sound REALLY, REALLY bad when its at full blast and me loving loud music (rock), i always put it at near full blast. so do you guys think i can return headphones and get a replacement ? its only been less than a month.

  • Wrecked after Syncing

    My iPhone 4s wrecked after syncing on a MacBook 2009. It kept to restart a lot of time when plugged. After that some functions where not available and another attempt to sync ended into putting the iPhone in "restore mode". I could not restore since

  • Incorrect valuation of stock items through multiple deliveries

    Dear all, In our SAP system, it was observed that items ordered though overseas purchase orders were wrongly valued by the system when they were received in two or more consignments. While CIF values were correctly apportioned, only part of total amo

  • Apo dp support

    hi sir good morning actually am going to assign in support project by the company within couple of days. Acutually i don't have any support experience. As per DP MODULE What will we do in the support project.  What kind of quiries we will get. i thou

  • Can PS Element catalog files .psa be read?

    I have PSE 5.0 and used it to calalog my pics. I like it, but it is so slow on startup so that I thought Album Starter Edition might be good for me to view my pictures. If I try to open the .psa catalog file created with Elements, however, I receive