Large import on dataguard (Physical Standby 11.2 )

Hi experts,
I have to import a great database (50 Gigabytes) (with impdp) which should be configured with a standby database.
My Question:
Should  I make the import before or after the configuration of the standby database?Thanks & regards
hqt200475
Edited by: hqt200475 on Sep 7, 2011 8:55 AM

Do the IMPORT first.
If you don't you risk messing up the FRA on both the Primary and the Standby side. The redo will stop applying the second the FRA hits the limit on the Standby or worse yet a day or two later when you think you are in the clear. Even if for some reason you don't use FRA shipping all that redo isn't a good idea on a new Data Guard system. You might have another issue and you just compound it by doing an import of this size. On most systems you would be adding an additional 500 plus redo logs to the mix.
Also you can duplicate the Standby database using RMAN after the import very easily.
I probably wait a least a few days after I imported on the future Primary before I built the Standby.
I have a solid duplicate document and will share if you decided to go that route.
Best Regards
mseberg

Similar Messages

  • Large import on dataguard (logical standby) 11.2

    The action I'll like to perform is to do a large import on the production enviroment without that this import will be applied on the logical-standby environment (because its to large for the standby envoriment to keep it up) and after that I will do this same import on the logical standby.
    What the most common way to do this large import on logical standby enviroment after this is performed on the produnction ?
    something like ;
    alter session disable guard;
    do the import
    alter session enable guard;
    alter database start logical standby apply skip failed transaction;
    thanks in adv

    if the table you are importing will have changes made to it AFTER the import and you want those changes replicated to the logical standby then you have to actually re-sync the table FROM primary.
    Step 1. Skip the table DML on logical
    EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'DML', schema_name => 'schema', object_name =>'table_name');
    Step 2. Import the table into primary
    Step 3. Stop Logical Standby apply
    alter database recover managed standby database cancel;
    Step 4. Get the restart_scn on Logical Standby to use for the flashback scn with exp_dp
    SELECT RESTART_SCN FROM V$LOGSTDBY_PROGRESS;
    Step 5. On Primary export the table using the restart_scn from logical
    expdp DIRECTORY=DP_DIR DUMPFILE=sync_table.dmp LOGFILE=sync_table.log tables=schema.table_name flashback_scn=6146375299983
    Step 6. On Logical import the table
    impdp DIRECTORY=DP_DIR dumpfile=sync_table.dmp TABLE_EXISTS_ACTION=REPLACE
    Step 7. Unskip the table and start the apply on logical standby
    EXECUTE DBMS_LOGSTDBY.UNSKIP(stmt => 'DML', schema_name => 'schema', object_name =>'table_name');
    alter database start logical standby apply immediate;
    Now the tables should both be synced up and any new changes made to the table on primary will replicate correctly to logical.
    Note that oracle must maintain a read consistent copy of the table as of the SCN you specified, depending on how long it takes to export you may run into rollback segment issues. I'd plan on doing this during the least busy time on your db and increase undo to avoid ORA-01555

  • Oracle 10g Dataguard Physical Standby Database

    When I set my dataguard group to "MAXIMIZE AVAILABILITY" the protection level is always RESYNCHRONIZATION.
    It's normal ?
    SQL> SELECT PROTECTION_MODE, PROTECTION_LEVEL, DATABASE_ROLE FROM V$DATABASE;
    PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
    MAXIMUM AVAILABILITY RESYNCHRONIZATION PHYSICAL STANDBY
    SQL> show parameter log_archive_dest_2
    NAME TYPE VALUE
    log_archive_dest_2 string SERVICE=PIJ10G2 LGWR SYNC AFFIRM
    SQL> show parameter log_archive_dest_state_2;
    NAME TYPE VALUE
    log_archive_dest_state_2 string ENABLE

    this is my log on primary db :
    Thread 1 advanced to log sequence 422
    Current log# 1 seq# 422 mem# 0: /oradata/orapij10g/redologs/PIJ10G/redo01.log
    Wed Oct 1Thread 1 cannot allocate new log, sequence 423
    Private strand flush not complete
    Current log# 1 seq# 422 mem# 0: /oradata/orapij10g/redologs/PIJ10G/redo01.log
    Wed Oct 17 16:24:51 2007
    Destination LOG_ARCHIVE_DEST_3 is SYNCHRONIZED
    LNSc started with pid=34, OS id=21052
    Wed Oct 17 16:24:56 2007
    Destination LOG_ARCHIVE_DEST_3 is UNSYNCHRONIZED
    Wed Oct 17 16:24:56 2007
    Errors in file /oracle/ora10g/admin/PIJ10G/bdump/pij10g_lgwr_26248.trc:
    ORA-16086: Message 16086 not found; No message file for product=RDBMS, facility=ORA
    LGWR: Failed to archive log 2 thread 1 sequence 423 (16086)
    Thread 1 advanced to log sequence 423
    Current log# 2 seq# 423 mem# 0: /oradata/orapij10g/redologs/PIJ10G/redo02.log
    I don't understand this error message. How can solve my probleme ?

  • RAC & DataGuard (Physical Standby)

    Hello all,
    I'm trying to get a high level overview of how RAC & DataGuard would behave in the following configuration. I've written down my understanding of how things would work. Please correct me if I'm wrong.
    1) 2 node RAC (Primary Database) with a single instance physical standby.
    a) Same standby related init.ora parameters would have to configured on both primary rac nodes.
    b) The redo apply service at the standby would merge the redo from the 2 threads from the primary and apply it to the standby to keep it in sync.
    c) During switch over only one primary RAC instance should be up besides the standby instance.
    d) During switch back again only one primary RAC instance should be up besides the standby instance.
    e) During failover ofcourse both primary instances would be down which warrants the fail over.
    2) 2 node RAC (Primary) with a 2 node physical standby
    This where it gets complex and I'm not really sure how a,b,c,d,e would be in this scenario. Appreciate if you could shed some light on this and list what
    a,b,c,d,e would look like in this scenario.
    I'm assuming that only one instance in the standby RAC should be up when the standby is in RAC configuration for the redo apply to work.
    Also, if there is a white paper that details step by step procedure for setting up the above 2 scenarios, please let me know. So far I was able to find only the MAA white paper but that was not very helpful. If you can prescribe a good book for RAC & DataGuard that would be great too..
    Thanks for your help

    >
    1) 2 node RAC (Primary Database) with a single instance physical standby.
    a) Same standby related init.ora parameters would have to configured on both primary rac nodes.Usually rac nodes share their spfile on a shared diskvolume or through ASM. So they have identical DG parameter anyway
    b) The redo apply service at the standby would merge the redo from the 2 threads from the primary and apply it to the standby to keep it in sync.Correct
    c) During switch over only one primary RAC instance should be up besides the standby instance.
    Sounds logical to me
    Edit: In fact during normal operation both RAC nodes are up, so during switchover they are both active too
    It is the configuration that matters. As soon as the standby is becoming primary, it might be that it talks only to one RAC node for its log-apply files
    d) During switch back again only one primary RAC instance should be up besides the standby instance.That single was the only one running in step c.
    e) During failover ofcourse both primary instances would be down which warrants the fail over.Correct. Keep in mind that during a failover the RAC config would be deconfigured from the DG setup and has to be added back again as standby.
    You might have to take a look at: http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimarySingleInstancePhysicalStandby.pdf
    >
    2) 2 node RAC (Primary) with a 2 node physical standby
    This where it gets complex and I'm not really sure how a,b,c,d,e would be in this scenario. Appreciate if you could shed some light on this and list what
    a,b,c,d,e would look like in this scenario.
    I'm assuming that only one instance in the standby RAC should be up when the standby is in RAC configuration for the redo apply to work.
    No. RAC primary to RAC Standby would mean both nodes are up on both side. PrimNode1 send its redo logs to StandbyNode1 and the same for PrimNode2 and StandbyNode2
    Have a look here: http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
    HTH,
    FJFranken
    My Blog: http://managingoracle.blogspot.com
    Edited by: fjfranken on 16-jul-2010 1:13

  • Dataguard physical standby archive log question

    Hi all,
    I will try to keep this simple..
    I have a 4 node RAC primary shipping logs to a 2 node physical standby.
    On the primary when I run 'alter system archive log current' on an instance I only see 1 log being applied on the standby, that is by querying v$archived_log.
    If I run the following on the standby:
    select thread#,sequence#,substr(name,43,70)"NAME",registrar,applied,status,first_time from v$archived_log where first_time
    in
    (select max(first_time) from v$archived_log group by thread#)
    order by thread#
    I get:
    THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
    1 602 thread_1_seq_602.2603.721918617 RFS YES A 17-jun-2010 12:56:58
    2 314 thread_2_seq_314.2609.721918627 RFS NO A 17-jun-2010 12:56:59
    3 311 thread_3_seq_311.2604.721918621 RFS NO A 17-jun-2010 12:57:00
    4 319 thread_4_seq_319.2606.721918625 RFS NO A 17-jun-2010 12:57:00
    Why do we only see the max(sequence#) having been applied and not all of them?
    This is the same no matter how many times I archive the current log files on any of the instances on the primary and also the standby does not have any gaps.
    Hope this is clear..
    any ideas?
    jd

    ok output from gv$archived_log on standby BEFORE 'alter system archive log current' on primary
    THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
    1 679 thread_1_seq_679.1267.722001505 RFS NO A 18-jun-2010 11:58:22
    1 679 thread_1_seq_679.1267.722001505 RFS NO A 18-jun-2010 11:58:22
    2 390 thread_2_seq_390.1314.722001507 RFS NO A 18-jun-2010 11:58:23
    2 390 thread_2_seq_390.1314.722001507 RFS NO A 18-jun-2010 11:58:23
    3 386 thread_3_seq_386.1266.722001505 RFS YES A 18-jun-2010 11:58:22
    3 386 thread_3_seq_386.1266.722001505 RFS YES A 18-jun-2010 11:58:22
    4 393 thread_4_seq_393.1269.722001507 RFS NO A 18-jun-2010 11:58:23
    4 393 thread_4_seq_393.1269.722001507 RFS NO A 18-jun-2010 11:58:23
    Output from v$archived_log on standby AFTER 'alter system archive log current' on primary
    THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
    1 680 thread_1_seq_680.1333.722004227 RFS NO A 18-jun-2010 11:58:29
    1 680 thread_1_seq_680.1333.722004227 RFS NO A 18-jun-2010 11:58:29
    2 391 thread_2_seq_391.1332.722004227 RFS NO A 18-jun-2010 11:58:30
    2 391 thread_2_seq_391.1332.722004227 RFS NO A 18-jun-2010 11:58:30
    3 387 thread_3_seq_387.1271.722004225 RFS NO A 18-jun-2010 11:58:28
    3 387 thread_3_seq_387.1271.722004225 RFS NO A 18-jun-2010 11:58:28
    4 394 thread_4_seq_394.1270.722004225 RFS YES A 18-jun-2010 11:58:29
    4 394 thread_4_seq_394.1270.722004225 RFS YES A 18-jun-2010 11:58:29
    as a reminder we have a 4 node RAC system shipping logs to a 2 node RAC standby. There are no gaps but only one log is ever registered as being applied.
    Why is that? Why arnt all logs registered as being applied?

  • Active dataguard physical standby

    Hi,
    Is it possible to create additional tables and do DML operations on them ( these tables will not be present on primary db) in physical standby database created by active data guard.
    Regards,
    prasad.

    Is it possible to create additional tables and do DML operations on them ( these tables will not be present on primary db) in physical standby database created by active data guard.Prasad,
    Here Active datagaurd feature is only for READ ONLY or reporting purpose, where you can perform only Select queries which is from 11gRx at the same time recovery also will be active.
    If you want to open database in Read & Write , There there would be no consistent with Primary database, These behaves as different databases.
    So Either you have to use flashback option after completing your REad & Write options,
    Again you will lost all of the data, whatever you performed DML operations. So this is no use again.
    You can use this note for that procedure *How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]*
    But i can say conclusion to make your standby high available your DML operations are not supported, ofcourse supported but its not High availability.
    Hope this clears.
    You seems to be new user to OTN , consider closing the thread as answered, Keep the forum clean. https://forums.oracle.com/forums/ann.jspa?annID=718
    Edited by: CKPT on Mar 19, 2012 11:38 AM

  • Step by step 10g Dataguard , physical standby database setup metalink notes

    On metalink i saw this note, but unable to find now if someone can help....

    Note:248382.1 Creating a 10g Data Guard Physical Standby on Linux

  • Rman duplicate on Active dataguard physical standby

    In DR site. i have to clone the database from pshysical standby database and clone db will be normal db not standby. Is it possible to do rman duplicate from active dataguard? will it support the duplicate database from active database or i have to take the rman backup of standby database and duplicate from backup piece. please advise

    Please check below link
    http://odenysenko.wordpress.com/2012/03/26/rman-duplicate-from-active-database-from-standby-ends-with-ora-01671/
    Hope this answers all your questions,
    Regards,
    http://www.oracleracexpert.com
    ORA-01031: insufficient privileges
    http://www.oracleracexpert.com/2013/02/ora-01031-insufficient-privileges.html
    Error while loading shared libraries: libdb.so.2 - After Migrating REHL4 to REHL5
    http://www.oracleracexpert.com/2013/01/error-while-loading-shared-libraries.html

  • 10g dataguard - physical standby database

    Hi Guys,
    DB1 <Primary> - Production
    DB2 <Physial Standby> - DR
    I will need to startup my DB2 in DR segment for testing.
    If i perform the below, will it affect my Production DB? I need it to be up and running as well.
    DR:
    recover managed standby database cancel;
    shutdown immediate;
    startup nomount;
    alter database mount standby database;
    recover standby database until cancel;
    alter database activate standby database;
    thanks

    Hi,
    In 10g version, you can open database database with READ ONLY mode. In that case standby database
    recieve primary generated changes but not apply .
    I see you steps you using ALTER DATABASE ACTIVATE STANDBY DATABASE statement for activating database
    Activate the standby database using the SQL ALTER DATABASE ACTIVATE STANDBY DATABASE statement. This converts the standby database to a primary database, creates a new reset logs branch, and opens the database.*
    If you are not need convert standby database to primary database then , you must use only
    ALTER DATABASE OPEN READ ONLY;
    Regards
    Mahir M. Quluzade
    www.mahir-quluzade.com

  • DataGuard Physical standby

    Hi all,
    11.2.0.1
    Aix 6.1
    My boss instructed me to change every month the SYS and SYSTEM database passwords at PRIMARY database and STANDBY database.
    Is my DG standby db archivelog updates affected by these password change?
    Thanks a lot,
    zxy

    Hi all,
    According to Tsh,
    Conclusion: As long as you specify REDO_TRANSPORT_USER to a user who has SYSOPER privileges on both the primary and the standby databases, then you don't need to copy the password file from the primary database to the standby database whenever you change the sys password on the primary database.
    SQL>GRANT SYSOPER to &USER;
    SQL>ALTER SYSTEM SET REDO_TRANSPORT_USER = <user_name> SID='*';
    So if i grant
    SQL> GRANT SYSOPER TO SYS;
    SQL>ALTER SYSTEM SET REDO_TRANSPORT_USER ='SYS' SID='*';
    Will this work or is this a valid command?
    Thanks a lot,

  • Streams or Physical standby?

    I have a scenario here as below
    I have an Oracle 10gR2 database server in state A and would like it to be replicate over to a new database in State B. Db server at State A is the primary server which will be access by users and DB server at State B will be use only if Server at State A is crash or down. So which approach should I use?
    Streams or physical standby?

    user12259190 wrote:
    ya logically from the scenario it is more suitable to use dataguard physical standby than Streams but my worry is would it be a problem (e.g: unstable WAN) for this approach since it is going to be go through the WAN? From my experience dataguard physical standby server required to be rebuild from the production server(which required a downtime) when it is not in sync or something?
    Just to let you know that the user required to access the server once the primary server is down(regardless is server crash or WAN network down)DataGuard can afford a Gap, it depends on how long the gap was sustained for, on busy databases a few hours can be enough, i had a database that went down and i could speed-apply redo logs 5 days later.

  • DG physical standby 1

    Hi
    11.2.0.1
    We have a DEV database which is also as critical as PROD db since there are lots of critical projects running on it.
    This DEV database was configured with dataguard physical standby at the DR server.
    Well this is what I read in the documents only, as I am newly taking over as dba. The setup was done outsourced
    by 3rd party, and I can not talk to the implentors as they have been long gone.
    When I check the DR server only the PROD is running and the DEV was shutdown for the last 12 months.
    My question is if the physical standby is shutdown for almost a year, can it still be activated? or will it still be valid?
    Will it affect performance of the Primary database? since it might still checking heartbeat to it? or holding up some processes like archivers?
    How do you disable physical standby from the primary db?
    Thanks
    petra k.

    Hello;
    "if the physical standby is shutdown for almost a year, can it still be activated? or will it still be valid?"
    No and no. Even a tiny production database would have generated and remove too much archive in a years time for the old standby to have ANY value. Rebuild it.
    How do you disable physical standby from the primary db?
    You could just do this: ( On the primary side )
    alter system set log_archive_dest_state_2=defer;
    And you could clean up all the parameters for DG too.
    How to remove a Data Guard Configuration from Primary Database (Doc ID 733794.1)
    Best Regards
    mseberg

  • Test physical standby database in dataguard

    Hi all,
    I had a successfull dataguard implementation for oracle 9r2.
    Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
    As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
    Now i want to test physical standby database with applications tier  but don't want to disturb origional primary database.
    as these are the normal switchover steps
    1) at primary db
    ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
    2) at standby
    ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
    3) at primary, now this will be the stand by database
    SHUTDOWN IMMEDIATE;
    STARTUP MOUNT;
    4) at standby, now this will be the primary database
    SHUTDOWN IMMEDIATE;
    STARTUP
    My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
    Regards,
    Ken

    To avoid touching the primary production DB, you may try to use the following command on your standby database side:
    alter database activate standby database;
    This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
    Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

  • How to create physical standby database without dataguard

    Hi,
    Can anyone please help me how to create Physical Standby Database without dataguard. As i am using Oracle 10.2.0.1 Standard Edition for production databases.
    Please find the specifications of my server :
    Database : Oracle 10.2.0.1(Standard Edition)
    Server : Linux 4.0(32 bit machine)
    As we know that Dataguard cannot be created in Standard Edition as we dont have that option in this edition. So please help me how to create the physical standby database.
    Thanks in advance.
    Regards,
    Farooq

    Hello,
    I hope this link helps you out...
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
    http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
    Thanks & Regards
    Pratik Lakhpatwala
    Jr Oracle DBA
    Edited by: Pratik.L on Dec 31, 2009 12:03 PM

  • Physical standby without dataguard

    Naive question.
    I am going thru metalink note (374069.1) on how to create a physical standby. In that note, they didn't mention data guard stuff. Am I to assume that physical standby without dataguard can be created?
    Thanks.

    It might appears to be easy to create psuedo standy but you will have hardtime to simulate the automatic archive log apply and gap resolve.
    Plus the level of data availability provided by self-managed standby can't come close to Data Guard can offer.
    With Data Guard you can almost get zero data loss between Primary and Standy, depends on your redo logfile size there could be many data in online redo logs.

Maybe you are looking for