Creation of logical standby in 9i from physical standby

Hi all,
I want to create logical standby from physical standby in 9i. can anyone send a doc for this

As per the Oracle documents "You create a logical standby database by first creating a physical standby database and then transitioning it to a logical standby database"
Please take a look at the below URL.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm
Regards,
Sabdar Syed.

Similar Messages

  • Using streams to capture data from physical standby database.

    Does anybody know if it is possible to use streams to capture data from physical standby database instead of PROD database? The standby database is in read only mode. We use Oracle 11gR2.
    Thanks in advance.

    physical are closed : how will it managed the queues and overspill queues when target is not present? Also the data dictionary must reflect the primary but If you run capture, then you introduce rules that are not on primary: How ?

  • Transport Tablespace from Physical Standby in Oracle 10gr2 - 64 Bit

    Hi,
    How to Export Transport Tablespaces from Physical Standby Server - Oracle 10gr2 EE in Windows 2003 EE, Since Production Servers are in 24*7 Support to avoid make Read Only Tablespaces.
    Regards
    Harish

    Open your Physical Standby in read only mode and do your export. Then mount it back in managed recovery mode.

  • Creation of logical standby by shipping the  redologs from physical standby

    Hi all,
    I have to create a logical standby database using redo shipping from my PHYSICAL STANDBY while it is in mounted state .Is it really possible to do it??
    Please send me any docs regarding this to my mail id ([email protected])
    Thanx in advance

    It is possible to do what you ask by using cascaded destinations. See the Data Guard Manual (online at OTN) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14239/cascade_appx.htm#i636046
    for the information. This relies on the standby creating and re-transmitting redo log data.
    Hope this helps

  • Goldengate from physical standby with Active data guard or from logical standby - which is better?

    Hi,
    We have Oracle 11.2.0.4 and are currently using Active Data Guard on a physical standby. My boss wants me to use Goldengate
    to replicate several schema from Oracle to SqlSserver. She doesn't want to touch the Primary, which is in production. Would it be better
    to setup a Logical standby for Goldendate to use, in addition to the Physical standby? Or will it be sufficient to use the Physical standby?
    The application tables don't all have primary keys. I'm trying to decide if the Logical standby adds another layer of complexity or would
    introduce delays in getting the data from Oracle to Sqlserver.
    Thanks in advance,

    Hi,
    In this case I recommend you to use physical standby + Golden gate with ALO mode. You might have sligthly more trouble in logical standby. it means you might have more trouble at Goldengate's extract side.
    You said
    The application tables don't all have primary keys.
    so you have to add keycols on replicat side.
    I recommend you to add an index which should consist of keycols columns. it will be necessary for replicat performance.
    Best Regards

  • Drop a datafile from physical standby's control file

    Hi,
    I am trying to create a physical standby database for my production...
    1) I have taken cold backup of my primary database on 18-Nov-2013...
    2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
    3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database...
    When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
    SQL> recover standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    How to overcome this situation...
    Can i delete the entry for the newly added datafile from the backup control file ?
    When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be  open..
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      AUTO
    SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
    System altered.
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      MANUAL
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    Regards,
    Jibu

    Jibu wrote:
    Hi,
    I am trying to create a physical standby database for my production...
    1) I have taken cold backup of my primary database on 18-Nov-2013...
    2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
    3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database..
    Hi,
    What is your version?
    If you added new datafile or created new tablespace, take backup again for restore new created standby database.
    If your standby  database running well, DG configuration success, then this datafile will create on standby side, too.
    Set STANDBY_FILE_MANAGEMENT=AUTO best practice.
    When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
    SQL> recover standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
    ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    How to overcome this situation...
    Can i delete the entry for the newly added datafile from the backup control file ?
    Not need any delete datafile from standby side, you must recreate standby database, or you can  take RMAN backup and restore to standby  side again.
    When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be  open..
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      AUTO
    SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
    System altered.
    SQL> show parameter STANDBY_FILE_MANAGEMENT
    NAME                                 TYPE        VALUE
    standby_file_management              string      MANUAL
    SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
    ERROR at line 1:
    ORA-01109: database not open
    It is not logical, Physical  standby must be bit-for-bit same with Primary  database.
    Regards
    Mahir M. Quluzade

  • Creating logical/virtual connection object  from physical connection

    Can anybody help me what is creating logical/virtual connection object and how to create it from physical connection in java ??
    Thanks in advance...

    WHile you are waiting for an answer, you might want to review the related Oracle documentation:
    For 10g, all docco is at http://www.oracle.com/pls/db102/portal.portal_db?selected=3 and docco I suspect will help you is "Java Developer's Guide" and "JDBC Developer's Guide and Reference"

  • How to automate the purging of archivelogs on primary when backing up from physical standby?

    Hi,
    When configuring archivelog backups to run from my Active Standby database (11.2.0.3) I am running into an issue where the archivelogs on the primary database are not getting purged. This is resulting in the archiver hanging on the primary.
    run {
    allocate channel ch1 type 'sbt_tape'
    TRACE 0;
    setlimit channel ch1 maxopenfiles 8;
    backup
    filesperset = 32
    (archivelog  all   delete input );
    backup  current controlfile  spfile  ;
    My archivelog deletion policy is set as follows on both the primary and standby
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    When I run REPORT OBSOLETE from RMAN however, the primary database seems to have outdated information in it.
    I have also observed the following in the RMAN backup log:
    RMAN-08120: WARNING: archived log not deleted, not yet applied by standby.
    Do I need to perform additional configuration to automate the purging of archivelogs on the primary database or is there an issue with the backup options and / or deletion policy specified?
    Many thanks,
    Gary Allen
    DBA

    The primary and standby databases are in sync and have been for over a week now.
    Primary:
    SQL> select max(sequence#), applied from v$archived_log group by applied;
    MAX(SEQUENCE#) APPLIED
               268 NO
               267 YES
    Standby:
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
               268
    For some reason though, the primary controlfile is not being updated properly and when I run the RMAN REPORT OBSOLETE command the data is nearly a week old yet on the standby the same command retrieves up to date information:
    Primary:
    RMAN> report obsolete
    Backup Set           136    06-AUG-13
      Backup Piece       136    06-AUG-13          48ogk9ik_1_1
    Backup Set           138    06-AUG-13
      Backup Piece       138    06-AUG-13          4aogkqbm_1_1
    Backup Set           142    06-AUG-13
      Backup Piece       142    06-AUG-13          4eogl5i6_1_1
    Backup Set           144    07-AUG-13
      Backup Piece       144    07-AUG-13          4gogmc0a_1_1
    RMAN> report obsolete
    Standby:
    Backup Set           156    13-AUG-13
      Backup Piece       156    13-AUG-13          4uoh65o7_1_1
    Backup Set           159    13-AUG-13
      Backup Piece       159    13-AUG-13          51oh6d0r_1_1
    Backup Set           162    13-AUG-13
      Backup Piece       162    13-AUG-13          54oh6n8a_1_1
    Backup Set           165    13-AUG-13
      Backup Piece       165    13-AUG-13          57oh78qr_1_1

  • Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

    Hi All,
    I am in confusion how to create logical standby database from primary database using rman active database command.
    What i did:-
    Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
    Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
    Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
    The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
    I done the creation of logical standby database by converting physical standby to logical standby database
    I am following the below mentioned doc for the same:
    Creating a physical and a logical standby database in a DR environment | Chen Guang's Blog
    Kindly guide me how to work over the same or please provide me the steps of the same.
    Thanks in advance.

    Thanks for your reply
    I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
    But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
    My primary database pfile is:
    pc01prmy.__db_cache_size=83886080
    pc01prmy.__java_pool_size=12582912
    pc01prmy.__large_pool_size=4194304
    pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    pc01prmy.__pga_aggregate_target=79691776
    pc01prmy.__sga_target=239075328
    pc01prmy.__shared_io_pool_size=0
    pc01prmy.__shared_pool_size=134217728
    pc01prmy.__streams_pool_size=0
    *.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
    *.audit_trail='db'
    *.compatible='11.1.0.0.0'
    *.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='/u01/app/oracle/oradata'
    *.db_domain=''
    *.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
    *.db_name='pc01prmy'
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
    *.fal_client='PC01PRMY'
    *.fal_server='PC01SBY'
    *.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
    *.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
    *.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
    *.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='DEFER'
    *.log_archive_dest_state_3='DEFER'
    *.log_archive_max_processes=30
    *.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
    *.open_cursors=300
    *.pga_aggregate_target=78643200
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=236978176
    *.undo_tablespace='UNDOTBS1'
    My logical standby pfile is:-
    pc01ls.__db_cache_size=92274688
    pc01ls.__java_pool_size=12582912
    pc01ls.__large_pool_size=4194304
    pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    pc01ls.__pga_aggregate_target=79691776
    pc01ls.__sga_target=239075328
    pc01ls.__shared_io_pool_size=0
    pc01ls.__shared_pool_size=125829120
    pc01ls.__streams_pool_size=0
    *.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
    *.audit_trail='db'
    *.compatible='11.1.0.0.0'
    *.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='/u01/app/oracle/oradata'
    *.db_domain=''
    *.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
    *.db_name='pc01prmy'
    *.db_unique_name='pc01ls'
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
    *.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
    *.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
    *.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
    *.open_cursors=300
    *.pga_aggregate_target=78643200
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=236978176
    *.undo_tablespace='UNDOTBS1'
    Kindly advice over the same

  • Logical and Physical Standby Practice

    Hello Gurus
    I am now attempting to practice Oracle Data Guard and in this direction I understand since 10g we have logical standby server as well as a physical standby server. While I am gathering information and knowledge about the data guard as is and varisous modes and types possible with oracle 10g and 11g in specific, an attempt to upgrade my self and learn these set-ups and understand them in detail.. I come to you for some guidence..
    I am referring to Oracle Documentation for these details. At the same time I also approach you to share your experiences .. may be a link apart from the documentation of oracle which you might want to refer me to use as a quick reference.. some thing that a person like me .. fairly new to this set-up understand it and then attempt to come up with one..
    This is for my practise and learning purpose.
    Sarat.

    Logical Standby was already introduced in 9i. It differs from physical standby in the way, the redo protocol, transmitted from the primary, gets used to actualize the standby. With logical standby, you have SQL APPLY - basically, we try to generate the same SQL that was done on the primary from the redo protocol that was written on behalf of that SQL on the primary. That SQL then is done on the OPEN instance at the logical standby.
    In case of a physical standby, the redo protocol from the primary is used to do RECOVERY - called REDO APPLY - to actualize the standby.
    Since 10g, the sames protection levels can be achieved with logical or physical standby.
    Drawback of logical standby: Not all kinds of SQL and all datatypes are supported
    Drawback of physical standby: It is mounted (versions before 11g) while being recoverd - or in 11g, REDO APPLY in READ ONLY status is possible but comes with an extra charge (ACTIVE DATA GUARD feature).
    If you look on my Blog, I have some examples about creating physical & logical standby DBs
    Kind regards
    Uwe
    http://uhesse.wordpress.com

  • Physical Standby: RFS: 'Attach' request version mismatch

    I have a 10.1.0.4 database that I want to move to a new machine and also upgrade to 10.2.0.1. I'm trying to follow the instructions for using SQL Apply to perforn a rolling upgrade with minimal downtime. My understanding is that I must first create a physical standby, and then transition the physical standby to a logical standby. Well, my physical standby is failing. I see the following in the standby's alert log:
    RFS: 'Attach' request version mismatch
    Both databases have their COMPATIBLE parameter set to 10.1.0.2.
    As an aside, if I must first create a working physical standby, then why do I need to transition that standby to a logical standby? I mean, can't I just get the physical standby working, perform a switchover, and be done with it?

    I was confused. I thought I could just create a 10.2.0.1 standby for a 10.1.0.4 primary. The process, though, is to first get a working 10.1.0.4 (logical) standby for the 10.1.0.4 primary. At that point dbua can be used to upgrade the standby, and I can go from there.
    I'm sure everything will work, now that I understand the steps required.

  • Physical standby database fail-over

    Hi,
    I am working on Oracle 10.2.0.3 on Solaris SPARC 64-bit.
    I have a Dataguard configuration with a single Physical standby database that uses real time application. We had a major application upgrade yesterday and before the start of upgrade, we cancelled the media recovery and disabled the log_archive_dest_n so that it doesn't ship the archive logs to standby site. We left the dataguard configuration in this mode incase of a rollback.
    Primary:
    alter system set log_archive_dest_state_2='DEFER';
    alter system switch logfile;
    Standby:
    alter database recover managed standby database cancel;Due to application upgrade induced problems we had to failover to the physical standby, which was not in sync with primary from yesterday. I used the following method to fail-over since i do not want to apply any redo from yesterday.
    Standby:
    alter database activate physical standby database;
    alter database open;
    shutdown immediate;
    startupSo, after this step, the database was a stand alone database, which doesn't have any standby databases yet (but it still has log_archive_config parameter set and log_archive_dest_n parameters set but i have 'DEFER' the log_archive_dest_n pointing to the old primary). I have even changed the "archive log deletion policy to NONE"
    RMAN> configure archivelog deletion policy to none;After the fail-over was completed, the log sequence started from Sequence 1. We cleared the FRA to make space for the new archive logs and started off a FULL database backup (backup incremental level 0 database plus archivelog delete input). The backup succeded but we got these alerts in the backup log that RMAN cannot delete the archivelogs.
    RMAN-08137: WARNING: archive log not deleted as it is still neededMy question here is
    1) Even though i have disabled the log_archive_dest_n parameters, why is RMAN not able to delete the archivelogs after backup when there is no standby database for this failed-over database?
    2) Are all the old backups marked unusable after a fail-over is performed?
    FYI... flashback database was not used in this case as it did not server our purpose.
    Any information or documentation links would be greatly appreciated.
    Thanks,
    Harris.

    Thanks for the reply.
    The FINISH FORCE works in some cases but if there is an archive gap (though it didn't report in our case), it might not work some times (DOCID: 846087.1). So, we followed the Switch-over & Fail-Over best practices where it mentioned about this "ACTIVE PHYSICAL STANDBY" for a fail-over if you intend not to apply any archivelogs. The process we followed is the Right one.
    Anyhow, we got the issue resolved. Below is the resolution path.
    1) Even though if you DEFER the LOG_ARCHIVE_DEST_STATE_N parameter's on the primary, there are some situations where the Primary database in a dataguard configuration where it will not delete the archive logs due to some SCN issues. This issue may or may not arise in all fail-over scenarios. If it does, then do the following checks
    Follow DOCID: 803635.1, which talks about a PLSQL procedure to check for problematic SCN's in a dataguard configuration even though the physical standby databases are no available (i.e., if the dataguard parameters are set, log_archive_config, log_archive_dest_n='SERVICE=..." still set and even though corresponding LOG_ARCHIVE_DEST_STATE_N parameters are DEFERRED).
    If this procedure returns any rows, then the primary database is not able to delete the archivelogs because it is still thinking there is a standby database and trying to save the archive logs because of the SCN conflict.
    So, the best thing to do is, remove the DG related parameters from the spfile (log_archive_config, log_archive_dest_n parameters).
    After i made these changes, i ran a test backup using "backup archivelog all delete input", the archive logs got deleted after backup without any issues.
    Thanks,
    Harris.
    Edited by: user11971589 on Nov 18, 2010 2:55 PM

  • Oracle DataGuard - Standy Redo log on physical Standby db

    Hello Guys,
    A quick question on my 10.2.0.2 db with Windows 2003 x64 OSs.
    I have 2 machines - One for primary & the other for physical standby
    I have successfully setup DG with Real Time Apply and also tested switchover & failover scenarios and they work well and as expected...
    But I have a query which popped up when I was trying to set this up at home.
    I create the physical standby db by shutting the primary db and copying all the datafiles, tempfiles,online redo logs and then creating a standby control file which will be used for the physical standby db to start off with.
    After mounting the standby db, I tried to create standby redo logs files starting with Group 4 but I got error that standby group 4 already exists.
    Upon querying v$logfile view, I noticed that the standby redo logs that I created on primary are also showing up on the standby db which I understand is from the standby control file.
    So here is my quesiton: What is correct method of creating these standby redo logs on the standby database?
    I know that I could drop those 4 standby redo logs from the standby db and recreate them but all the DG docs online and the documents that I have referred say that I should create the standby redo logs on the standby as I did on the primary but how can this duplication be avoided i.e. from the standby control file?
    I know that I could use another method to create a hot backup such as RMAN etc...but I wanted to follow this way of shutting down the primary and copy the relevant database files.
    Any help appreciated...and thanks in advance guys!
    -Bharath

    so with the setup that I used, i.e. create a standby control file which contains info about the standby redo logs at the primary site, should I also copy over the standby redo logs from the primary to standby as I only copied the datafiles, tempfile(s) & online redo logs? But then the filenames of the standby redo logs will be the exact same as that of the primary. Will that cause any issue during a switchover/failover?
    I don't remember exactly how I did it when I got the whole thing working but I have a vague remembrance that I drop the std. redo log files entries from the std database and then recreate new ones with different filenames (as compared to primary).
    Thanks

  • FWSM move from Active/Standby to Active/active

    Hi there,
    we have some FWSM installed in 6500 with many contexts in them.  They are at the moment configured as Active/Standby and in production.  But we have noticed that whenever a backup is run which goes through some of the contexts, the FWSM start counting errors which was already determined to be an oversubscription issue.  So, while we wait for the new ASA 5585X to arrive and finally replace them, we want to mitigate the issue by configuring the FWSM as Active/Active and move the contexts for backup traffic to the other box (keeping the production contexts in the other one).
    My question is, can this be done without impacting the production traffic?  Or as soon as we enable the active/active by the configuration of the groups and assignments of the contexts, the traffic will be impacted and we will produce an outage to the network?
    Thanks in advance for your help.
    Regards,
    Paula

    So no answers?
    Just one to update why had problem here: we need to to pull changes from Physical StandBy, because of performance reasons we cannot afford to reload every table with full refresh, we only want to get changes. At first I thought that it will be easy just create materialized view log and do basic replication, but in Physical StandBy we cant do it

  • Physical standby failed to start MRP process

    Hi,
    I have a qa db which is in ASM. I have a qa standby which is a physical standby also in ASM. I added space to the primary. Unfortunately, the standby diskgroup did not have enough space and standby mrp process crashed. I edited the primary data files to release some space and tried to restart the standby but it does not seem to work.
    What next?

    Er, Can you provide more information?
    Like maybe some details from the alert logs?
    Or maybe even the error message you get when you try to restart the standby
    The more information the easier it is to debug at a distance.
    jason.
    http://jarneil.wordpress.com

Maybe you are looking for