Standby controlfile in 11.2

Dear all,
am in the process of configuring rac physical standby for 11.2 rac one node . Am following the
guide "download.oracle.com/docs/cd/E18283_01/server.112/e17022.pdf" . There is to mentioned
to create standby controlfiles in the primary location and nothing more is mentioned there.
(Probably I missed to understand this :)
In our primary database , we have 3 control files in a single location like
e:\oradata\control01.ctl,e:\oradata\control02.ctl,e:\oradata\control03.ctl and with standby including e:\oradata\standby0101.ctl .
Now, do I have to copy all the control files from the primary to the standby site and mention (in the pfile of the standby as)
control_files=e:\oradata\standby0101.ctl alone ?. or do I have to mention all the control files
in the control_files parameter ?
Please guide
Kai

do I have to copy all the control files from the primary to the standby siteSurely you know by this time that it is logically 1 controlfile file with 3 physical copies --- this is called "multiplexing".
Any production (even development) database -- whether primary or standby -- should be multiplexing its controlfile.
e17022.pdfInstead of reading the Data Guard Broker documentation you should read the Data Guard Concepts and Administration documentation.
Hemant K Chitale

Similar Messages

  • What is the diffrence between ' Contolfile ' and ' Standby Controlfile' ???

    Hi Guru's,
    Can someone please help me out with the diffrences between a 'Control File' and 'Standby Controlfile'.
    Thanks in advance
    Regards,
    Girish

    Kind of reply you can always expect from Sybrand...anyways...the controlfile of any production database would always be having a bit in itself which identifies a database as a primary or a standby database, so whenever you try to query select database_role from v$database; for any production database it would always give output as PRIMARY and for a standby it would always give output as PHYSICAL STANDBY..Hope it clears your doubts
    Regards,
    Ajinkya

  • Create a standby controlfile using cold backup

    Hi All,
    We have to setup a DR for a production database.
    Here we have the coldbackup which backups all the datafiles and the control file from the production database.
    For cloining we generally copy them to another instance and then create controlfile manually. But for setting up as a DR , we would be creating it for standby controlfile.
    I tried to google but I am not able to find a way to create a standby controlfile from the existing controlfile cold backup.
    OS version solaris 10 , database version 11.2.0.1
    Regards
    KK
    Edited by: Kk on Feb 16, 2012 8:51 AM

    Kk wrote:
    Hi All,
    We have to setup a DR for a production database.
    Here we have the coldbackup which backups all the datafiles and the control file from the production database.
    For cloining we generally copy them to another instance and then create controlfile manually. But for setting up as a DR , we would be creating it for standby controlfile.
    I tried to google but I am not able to find a way to create a standby controlfile from the existing controlfile cold backup.
    OS version solaris 10 , database version 11.2.0.1
    Regards
    KK
    Edited by: Kk on Feb 16, 2012 8:51 AMTry as below
    My version:
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE    11.2.0.1.0      Production
    TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production
    SQL>1) Taken backup of current controlfile
    2) Deleted Current controlfiles
    3) Restored using standby clause from current controlfile
    4) Mounted & now controlfile type is Standby
    Try in this way when you have cold backup. :)
    SQL> select controlfile_type from v$database;
    CONTROL
    CURRENT
    RMAN> run
    2> {
    3> allocate channel ch1 device type disk format 'c:\oracle\control%U.bkp';
    4> backup current controlfile;
    5> release channel ch1;
    6> }
    using target database control file instead of recovery catalog
    allocated channel: ch1
    channel ch1: SID=63 device type=DISK
    Starting backup at 16-FEB-12
    channel ch1: starting full datafile backup set
    channel ch1: specifying datafile(s) in backup set
    including current control file in backup set
    channel ch1: starting piece 1 at 16-FEB-12
    channel ch1: finished piece 1 at 16-FEB-12
    piece handle=C:\ORACLE\CONTROL08N3GEA6_1_1.BKP tag=TAG20120216T230334 comment=NONE
    channel ch1: backup set complete, elapsed time: 00:00:01
    Finished backup at 16-FEB-12
    released channel: ch1
    RMAN> exit
    RMAN> restore standby controlfile from 'C:\ORACLE\CONTROL08N3GEA6_1_1.BKP';
    Starting restore at 16-FEB-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=66 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=C:\ORACLE\ORADATA\ORCL\CONTROL01.CTL
    output file name=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL
    Finished restore at 16-FEB-12
    SQL> alter database mount;
    Database altered.
    SQL> select controlfile_type from v$database;
    CONTROL
    STANDBY
    SQL>
    Some More information:-
    Even if your database backup is old, still you can create a new standby controlfile and restore new controlfile and restore database. Later after starting MRP all will be synchronized. No issues
    SQL> select controlfile_type from v$database;
    CONTROL
    CURRENT
    SQL> alter database create standby controlfile as 'c:\oracle\control_stby.ctl';
    Database altered.
    SQL> $dir c:\oracle\con*
    Volume in drive C is System
    Volume Serial Number is 1853-3E21
    Directory of c:\oracle
    02/16/2012  11:41 PM         9,748,480 CONTROL_STBY.CTL
                   1 File(s)     19,546,112 bytes
                   0 Dir(s)  177,185,570,816 bytes free
    SQL>Now Just restore database. You already have backup.
    Or
    If you have opportunity you can go ahead for Duplicate/Duplicate from active database
    Edited by: CKPT on Feb 16, 2012 11:41 PM

  • Create standby controlfile

    To create a standby controlfile, do I have to be with my database mounted in exclusive, or there is another way to do that without shutdown the database?
    Thanks,
    Rafael.

    dear friend
    The production database need not be open in exclusive mode
    to create statnd by control file.
    Suresh

  • Oracle 9i. RMAN. How to restore standby controlfile using "from tag" clause

    -bash-3.00$ rman target / catalog rman/rman@emgc
    Recovery Manager: Release 9.2.0.8.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to target database: crvs (not mounted)
    connected to recovery catalog database
    RMAN> list backup tag stby_ctrl;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    142851 Full 7M SBT_TAPE 00:01:44 02.02.11
    BP Key: 142852 Status: AVAILABLE Tag: STBY_CTRL
    Piece Name: CRVS_20110202.c7m3kbrd_1_1.stb
    Controlfile Included: Ckp SCN: 67168490043 Ckp time: 02.02.11
    RMAN> run
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/oracle/apps/osb/lib/libobk.so';
    RESTORE standby CONTROLFILE from tag stby_ctrl;
    release channel ch1;
    2> 3> 4>
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "from": expecting one of: "to"
    RMAN-01007: at line 4 column 29 file: standard input
    RMAN> run
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/oracle/apps/osb/lib/libobk.so';
    RESTORE CONTROLFILE from tag stby_ctrl;
    release channel ch1;
    2> 3> 4> 5> 6>
    allocated channel: ch1
    channel ch1: sid=13 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting restore at 04.02.11
    released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/04/2011 09:49:26
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the controlfile found to restore
    RMAN> run
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/oracle/apps/osb/lib/libobk.so';
    RESTORE CONTROLFILE from 'CRVS_20110202.c7m3kbrd_1_1.stb';
    release channel ch1;
    2> 3> 4> 5> 6>
    allocated channel: ch1
    channel ch1: sid=13 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting restore at 04.02.11
    channel ch1: restoring controlfile
    channel ch1: restore complete
    replicating controlfile
    input filename=/data02/crvs/ctrl/control01.ctl
    output filename=/data02/crvs/ctrl/control02.ctl
    Finished restore at 04.02.11
    released channel: ch1
    RMAN>

    The error message states:
    RMAN-01005: syntax error: found "from": expecting one of: "to"restore TO where?
    Personally I'd never use RMAN to restore a control file. Takes less time to job copy an existing one.

  • How to create standby controlfile from restored backup

    Hi Techies,
    I am re-building one of my DR server, Source and target DB is oracle 10g.
    I have taken the source backup which is going to be restored on target, But I forgot to take a standby controlfile from source DB at the time (Pre/Post) backup.
    Now the issue is I can create a standby controlfile on primary and copy the same to target, But so many datafiles are added after the backup which I have taken to restore and medias are already shipped.
    I can send the other set of backup to DR site, but it takes a week time and I don't want to do that If I can regenerate it.
    So any clue to create standby controlfile on target with restored datafiles?
    Regards,
    Nick Loy

    Hmm... sounds like you perform this in a rather manual fashion...
    Do you use RMAN for taking the backups?
    Or maybe the BR*TOOLS?
    With these tools you are usually safe from such mistakes - I can only recommend to use them!
    However, since you don't have a control file at all on the target side, the only thing left to do would be to
    ALTER DATABASE BACKUP CONTROLFILE TO TRACE NORESETLOGS;
    on the primary side and manually remove the files that have been added since you took the backup from the control file script,
    Afterwards you use the script on the standby side to create the control files.
    regards,
    Lars

  • 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

  • Creating Standby Controlfile

    Is it necessary to shutdown the primary database and then mount it to create standby controlfile for both Physical and Logical standby databases?
    Or is it alright to create standby controlfile while primary database is open?

    You should create standby controlfile while database is in mount mode
    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/]

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

  • Standby controlfile

    Hi all,
    I have created a standby database and is working propertly. I just drop the redo logs and recreated more and larger redo logs in the primary database. I followed the oracle documentation and try to refresh the standby database controlfile so that it reflects this change:
    1. shutdown the standby database
    2. on the primary datbase:
    alter database create standby controlfile as 'filesname'
    3. move the control file created in the step 2 to the primary database
    4. startup nomount
    5. alter database mount standby database.
    so far so good, no erros yet. Therefore I try to apply the log:
    6. recover standby database until cancel
    I hit cancel
    and received the following:
    SVRMGR> recover standby database until cancel;
    ORA-00279: change 95713083 generated at 02/16/2001 12:34:59 needed for thread 1
    ORA-00289: suggestion : /logs/ORCL/arch/ORCL_1_492.arc
    ORA-00280: change 95713083 for thread 1 is in sequence #492
    Specify log: {<RET>=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: '/u01/oradata/ORCL/system01.dbf'
    Why this happend? Any suggestion?
    Thank you very much in advance!
    --yc                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Oh,
    I mean move the standby controlfile to the standby database.
    --yc
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Shuet Ying Choi ([email protected]):
    Hi all,
    I have created a standby database and is working propertly. I just drop the redo logs and recreated more and larger redo logs in the primary database. I followed the oracle documentation and try to refresh the standby database controlfile so that it reflects this change:
    1. shutdown the standby database
    2. on the primary datbase:
    alter database create standby controlfile as 'filesname'
    3. move the control file created in the step 2 to the primary database
    4. startup nomount
    5. alter database mount standby database.
    so far so good, no erros yet. Therefore I try to apply the log:
    6. recover standby database until cancel
    I hit cancel
    and received the following:
    SVRMGR> recover standby database until cancel;
    ORA-00279: change 95713083 generated at 02/16/2001 12:34:59 needed for thread 1
    ORA-00289: suggestion : /logs/ORCL/arch/ORCL_1_492.arc
    ORA-00280: change 95713083 for thread 1 is in sequence #492
    Specify log: {<RET>=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: '/u01/oradata/ORCL/system01.dbf'
    Why this happend? Any suggestion?
    Thank you very much in advance!
    --yc<HR></BLOCKQUOTE>
    null

  • Can standby controlfile be created after backup

    can we take the online backup of primary database first and then create standby controlfile.will it be useful.
    as i have yesterday backup..now can i create standby controlfile now and configure data guard by restoring that backup.
    Regards

    Hi,
    user11221081 wrote:
    can we take the online backup of primary database first and then create standby controlfile.will it be useful.
    as i have yesterday backup..now can i create standby controlfile now and configure data guard by restoring that backup.
    Regards
    Yes, we can create standby  control  file, after backup.
    What is your database version?
    If you  are using 11g version, then you can RMAN DUPLICATE command FROM  ACTIVE DATABASE option.
    This duplication is not backup-based duplication.
    Regards
    Mahir M. Quluzade

  • Standby controlfiles

    I have 2 questions regarding the subject,
    1. When we create standby controlfile does this entry gets written into the existing controlfiles, if yes then if i run the create controlfile command again will it be overwriting the entry in existing contriol file?
    2. As per below text from documentation, Why do we have to create it only after the backup of datafiles.
    The below is from documentation:
    A control file needs to be created for the standby system. Execute the following on the primary system:
    alter database create standby controlfile as '/some/path/to/a/file'
    The created file must meet two conditions:
    •Its filename must be different from any other control file
    *•Must be created after the backup of the datafiles.*

    1. When you execute a CREATE CONTROLFILE, you lose all information about ArchiveLogs, Backups etc that was present in the controlfile. (You need to reregister backups into the controlfile with ALTER SYSTEM REGISTER LOGFILE for ArchiveLogs and CATALOG for all other backups).
    Nevertheless, an ALTER DATABASE CREATE STANDBY CONTROLFILE does not appear to register the standby controlfile as a backup of the controlfile.
    2. When you need to initiate Recovery or Managed Recovery of the Standby database, it should start with a target SCN higher than the datafile SCNs. A Standby controlfile that is created after the datafile backups, does have a higher SCN than those of the datafiles.
    Hemant K Chitale

  • Standby controlfile SCN ahead of datafile SCN

    Hello,
    Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
    Recovery interrupted!
    Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
    Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
    DB (stand-alone): 11.2.0.2
    Platform: Sun SPARC
    Thanks
    aBBy

    Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
    Recovery interrupted!
    Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
    Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
    Are you trying to perform Manual recovery from SQL? like recover standby database?
    Even if controlfile is new and datafiles are older, still you should able to perform recovery , But this will be a valid database to open when SCN's are in SYNC.
    SO perform recovery automated and then check synchronization.
    SQL> alter database recover managed standby database disconnect from session;
    Refer alert log file until it waits as " Media recovery waiting for thread# <no> sequence# <>"
    Then, check SYNC as follows
    Primary:-
    SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
    Standby:-
    SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
    SQL> select thread#, max(sequence#) from v$archived_log where applied='YES' group by thread#;
    Also you can try option of recreating standby controlfile as below from primary
    SQL> alter database create standby controlfile as 'loation';
    & restore it in standby database.

  • ORA-00235 Standby Database Controlfile problem

    Dear fellow dbas,
    I am just starting to become acquainted with high availability and have to solve following problem.
    We have a RAC database with a standby database that is out of sync. In fact the standby database is running in async mode but archived redo logs are not applied.
    They are successfully forwarded from the primary instance to the standby db though. Looking at the alert.log I discovered an ORA-00235 error - control file fixed table inconsistent due to concurrent update.
    As a result of this I have a huge gap between the primary and standby database.
    Can you please give me a step to step tutorial, how I can resolve this issue?
    Any help is appreciated!
    Many thanks,
    Sebastian

    Hello Anand,
    I am using 11.1.0.7.0.
    My standby database is a cluster database as well. I shut both instances down using srvctl and created a standby controlfile from my primary instance, which I copied to the respective locations referred to in the spfile of my dataguard database. Afterwards I started up and issued a ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    The database does not open and the alert.log states ORA-01124 "cannot recover datafile 1 - file is in use or recovery".
    Next, the background media recovery process was shut down.
    What should I do, to get my standby back running?
    Should I place the primary database in backup mode and copy the datafiles to my standby db?
    Afterwards I would create a standby controlfile again and overwrite the standby ones.
    Maybe you assist in pointing at the next steps.
    Many thanks,
    Sebastian

  • Creation of standby logical controlfile

    can anybody let me know how to create standby logical controlfile....
    i know how to create physical standby control file....
    when i created a logical standby controlfile and after mounting the logical standby database, i got an erorr database name is not a standby database...

    Hi,
    DB VERSION matters here!!
    apart from that just look at this...
    For 9.2
    On the primary database, create a backup copy of the control file for the standby database:
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO
    2> '/disk1/oracle/oradata/payroll/standby/payroll3.ctl';
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ls.htm#1060804
    and If possible Please search google or this forums!
    Regards!

Maybe you are looking for