Manual Standby and Archlogs application

Hi There,
I need to set up a manual standby database for one of our production databases. We are using oracle 11g (11.1.0.7) 64x STANDARD EDITION on Windows 2008 server 64x.
I shutdown the database, copied the data files and redo logs to a new server (same directories structure to the production database); I created a standby controlfile and a pfile and copied both across to the new host.
I created the oracle windows service on the new machine and started the database as follows:
C:\Users\oracle>
C:\Users\oracle>SQLPLUS "/AS SYSDBA"
SQL*Plus: Release 11.1.0.7.0 - Production on Tue Apr 13 15:04:53 2010
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to an idle instance.
SQL> STARTUP PFILE='C:\oracle\product\11.1.0.7\database\INITSTDBT.ORA' NOMOUNT;
ORA-32006: STANDBY_ARCHIVE_DEST initialization parameter has been deprecated
ORACLE instance started.
Total System Global Area  542814208 bytes
Fixed Size                  2131248 bytes
Variable Size             419433168 bytes
Database Buffers          117440512 bytes
Redo Buffers                3809280 bytes
SQL>
SQL>
SQL> SELECT STATUS FROM V$INSTANCE;
STATUS
STARTED
SQL> alter database mount standby database;
Database altered.The production database has forced logging enabled in it so that we can capture all the DDL statemtents.
We created a dummy schema, a dummy table (with few rows); issued a commit, and then switched the logs few times to create the necessary archive logs. We then manually moved the archive logs to the new standby host, and put them under the appropriate directory (D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13).
Now we tried to recover the database by applying the new shipped logs:
SQL> recover standby database
ORA-00279: change 606666 generated at 04/13/2010 14:37:19 needed for thread 1
ORA-00289: suggestion :
D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_%U_.ARC
ORA-00280: change 606666 for thread 1 is in sequence #46
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
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: 'D:\ORACLE\ORADATA\STDBT\SYSTEM01.DBF'So we thought we'll try the recovery again by manually putting the filename in:
SQL> recover standby database
ORA-00279: change 606666 generated at 04/13/2010 14:37:19 needed for thread 1
ORA-00289: suggestion :
D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_%U_.ARC
ORA-00280: change 606666 for thread 1 is in sequence #46
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_5W9W3LT3_.ARC
ORA-00279: change 608376 generated at 04/13/2010 15:30:10 needed for thread 1
ORA-00289: suggestion :
D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_47_%U_.ARC
ORA-00280: change 608376 for thread 1 is in sequence #47
ORA-00278: log file
'D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_5W9W3LT3_.
ARC' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_47_5W9W7P6D_.ARC
ORA-00279: change 608426 generated at 04/13/2010 15:32:20 needed for thread 1
ORA-00289: suggestion :
D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_48_%U_.ARC
ORA-00280: change 608426 for thread 1 is in sequence #48
ORA-00278: log file
'D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_47_5W9W7P6D_.
ARC' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.So, the issue here is that even though the archive logs did exist in the correct directory, when we hit enter to accept the default, oracle didn't find the logs and it was looking for a file with the format "O1_MF_1_46_%U_.ARC" instead of "O1_MF_1_46_5W9W3LT3_.ARC" and so the recovery failed.. How can we fix this so that oracle will detect the correct archlog name so that when we automate the applying of the logs it will work (and we don't have to do enter them manually one by one)?
SQL> ALTER DATABASE ACTIVATE STANDBY DATABASE;
Database altered.
SQL> select status from v$instance;
STATUS
MOUNTED
SQL>
SQL>
SQL>
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16433: The database has not been opened in read-write modeAnother question, once we activated the standby database, we tried to open it but it failed with above error; do we have to shut it down 1st and then do a normal STARTUP command? or do we have to open it with resetlogs??
If someone can shed some light here that will be great.
Thanks
Edited by: rsar001 on Apr 13, 2010 4:27 PM

SQL> show parameter log_archive_dest
NAME                                 TYPE        VALUE
log_archive_dest                     string
log_archive_dest_1                   string
log_archive_dest_10                  string
log_archive_dest_2                   string
log_archive_dest_3                   string
log_archive_dest_4                   string
log_archive_dest_5                   string
log_archive_dest_6                   string
log_archive_dest_7                   string
log_archive_dest_8                   string
log_archive_dest_9                   string
log_archive_dest_state_1             string      enable
log_archive_dest_state_10            string      enable
log_archive_dest_state_2             string      enable
log_archive_dest_state_3             string      enable
log_archive_dest_state_4             string      enable
log_archive_dest_state_5             string      enable
log_archive_dest_state_6             string      enable
log_archive_dest_state_7             string      enable
log_archive_dest_state_8             string      enable
log_archive_dest_state_9             string      enable
SQL> show parameter recover
NAME                                 TYPE        VALUE
db_recovery_file_dest                string      D:\oracle\flash_recovery_area
db_recovery_file_dest_size           big integer 2G
recovery_parallelism                 integer     0
SQL>

Similar Messages

  • Difference between Manual Standby and Data Guard Broker..

    hi,
    could any let me know any usefull docs which help to understand the difference between manual dr and data guard broker?
    thanks,

    >
    could any let me know any usefull docs which help to understand the difference between manual dr and data guard broker?
    >
    Without Data Guard Broker:
    http://www.oracle.com/pls/db112/to_toc?pathname=server.112/e17022/toc.htm
    With Data Guard Broker:
    http://www.oracle.com/pls/db112/to_toc?pathname=server.112/e17023/toc.htm
    See especially why you want to use the broker:
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17023/concepts.htm#i1013106
    In short: You should have a good reason if you do not use the broker, because it is the officially recommended way to maintain Data Guard. It is even required for some features like Fast-Start Failover.
    Kind regards
    Uwe Hesse
    http://uhesse.wordpress.com

  • Datafile issues in manual standby database

    Hi all,
    oracle - 10gR2
    OS - RHEL 2.6
    We have primary and standby database setup using manual methods('rsync') to send archive logs from primary to standby database and they are applied there. Today I have created a new datafile in primary and seen that the same is not replicated in standby( i was not aware of the functionality of this kind of setup) later I have seen that "standby_file_management parameter is set to MANUAL".
    I have seen the following message in standby alert log(not disabled the archive log application script in satndby),
    "Media Recovery Log /u01/app/oracle/oradata/bmprod/archivelog/1_1761_703415336.arc
    File #6 added to control file as 'UNNAMED00006' because
    the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
    The file should be manually created to continue.
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail"
    Later I have copied the required file from primary to standby database(now I have disabled the archive log application script in standby), and renamed the datafile 'UNNAMED00006' to 'desired one' and restarted the archive log application script. I have seen the following messages,
    "ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 6 needs more recovery to be consistent
    ORA-01110: data file 6: '/u02/app/oracle/oradata/bmprod/BMTEST.dbf'"
    Now I am unable to figure out what I should do to come out of this situation. Atleast tell me this condition is not worse than I thought(I think that the standby database should be recreated).
    Any help is appreciated.......
    regards
    Edited by: techfeud on Jan 18, 2010 11:26 PM

    Hi,
    when you set the standby_file_management parameter as mannual then , if you create any datafile or adding it to the tablespace then you should mannaully run the command on the standby side , if its auto then auto matically it will create the file over in the respective locationa and with the name what you have used to create the datafile on the primary side,
    as the parameter value is mannual ypu need to create the datafile over the standby side and then performt the recovery,
    Farhan.

  • I want to remove the COnlineBank, OnlineBank and csample applications from my application and web server.

    How can I safely do this on Solaris? I've tried "iasdeploy removeapp" and "iasdeploy removemodule" with no luck. I want to clear all of this demo stuff out to make both the web and app server look more production like.
    Thanks
    Eric

    Eric,
    these applications are applogics which are not controlled by the
    iasdeploy tool. Unfortunately, there is no tool available to remove
    these applications for you. What you can do is to manually remove all
    their entries, but be careful if you do that. If you remove the wrong
    keys you might break your ias installation, so be warned and make sure
    you backup the whole ias registry before attempting to remove anything.
    Eric Coleman wrote:
    >
    I want to remove the COnlineBank, OnlineBank and csample applications
    from my application and web server.
    How can I safely do this on Solaris? I've tried "iasdeploy removeapp"
    and "iasdeploy removemodule" with no luck. I want to clear all of
    this demo stuff out to make both the web and app server look more
    production like.
    Thanks
    Eric
    Try our New Web Based Forum at http://softwareforum.sun.com
    Includes Access to our Product Knowledge Base!--
    Han-Dat Luc ([email protected])
    Senior Consultant
    SUN Professional Services (iPlanet)
    o .
    o .
    O _ ____ _ _
    (_) _ \| | __ _ _ __ ___| |_ TM
    | | |_) | |/ _` | '_ \ / _ \ __|
    | | __/| | (_| | | | | __/ |_
    |_|_| |_|\__,_|_| |_|\___|\__|
    e-commerce solutions
    Sun Microsystems Australia Pty Ltd

  • How to Create Manual Standby for a Oracle 11g RAC with ASM to Single Instan

    Hi All,
    I have a task to configure a Single Instance Standby Database with ASM for 2-node Primary RAC+ASM database.
    Version using : 11.1.0.6 Oracle 11g --- *" STANDARD EDITION "* Please note datagaurd will not be supported in standard edition.
    Primary database - 2 -Node RAC using ASM storage (All datafiles, redologs, controfile and archive logs)
    Need to setup a single instance standby database manually and than using scripts to transfer the archive logs from primary server to standby server to do recovery time to time.
    Please let me know if there are any configuration document(s) which can help me to set the manual standby? or need your kind help to give your valuable ideas how to go in above situation.
    Thanks in advance

    Niall Litchfield wrote:
    El DBA wrote:
    Well if the archive logs are stored in ASM on the primary nodes, you almost definitely want to be using RMAN to access them. Then to transfer between primary and standby there are many options, this is essentially the step that Data Guard takes care of - so if you (and I) are running Standard Edition, this is the part to "worry" about.
    I'm not really sure what you mean by this:
    As in standard edition the archive destination will be on ASMI don't think the Edition of Oracle (Standard or Enterprise) dictates where and how you store your archive logs, but it's possible I've misunderstood what you mean...SE dictates that database storage for RAC will be ASM, including archive log files. Anything else is not officially supported. I haven't tested but it may be that you can use LOG_ARCHIVE_DUPLEX_DEST to specify a local filesystem for archive log files as well.
    If that doesn't work you'll have to script rman "backup as copy" jobs regularly and then transport the results of that.
    Niall Litchfield
    http://www.orawin.info/
    By the way, it seems Robert has been pretty helpful, it's polite to give him some points dude. And since this is your thread, not mine, give him a "helpful" from me too :p
    El DBA
    Incidentally if you are forced down the RMAN backup as copy route then this will likely throw your current backup retention strategy somewhat, you'll need to think carefully about when an archivelog can be deleted following backup, how many times it might be backed up and so on. I do understand, and have argued for, the use of SE RAC. I also understand and have argued for and implemented manually managed standby a number of times. However by the time your primary database is a RAC instance and you need a standby for DR etc then you really have to look very seriously at whether Standard Edition is still the right investment or not. You will be spending a lot of DBA time managing and troubleshooting this, and you will find that it is less reliable than the off the shelf solution. I suspect that you are very close to the point where an EE installation becomes a worthwhile investment here.
    Niall Litchfield
    http://www.orawin.info/

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

  • Single-instance manual standby for a three-node RAC database

    Hi all,
    I am wondering how it is possible to create a manual standby database for a rac primary database.
    Oracle versione is standard edition 11.1.
    I have experience creating and managing manual standby for single-instance database; I am wondering if and how I can instruct the single-instance standby database to discover and apply the three redo threads that I will copy from the primary site to the standby site.
    Should I use rman to catalog all the archived log on the standby site ?
    Should I configure many LOG_ARCHIVE_DEST_n parameters to point to many different path, one for each primary instance (i.e. one for each redo thread), and let rman automagically discover all the archived logs ?
    Should I configure only LOG_ARCHIVE_DEST_1 , put archivelogs from all threads in the same folder, and let rman automagically discover all the archived logs ?
    Thanks for every answer!
    Andrea

    Hi,
    indeed i catalog all transfered archive logs in front of the recover process.
    During the tests i believe (iirc) i was unable to recover from transfered archivelogs without catalog them first. But this statement is out of my mind, i am not 100% sure for this, sorry.
    Some more details.
    Because it is a standard edition, i have to use on the RAC side ASM. So our normal scripts to transfer archivelogs from primary to standby are obsolete.
    So i decided to put the whole standby thing into the database. Now the primary database uses external scheduler jobs to do the work. The standby side is not using ASM, so there is no need to handle the logs in any special way.
    The steps are:
    1. Get SCN from primary and standby
    2. Transfer the logs for the gap from ASM to "normal" filesystem.
    3. Transfer (and compress, if not in LAN) to standby archive dest
    4. Catalog on standby side
    5. Recover on standby side
    6. Delete on normal filesystem (on both sides, but on standby with a delay of 2 days just to be sure)
    The steps on the standby side are both using the primary scn from step 1 as a parameter to avoid error messages during the catalog or recover call.
    Hth
    Joerg

  • DB link problem between active Data Guard and report application database

    My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
    I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
    SQL> select name, database_role, open_mode from v$database;
    NAME DATABASE_ROLE OPEN_MODE
    ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
    Problem detail is below
    I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
    SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
    Database link created.
    But when I run a query using db link from my report application database I got this below error.
    ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
    ORA-02063: preceding line from DATADB_LINK
    Then I check Active Data Guard database alart log file and get below error
    ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
    But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
    So is it a problem of DB link between active Data Guard and other database?

    Fazlul Kabir Mahfuz wrote:
    My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
    I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
    SQL> select name, database_role, open_mode from v$database;
    NAME DATABASE_ROLE OPEN_MODE
    ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
    Problem detail is below
    I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
    SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
    Database link created.
    But when I run a query using db link from my report application database I got this below error.
    ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
    ORA-02063: preceding line from DATADB_LINK
    Then I check Active Data Guard database alart log file and get below error
    ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
    But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
    So is it a problem of DB link between active Data Guard and other database?
    Check this note which is applicable for your environment
    *ORA-01555 on Active Data Guard Standby Database [ID 1273808.1]*
    also
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8908307196113

  • 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

  • Oracle manually standby database with standard edition

    Hi, I want to have a plan for disaster. I'm triying with two virtual machines with oracle database 10g on suse linux. I follow these URLs
    http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
    http://oramdq.blogspot.com/2009/05/como-configurar-un-sistema-de-alta.html
    and it look that work all right.
    I know that with manually standby database we applied archived logs, and so, we don't propagate any physical changes to secondary database (standby), for example, if I create a new tablespace, or adding a new datafile to an existing tablespace, it don't work in the secondary database.
    Anyone does know how is the better way to apply the physical changes??
    Anyone have any scripts to do that?
    Thanks in advance.

    HI,
    Add the STANDBY_FILE_MANAGEMENT = AUTO to the primary parameter file, it will solve it.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams209.htm]
    Reagds,
    Vijayaraghavan K
    Edited by: Vijayaraghavan Krishnan on Feb 24, 2010 7:19 PM

  • Manual Standby Database

    Hi,
    I have ORACLE 10.2.0.3.0 64 bit SE1 running on a RHEL4 server. I have a backup server on which I need to create a manual standby database for a (poor man's) high availability environment. We have explored RAC, Dataguard etc and given them up for cost considerations. We understand the potential of up to 15 minutes data loss. I know the general steps necessary to set up the manual standby server. For example, I know I need a cold (or hot) backup of the primary to reset my standby database. Then I need to create the standby control file. I need to write deamon processes to ship the archive logs to the standby server and apply those logs to the database. I am new to ORACLE and would appreciate some specific advice.
    (1) Should I use DBCA to create the database on the standby server first? My impression is that using DBCA will set up the enterprise manager, isqlplus and the relevevant entries in oratab etc on the standby server. If I simply install ORACLE 10g on the standby and copy the backup files from the primary server, I will not have access to the database tools that come with ORACLE 10g.
    (2) Can someone please share the scripts you may have written? or point me to some skeleton scripts?
    (3) What are the failure points for manual standby databases? What do I need to pro-actively monitor? For example, if the logs are not being applied properly to the standby database for a prolonged period, I would like to know about it.
    (4) What are the procedures for recovering from a failed master database?
    (5) Where can I learn more about the subject? I will need specific commands to setup the standby. Are these procedures documented somewhere?
    Thanks!
    - Rajesh

    Try this one Manual Standby Database under Oracle Standard Edition
    Or search the subject on google, many results.
    No, you will not create "standby" using DBCA, you need to use primary's backup to restore on standby server and constantly recover.

  • Manual Standby Database from EE to SE1

    Can I do a Manual Standby Database from Oracle Enterprise edition (EE) to Oracle Standard Edition One (SE1)?

    Hi,
    You can created a manual standby for EE, But you need to purchase a seperate licence for standby database also.
    See oracle licencing manul in oracle documentation.
    Thanks and Regards,
    Satish.G.S

  • Manual Standby Database not in sync with missing archivelogs

    Hello,
    OS: Solaris
    DB: Oracle 11.2.0.1 EE
    Not Using ASM or RAC
    I have a Production database that is in archivelog mode and a Standby DR server.
    Both servers (Prod, Standby) have exact same structure and db name/version.
    We manually scp archive logs and recover them to a manual standby database via SQL Scripts "cron". (I.E. set autorecovery on; recover standby database;)
    We recently got out of sync with our log files and have not been applying them to the standby. As part of Prod Maintenance, these log files were deleted and are not available anymore.
    I've tried several ways to "rebuild" our standby database. I have tried to Shutdown prod, backup all the db files and scp them to standby, re-create standby controlfile and startup mount and recover standby.
    Every time I try to apply a new archive log via recover standby, these are the errors:
    ORA-00279: change 211077622 generated at 1/27/2012 12:18:42 needed for thread 1
    ORA-00289: suggestion : /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
    ORA-00280: change 211077622 for thread 1 is in sequence #69486
    ORA-00308: cannot open archived log '/oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-10879: error signaled in parallel recovery slave
    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: '/oradevices/PROD/oraPRODsystem1.dbf'
    When I check v$log_history, the new logs have not been applied.
    I've also tried the "Restore from incremental backup via SCN" method with same results.
    Is there a way to re-create the standby clean and ensure that the log chain that is currently broken gets fixed or reset?
    I would eventually like to get DataGuard in here, but that's not the case at the moment.
    Thanks for your suggestions.
    -Dav

    if you are using the cold backup to create the standby database, Check that have you followed the following steps or not.
    1. remove
    all the datafiles and controlfiles from the standby database.
    2. Create a new standby controlfile of the production for standby using the following cmd
    'alter database create standby controlfile as 'Location';'
    3. move the new controlfile to standby database server location as specified in initialization parameter file.
    4. Restore all the datafiles to its appropriate loaction which was taken through cold backup.
    5. startup nomount
    6. alter database mount standby database;
    7. recover standby database.
    scp the archive log sequence that is asked by the database, from production.
    You can try this steps.

  • Manual Standby Recovery

    Hi Friendz,
    Oracle Db 9i
    I have configured a manual standby database(I am not using Dataguard or "create standby database" command ) I only copy the cold backup to the target recovery server. I have been applying archive logs to it for a week now. I use the "recover automatic database using backup controlfile" command.
    My problem is, when I try to "alter database open resetlogs" so I can test if I can open it, It is asking for the next archive log and message "that the system01.dbf needs recovery". How can I open my standby database and force it to stop recovery?
    Thanks a lot
    Ms Inday

    ALTER DATABASE RECOVER  automatic database using backup controlfile
    Media Recovery Start
    Sun Dec 19 18:33:14 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40621.dbf
    Sun Dec 19 18:33:14 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40622.dbf
    Sun Dec 19 18:33:18 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40623.dbf
    Sun Dec 19 18:33:22 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40624.dbf
    Sun Dec 19 18:33:25 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40625.dbf
    Sun Dec 19 18:33:26 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
    Errors with log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
    ORA-279 signalled during: ALTER DATABASE RECOVER  automatic database using b...
    Sun Dec 19 18:33:26 2010
    ALTER DATABASE RECOVER    CANCELThis is the alert when I try to open it using resetlogs.
    ALTER DATABASE   MOUNT
    Sun Dec 19 19:29:56 2010
    Successful mount of redo thread 1, with mount id 4188096816
    Sun Dec 19 19:29:56 2010
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Sun Dec 19 19:29:56 2010
    ALTER DATABASE OPEN
    ORA-1589 signalled during: ALTER DATABASE OPEN...
    Sun Dec 19 19:30:51 2010
    alter database open noresetlogs
    Sun Dec 19 19:30:51 2010
    ORA-1588 signalled during: alter database open noresetlogs...
    Sun Dec 19 19:31:18 2010
    alter database open resetlogs
    Sun Dec 19 19:31:20 2010
    ORA-1113 signalled during:  alter database open resetlogs...
    Sun Dec 19 19:32:00 2010
    ALTER DATABASE RECOVER  database
    Sun Dec 19 19:32:00 2010
    Media Recovery Start
    Sun Dec 19 19:32:00 2010
    Media Recovery failed with error 1610
    ORA-283 signalled during: ALTER DATABASE RECOVER  database  ...
    Sun Dec 19 19:32:56 2010
    ALTER DATABASE RECOVER  database using backup controlfile
    Sun Dec 19 19:32:56 2010
    Media Recovery Start
    ORA-279 signalled during: ALTER DATABASE RECOVER  database using backup cont...
    Sun Dec 19 19:33:12 2010
    ALTER DATABASE RECOVER    CANCEL
    Sun Dec 19 19:33:12 2010
    Media Recovery Cancelled
    Completed: ALTER DATABASE RECOVER    CANCEL
    Sun Dec 19 19:33:31 2010
    alter database open resetlogs
    Sun Dec 19 19:33:31 2010
    ORA-1113 signalled during: alter database open resetlogs...
    Sun Dec 19 19:34:15 2010Thanks

  • How to validate a manual standby

    Hi all,
    I am setting up a manual physical standby and I want to periodically check the standby database for physical and logical corruption.
    I am not sure what is the best way to do it:
    1) should I only use dbv?
    2) should I open the database read only and use RMAN "validate database check logical ;" ?
    3) should I open the database read only and use anlter table ... validate structure cascade ; for every table?
    4) Do steps 2 and 3 do the same checks?
    Thanks,
    Andrea

    user585511 wrote:
    Hi all,
    I am setting up a manual physical standby and I want to periodically check the standby database for physical and logical corruption.
    I am not sure what is the best way to do it:
    1) should I only use dbv?
    2) should I open the database read only and use RMAN "validate database check logical ;" ?
    3) should I open the database read only and use anlter table ... validate structure cascade ; for every table?
    4) Do steps 2 and 3 do the same checks?May be physical corruption can occur, But logical corruption only on standby have less chances..
    as always, Standby is image copy so if any logical corruption in primary you will have those in standby too..
    May be due to some mount point issues (or) any other there is chance for physical corruption.
    So either you can go for DBV, Even you can check by RMAN too.
    Better, if you perform some tests like creating a user with tables(schema) & open standby and keep track the status. I think if you able to open and count is same. You are fine.
    Another point , If any corruption in your database, MRP process will be died and no recovery will be performed, So until unless you able to perform Recover, then there is no issue at the most.+
    Edited by: CKPT on May 18, 2012 4:22 PM

Maybe you are looking for