Copy controlfiles to standby

Hello,
I will create a standby database 11g. For that, I need to copy all files from source server to new standby destination server.
sql> ALTER DATABASE BEGIN BACKUP;
-- copy all datafiles, redologs, tempfiles, controlfiles, etc. by o/s from source database server to standby server.
sql> ALTER DATABASE END BACKUP;In source database, I have these controlfiles:
sql> select status, name, is_recovery_dest_file from v$controlfile;
STATUS  NAME                                                         IS_RECOVERY_DEST_FILE   
        D:\ORADATA\PROD\OPEXT\CONTROL1_1.CTL                         NO                      
        D:\ORADATA\PROD\OPEXT\CONTROL2_1.CTL                         NO                      
        C:\APP\ORACLE\PRODUCT\11.2.0\FLASH_RECOVERY_AREA\OPEXT\CONTR YES                     
        OLFILE\O1_MF_8F71JQLV_.CTL                                          Do I need to also copy controlfile which is in flash_recovery_area?
Do I need to replace it in same path in standby server?

Hi,
I copy a link where you can see a complete configuration of RMAN for generate the standby database of mode simple.
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101723
Please take as reference the pages: 1-42

Similar Messages

  • How to create primary controlfile from standby controlfile?

    We need to create a primary control file from a standby control file.
    SQL> select name, controlfile_type from v$database;
    NAME CONTROL
    HPR STANDBY
    Please help.
    Thank you very much.

    May wrote:
    We need to create a primary control file from a standby control file.
    SQL> select name, controlfile_type from v$database;
    NAME CONTROL
    HPR STANDBY
    Please help.
    Thank you very much.What is a problem?
    You can not create controlfile from standby controlfile(Expected activate time).
    And you lost controlfile?

  • RMAN and ASM, copy controlfile

    How to copy a controlfile from one diskgroup to another diskgroup?

    I answered here:
    ASM, copy controlfile
    Joel Pèrez
    http://otn.oracle.com/experts

  • Switchover of a manual standby database (no data guard)

    Hi all,
    I have a standby database .
    I am using Oracle Standard Edition 10.2.0.4 / 10.2.0.5 so I have build a manual standby .
    I am able to do a failover in the case something goes wrong; I was thinking if it is possible to do a manual switchover . and failback.
    Do you thick that mounting the primary database and applying ALL archivelogs and online redolog to the standby database is enough ?
    Do you think this is a supported operation?
    How can I check the current scn of a mounted database? (v$database.current_scn shows 0 until the database is opened )
    thnk you for every answer
    Andrea

    helter_skelter wrote:
    hi,
    You can see current_scn of standby database in v$database.current_scn. It is null only on primary database if it's in mount state.that's the problem: I am unable to mount both database and to check they have the same current_scn
    not all changes are written to ARL so you can't recover standby database to exact the same SCN as primaryI thinks this is because the last changes are only recorder in online redolog, so I was thinking that a possible way to simulate a clean switchover could be as follow:
    1 - shutdown immediate the primary database on server prod1
    2 - shutdown abort the (manual) standby database on server dr2
    3 - copy archivelog, controlfiles, tempfiles, onlinelogs from primary to the standby database
    3 - copy controlfiles from standby database to primary database
    4 - open the database on server dr2. It should open "read write" cleanly (mount + recover from archivelog + recover from onlinelog + open noresetlogs )
    5 - mount the database on server prod1. It should mount as a physical standby database.
    What do you think about it?
    thanks,
    andrea

  • Create standby database using restore backup

    Hi,
    I am creating a standby database 11g using  manual process of restoring a backup , but to no avail. I can not even restore the backup successfully.
    This is the steps I followed (courtesy of ORACLE-BASE) ORACLE-BASE - Data Guard Physical Standby Setup in Oracle Database 11g Release 2
    I am confused about these steps:
    Copy the files from the primary to the standby server.
    Copy Standby controlfile to all locations.
    $ scp oracle@ol5-112-dga1:/tmp/db11g_stby.ctl /u01/app/oracle/oradata/DB11G/control01.ctl
    $ cp /u01/app/oracle/oradata/DB11G/control01.ctl /u01/app/oracle/fast_recovery_area/DB11G/control02.ctl
    My question is, for the 2nd copy, do I need to shutdown the primary db? since control01.ctl is being updated all the time?
    Can I not used the standby ctl (db11g_stbg.ctl) and copy it to /u01/app/oracle/fast_recovery_area/DB11G/control02.ctl instead?
    Your assistance is highly appreciated.

    f55237a7-2c38-4db3-a7a3-1d77256f0730 wrote:
    Hi,
    I am creating a standby database 11g using  manual process of restoring a backup , but to no avail. I can not even restore the backup successfully.
    This is the steps I followed (courtesy of ORACLE-BASE) ORACLE-BASE - Data Guard Physical Standby Setup in Oracle Database 11g Release 2
    I am confused about these steps:
    Copy the files from the primary to the standby server.
    Copy Standby controlfile to all locations.
    $ scp oracle@ol5-112-dga1:/tmp/db11g_stby.ctl /u01/app/oracle/oradata/DB11G/control01.ctl
    $ cp /u01/app/oracle/oradata/DB11G/control01.ctl /u01/app/oracle/fast_recovery_area/DB11G/control02.ctl
    My question is, for the 2nd copy, do I need to shutdown the primary db? since control01.ctl is being updated all the time?
    Can I not used the standby ctl (db11g_stbg.ctl) and copy it to /u01/app/oracle/fast_recovery_area/DB11G/control02.ctl instead?
    Your assistance is highly appreciated.
    Hi,
    You are created standby  control file on primary and copied to standby  side:
    $ scp oracle@ol5-112-dga1:/tmp/db11g_stby.ctl /u01/app/oracle/oradata/DB11G/control01.ctl
    And now, in paramter files, you have CONTROL_FILES parameter as below :
    control_files='/u01/app/oracle/oradata/DB11G/control01.ctl', '/u01/app/oracle/fast_recovery_area/DB11G/control02.ctl'
    it means you must copy controlfile IN standby side to second control file. Control  files must be same.
    $ cp /u01/app/oracle/oradata/DB11G/control01.ctl /u01/app/oracle/fast_recovery_area/DB11G/control02.ctl
    My question is, for the 2nd copy, do I need to shutdown the primary db? since control01.ctl is being updated all the time?
    You not need shutdown priamry database, becuase you  copied standby control file to standby side, and all operations goin in standby side.
    Can I not used the standby ctl (db11g_stbg.ctl) and copy it to /u01/app/oracle/fast_recovery_area/DB11G/control02.ctl instead?
    Yes, you can use (db11g_stbg.ctl)  standby controlfile
    Regard
    Mahir M. Quluzade

  • Copy a standby database

    Hi
    I need to periodically make a copy of a standby database to another db. For this purpose we can use a fast copy mechanism at the storage level. We've been doing similar things with normal (non-standby) databases many times and all is fine. Normally, before the copy happens we simply switch the db into the backup mode (alter database begin backup), than clone it and start the copy on a different host under a different name.
    My question is if I can copy the standby database while it is mounted and redolog application is stopped? Nothing should be writing to data files in such case. Will this image be consistent? I cannot execute the 'alter database begin backup' command because the database is a standby database and cannot be opened. Shutting down the source database would require action from other people what I would like to avoid.
    Kind Regards,
    Tim

    Thank you for your replies.
    rajeysh wrote:
    why you are using user managed backup ?
    use rman it is faster than traditional user managed backup copy.As I wrote, we use a copy mechanism at the storage array level. It's a way faster than RMAN. We only need to make sure the copy is recoverable.
    rajeysh wrote:
    also you cannot take backup while the database is in mount stage, the image will be inconsistent.Why do you think I cannot? If no recovery actions are running in the mount state, no data files are being written. If it's inconsistent in the mount state (awaits recovery because instance was terminated), than it is recoverable. No problem, I can later use redo data to make the copy consistent.
    Iordan Iotzov wrote:
    A sure way to have you standby DB in a consistent state is to open it read-only.
    Once the copy is done you can return it back to applying redo.
    Iordan Iotzov
    http://iiotzov.wordpress.com/
    Edited by: Iordan Iotzov on Jul 12, 2011 8:00 AMIt's a great idea. In the read-only mode no changes occur to data files and nobody will accidentally start managed recovery (without restarting the instance) while I am copying the database.
    Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2):
    Making User-Managed Backups of Read-Only Tablespaces
    When backing up an online read-only tablespace, you can simply back up the online datafiles. You do not have to place the tablespace in backup mode because the database is not permitting changes to the datafiles.

  • Mounting a standby database with an older standby controlfile (Manual)

    Hi,
    We recently created a standby database and mounted it with a standby controlfile that was at least 1 month older than than the datafiles. The database was not taken out of recovery mode or opened. When we attempted to recovery the database using the older standby control file, it requested an archival log that was much older than SCN for the datafiles.
    My question is: Is it possible to create a new standby controlfile (CREATE STANDBY CONTROLFILE TO <file>) from the production live system and put the standby database back into recovery mode to apply newer/recent archivelogs? Or essentially has anything been corrupted?
    The database is 10.2.0.4 on Sun Solaris. Also, the this is manual standby, not automatic (RMAN).
    Thanks in advance.

    user6676819 wrote:
    Hi,
    We recently created a standby database and mounted it with a standby controlfile that was at least 1 month older than than the datafiles. The database was not taken out of recovery mode or opened. When we attempted to recovery the database using the older standby control file, it requested an archival log that was much older than SCN for the datafiles.
    My question is: Is it possible to create a new standby controlfile (CREATE STANDBY CONTROLFILE TO <file>) from the production live system and put the standby database back into recovery mode to apply newer/recent archivelogs? Or essentially has anything been corrupted?Hi.That is not possible.In your case best way is getting incremental backup from primary database and apply that into standby database then place stanby database in recover mode.To doing this see below thread.
    Re: archive log missing for standby

  • Error while trying to setup a standby database.

    While tring to setup a standby database (with version 8.1.7.0.0) i am running the command:
    recover managed standby database timeout 20;
    Here is the errors i'm getting:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/data/syndicate/standby/system/dup75_system01.dbf'
    ORA-16016: archived log for thread 1 sequence# 6518 unavailable
    Although it says that file 1 was not restored from sufficiently old backup I've copied all the datafiles from the primary database at once - using a script.
    The archived log sequence it asks for is non-existant - the last one i have is # 6517.
    Thank you guys in advance for any ideas.
    Greg

    I am having the same problem as you are when I am applying the current logs after successfully mounting standby database as seen below:
    SVRMGR> alter database mount standby database;
    Statement processed.
    SVRMGR> recover standby database ;
    ORA-00279: change 2939586 generated at 07/28/2002 01:09:33 needed for thread 5718
    ORA-00289: suggestion : C:\ORACLE\ORADATA\STANDBY\ARCHIVE\STANDBYT571S00362.ARC
    ORA-00280: change 2939586 for thread 5718 is in sequence #362
    Specify log: {=suggested | filename | AUTO | CANCEL}
    CANCEL
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'C:\ORACLE\ORADATA\STANDBY\SYSTEM01.DBF'
    SVRMGR>
    Just before copying the datafiles from the primary database I did the following:
    Connected to the primary database:
    1. alter database create standby controlfile as .....
    2. alter system switch logfile
    3. shutdown normal
    4. took a cold backup (including archived redo logs)
    Copied the data files, redolog files, archived redo logs and standby controlfile to standby database:
    1. made copies of standby controlfile over current standby ones.
    2. startup nomount (the standby database)
    3. alter database mount standby database;
    4. recover standby database;
    That's when it asks for an archived redo log that does'nt exist and when I enter cancel, that's when I get the above error?
    Am I not applying the latest redo logs to the latest cold backup of the primary database?
    Your help would be much appreciated!

  • Restore from OSB. RMAN-06024: no backup or copy of the control file found

    I backed up controlfile for standby on production server to OSB media:
    -bash-3.00$ rman target / catalog rman/rman@emgc
    Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:15:33 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: EMGC (DBID=1838014073)
    connected to recovery catalog database
    RMAN>
    RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    BACKUP CURRENT CONTROLFILE FOR STANDBY tag 'stb_ctl';
    RELEASE CHANNEL ch1;
    CONFIGURE DEVICE TYPE 'SBT_TAPE' CLEAR;
    new RMAN configuration parameters:
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN> 2> 3> 4> 5> 6>
    allocated channel: ch1
    channel ch1: sid=1085 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting backup at 25-JAN-11
    channel ch1: starting compressed full datafile backupset
    channel ch1: specifying datafile(s) in backupset
    including standby control file in backupset
    channel ch1: starting piece 1 at 25-JAN-11
    channel ch1: finished piece 1 at 25-JAN-11
    piece handle=1em30ngu_1_1 tag=STB_CTL comment=API Version 2.0,MMS Version 10.3.0.2
    channel ch1: backup set complete, elapsed time: 00:00:27
    Finished backup at 25-JAN-11
    released channel: ch1
    RMAN> list backup of controlfile;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    RMAN configuration parameters are successfully reset to default value
    starting full resync of recovery catalog
    full resync complete
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
    BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
    Handle: 1em30ngu_1_1 Media: mf_rman-000003
    Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
    RMAN>
    On standby server I try to restore this control file but there is some trouble with restore... By the way I can delete that backup piece...
    -bash-3.00$ rman target / catalog rman/rman@emgc
    Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:34:32 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: emgc (not mounted)
    connected to recovery catalog database
    RMAN> set DBID=1838014073;
    executing command: SET DBID
    database name is "EMGC" and DBID is 1838014073
    RMAN> RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    crosscheck backup of controlfile;
    2> 3> 4> 5>
    allocated channel: ch1
    channel ch1: sid=1093 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
    Crosschecked 1 objects
    released channel: ch1
    RMAN> list backup of controlfile;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
    BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
    Handle: 1em30ngu_1_1 Media: mf_rman-000003
    Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
    RMAN> RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    RESTORE CONTROLFILE FROM TAG 'STB_CTL';
    2> 3> 4> 5>
    allocated channel: ch1
    channel ch1: sid=1093 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting restore at 25-JAN-11
    released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 01/25/2011 15:35:20
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    RMAN> RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    delete noprompt backup of controlfile;
    2> 3> 4> 5>
    allocated channel: ch1
    channel ch1: sid=1093 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    List of Backup Pieces
    BP Key BS Key Pc# Cp# Status Device Type Piece Name
    1480 1479 1 1 AVAILABLE SBT_TAPE 1em30ngu_1_1
    deleted backup piece
    backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
    Deleted 1 objects
    released channel: ch1
    RMAN>

    You cannot specify a tag for a standby control file.
    read here
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmstand.htm#1002594
    Edited by: Adigozalov Gurban on Jan 25, 2011 2:14 PM

  • Creation of Standby database on same host

    Hi All,
    I am using oracle 9.2.0.1.0 on windows XP machine.
    *I want to create the standby database for my primary database on same machine.
    But both tha data base is heaving diff instance as well as the diff database name say "ASHU" for primary & "TEST" for standby database.
    I took the backup of all datafile and copied it in the standby location.
    Generate the standby control file also and copied to the standby location.
    But when i am going to start the standby database it is giving the below error:
    SQL> startup nomount;
    ORACLE instance started.
    Total System Global Area 135338868 bytes
    Fixed Size 453492 bytes
    Variable Size 109051904 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 667648 bytes
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01103: database name 'ASHU' in controlfile is not 'TEST'
    How to rectify it? Please help me
    (* This is only for learning pupose , that's why i am going to create both on same host"

    >
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01103: database name 'ASHU' in controlfile is not 'TEST'
    How to rectify it? Please help me
    >
    You do not change the dbname of the physical standby database. They always must have the same name as the primary.
    Here is a snippet from my standby initialization file for a 9i installation. Notice the parameter LOCK_NAME_SPACE that was replaced in 10g with DB_UNIQUE_NAME
    db_file_name_convert=('E:\PRIMA','E:\PHYST')
    db_name='PRIMA'
    instance_name='PHYST'
    service_names='PHYST'
    lock_name_space='PHYST'
    log_archive_dest_1='LOCATION=E:\PHYST\ARCHIVE'
    log_archive_start=TRUE
    log_archive_format='%t_%s.arc'
    log_file_name_convert=('E:\PRIMA','E:\PHYST')Kind regards
    Uwe
    http://uhesse.wordpress.com
    Edited by: Uwe Hesse on 27.07.2009 13:36

  • RMAN 11gR2 DUPLICATE TARGET FOR STANDBY FROM ACTIVE DATABASE - Issue -HELP

    First question.
    Can primary and standby database have the same SID name?
    As I recall it is yes.
    I believe they must have different GLOBAL or DB_UNIQUE_NAME?
    Anyway, RMAN I believe is telling me it is having problems copying control file on first and dies.
    Permissions Issue on STANDBY machine?
    RMAN> connect target backup_admin/backup_admin
    connected to target database: LABDG (DBID=1973403623)
    RMAN> connect auxiliary sys/oracle@STANDBY;
    connected to auxiliary database: LABDG (not mounted)
    RMAN> DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE;
    Starting Duplicate Db at 18-JUL-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=10 device type=DISK
    contents of Memory Script:
    backup as copy reuse
    targetfile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' auxiliar
    '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' ;
    executing Memory Script
    Starting backup at 18-JUL-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=151 device type=DISK
    Finished backup at 18-JUL-11
    contents of Memory Script:
    backup as copy current controlfile for standby auxiliary format '/u01/oradat
    restore clone controlfile to '/u01/app/oracle/flash_recovery_area/LABDG/cont
    '/u01/oradata/LABDG/control01.ctl';
    executing Memory Script
    Starting backup at 18-JUL-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile copy
    copying standby control file
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/18/2011 11:20:54
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/18/2011 11:20:
    ORA-17628: Oracle error 19505 returned by remote Oracle server

    Hi,
    Permissions Issue on STANDBY machine?First problem I see is the sysdba password must be the same on both sides (target and auxiliary dbs).
    From the documentation.
    The source database and auxiliary instances must use the same SYSDBA password, which means that both instances must have password files. You can
    create the password file with a single password so you can start the auxiliary instance and enable the source database to connect to it.Check all prereqs for the standby db duplicate here.
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724
    Rgds,
    Tycho

  • Problem creating physical Standby database with RMAN

    Hi All
    I am trying to learn oracle dataguard and as part of the process learning creating standby database.
    Platform : Sun-Fire-V250 Sparc, Solaris 10
    Database Version - Oracle 11R2
    I am creating standby database on same server, so directory structure is different.
    Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
    1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
    2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
    On Primary Database:
    *.FAL_CLIENT='orcl11020' #Primary database unique name
    *.FAL_SERVER='stdby_11' #Standby database unique name
    db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
    log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
    standby_file_management=auto
    *.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
    *.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
    *.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    Copied same pfile for standby database and modified following-
    *.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
    *.db_name='orcl1102'
    *.db_unique_name='stdby_11'
    *.FAL_CLIENT='stdby_11'
    *.FAL_SERVER='orcl11020'
    db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
    log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
    standby_file_management=auto
    *.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
    *.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    db_unique_name=orcl11020'
    3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
    3. Created password file with same credential as primary database.
    4.Up-to-date RMAN backup of primary database available.
    5.Create standby controlfile with rman
    While primary database s open (I tried with primary database in mount mode as well)-
    $>rman catalog rman/paswd@rman target /
    RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
    6. Open a new terminal and startup standby database in nomount mode using parameter file created -
    $>ORACLE_SID=stdby_11
    $>export ORACLE_SID
    $>sqlplus / as sysdba
    SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
    SQL>quit
    $> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
    RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
    RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
    Error 1017 received logging on to the standby
    Check that the primary and standby are using a password file
    and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
    and that the SYS password is same in the password files.
    returning error ORA-16191
    FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
    Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    So on both primary and standby I confirmed
    SQL> show parameter remote_login_passwordfile
    NAME TYPE VALUE
    remote_login_passwordfile string EXCLUSIVE
    To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
    Password files are called - orapworcl11020 and orapwstdby_11
    Can someone guide me where thisngs are going wrong here please.

    Not sure if I understood it clearly.
    SELECT * FROM V$ARCHIVE_GAP;
    returns no rows so there is no gap.
    But could you please explain me the result of the previous query. To catch up again, on standby when I check
    SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    SEQUENCE# APPLIED
    75 NO
    74 NO
    76 NO
    77 NO
    I understand that though archive files have been copied across but they are not applied yet.
    On primary when I give your query -
    SELECT name as STANDBY,SEQUENCE#,applied, completion_time
    2 FROM v$archived_log
    3 where dest_id=2
    4 and sequence# BETWEEN 74 and 80;
    I get -
    STANDBY SEQUENCE# APPLIED COMPLETIO
    stdby_11 74 YES 28-JUN-11
    stdby_11 75 YES 28-JUN-11
    stdby_11 76 YES 29-JUN-11
    stdby_11 77 YES 29-JUN-11
    stdby_11 78 YES 29-JUN-11
    stdby_11 79 YES 29-JUN-11
    stdby_11 80 YES 29-JUN-11
    stdby_11 75 NO 07-JUL-11
    stdby_11 74 NO 07-JUL-11
    stdby_11 76 NO 07-JUL-11
    stdby_11 77 NO 07-JUL-11
    stdby_11 78 NO 07-JUL-11
    I have intentionally given
    sequence# BETWEEN 74 and 80
    because I know in the current incarnaion of the database, max sequence is 78.
    So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
    Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
    Then my final question is, when will these archives be applied to standby database?
    I am sorry to ask too many questions but I am just trying to understand how it all works.
    Thanks for your help again

  • Standby database from RMAN backup

    I have been assigned to create a standby database from our RMAN backups in a different machine, as this is my first attempt at recovering, I am struggling a bit. I would appreciate if someone can throw any light on what dumb mistakeI am doing here. I ahve absolutely no control over the back up script which is done by my vendor, but can do anything in the reocvery portion. I did try going through the documentaiton and other help available for the last 2 days.
    Database : Oracle 10G R2
    OS : Windows Server 2003
    My backup script is
    configure channel device type disk format 'J:\RMAN\RMAN_df_%U' maxpiecesize 2048M;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup database;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup current controlfile for standby FORMAT='J:\RMAN\RMAN_sc_%U';
    For recovery of a standby database,
    I have copied the the back up pieces and the archive logs to the standby server where I have just created an instance with the same name as production db.
    set ORACLE_SID=NGINPROD
    set dbid 820336652
    STARTUP NOMOUNT
    RESTORE STANDBY CONTROLFILE FROM 'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    CATALOG BACKUPPIECE 'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_5_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_6_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_7_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2TMIUJLN_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    RESTORE DATABASE;
    Till this step I do not encounter any issues, but when i try to recover the database I am hit with the below error.
    RMAN> recover database;
    Starting recover at 16-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=253340
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/16/2011 09:31:57
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 253340 lowscn 4696173517
    ------------------------------------------------------------------------------------------------------------------------------------------------

    Here's the standard dcoumentation on the procedure :
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377
    Appendix "F Creating a Standby Database with Recovery Manager" of the "Oracle® Data Guard Concepts and Administration" guide.
    I don't see ArchiveLog backups being done by the vendor's script. How do you backup the ArchiveLogs ?
    In your post you state that you have copied the ArchiveLogs. Are they copied to the same log_archive_dest location ? RMAN needs to be "aware" of them. You can use the "CATALOG" command in RMAN to register them into the controlfile.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
    A Standby Database uses a Standby Controlfile which is created from the Primary (with the "ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'locaion';" command) and then copied over to the Standby server.
    Hemant K Chitale

  • Problem in identifying control file when creating physical standby

    hi there,
    (database version: 10.2.0.4
    plateform linux)
    I'm using the command as below to create physical standby database from backup:
    rman target / auxiliary sys/tiger@paceview
    Recovery Manager: Release 10.2.0.4.0 - Production on Tue Sep 4 18:05:53 2012
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: PACEVIEW (DBID=2092349485)
    connected to auxiliary database: PACEVIEW (not mounted)
    run {
    allocate auxiliary channel c1 device type DISK;
    set until sequence 38;
    duplicate target database for standby dorecover nofilenamecheck;
    released channel: ORA_DISK_1
    allocated channel: c1
    channel c1: sid=35 devtype=DISK
    allocated channel: c2
    channel c2: sid=36 devtype=DISK
    executing command: SET until clause
    Starting Duplicate Db at 04-SEP-12
    contents of Memory Script:
       set until scn  138180211934;
       restore clone standby controlfile;
       sql clone 'alter database mount standby database';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 04-SEP-12
    channel c1: restoring control file
    ORA-19625: error identifying file /backup/rman/paceview/DEL1_standby.ctl
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-19600: input file is control file  (/backup/rman/paceview/DEL1_standby.ctl)
    ORA-19601: output file is control file  (/PGHProdDB/oradata/paceview/control1.ctl)
    failover to previous backup
    released channel: c1
    released channel: c2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/04/2012 18:01:44
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restorei have already tried crosscheck but still giving same error
    thanks

    Hello;
    So this is what I would do :
    Backup Primary ( change to your directory as need )
    RMAN RUN {
    allocate channel d1 type disk;
    backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
    sql 'alter system archive log current';
    backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
    backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
    release channel d1;
    }Move the backup and duplicate like this :
    rman target sys/password@PRIMARY auxiliary /
    RMAN> run {
    allocate channel C1 device type disk;
    allocate auxiliary channel C2 device type disk;
    duplicate target database for standby nofilenamecheck;
    }For complete details of this method see :
    http://www.visi.com/~mseberg/duprman2.html
    Best Regards
    mseberg

  • Manual Standby on Standard Edition

    Hey, I try to setup a manual standby on standard edition 10gR2.
    Source is a RAC database (standard edition on sles10 sp3)
    I created a node and created a oracle instance on this node. This node is using the filesystem for the oracle files.
    I did a hotbackup of the source database and copied all files over to the other host.
    Which parameters needs to be change in the init.ora and how can I recover my database ?
    Articles like
    http://www.databasejournal.com/features/oracle/article.php/3682421/Manual-Standby-Database-under-Oracle-Standard-Edition.htm
    or
    Alternative for standby database in standard edition [ID 333749.1]
    does not really help me.
    Thanks for your patience... :-)

    ./rman target / cmdfile=/opt/oracle/rman.sh
    rman.sh
    run{
    change archivelog all crosscheck;
    allocate channel ch1 type disk;
    backup incremental level 0 database format
    '/opt/oracle/backup/backupnew/bk_inc0_%s_%p' include current
    controlfile for standby ;
    sql "alter system archive log current";
    backup archivelog all format '/opt/oracle/backup/backupnew/al_%s_%p';
    release channel ch1;
    copy files from '/opt/oracle/backup/backupnew' to standbyhost:'/opt/oracle/backup/backupnew'
    ./rman cmdfile=/opt/oracle/duplicate.rman
    duplicate.rman
    connect auxiliary sys/oracle@standby
    connect target /
    run {
    allocate auxiliary channel ch1 type disk;
    duplicate target database for standby dorecover nofilenamecheck;
    release channel ch1;
    Now I get this:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/15/2010 15:20:35
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    When do have I to issue the
    ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/opt//oracle/stbycf.ctl';
    command. And where to copy ?

Maybe you are looking for

  • Time Machine won't work with Time Capsule

    HI all I have been using TM to backup to an Iomega portable drive but because the drive is relatively small and because I thought that having less wires around the place would be a good thing, I bought Time Capsule. However when I try to backup to TC

  • Mac mini 2014 mDP out of range

    Hi, I have a strange issue with Mac mini late 2014 and NEC PA272W monitor. Mac mini and the monitor are connected by high quality mini display port cable. Sometimes on boot the display is reporting: Out of range message H 14,6KHz. Its a sync problem?

  • Flash Help not displaying in IE7

    Hi all, Another issue (I'm having a great afternoon!) - Running the RH for Word 6 sample projects - when output to FlashHelp, the flash menus do not display. I have the latest version of Flash (9.0.smething) and IE7 and regularly run Flash output I h

  • Automator problem - Send text from file to email

    Hi all, I used automator on OsX 10.6 to send automatically the text within an HTML file to an email and then to a list of addresses. I installed 10.7 and now the thing doesn't work anymore. I did a couple of tests and it looks like the text taken fro

  • BDC message parameter(MSGTYP) by default coming Success

    Hi, In my BDC program by default the message type is coming success, whatever flat file I pass. Does anybody have any idea about this, letme know(kind of urgent). Thanks, Soumya Ranjan Patel.