DataGuard - payback time

Hi all

9i

RHEL5

I can't think of any use to delay the recovery?

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DELAY 30;

Why delay?

Thank you all,

JC

http://docs.Oracle.com/CD/B28359_01/server.111/b28294/log_arch_dest_param.htm#i77472

Tags: Database

Similar Questions

  • ORA-01274 on the physical database paused.

    Hello

    I configured a physical database ensures with * LGWR ASYNC * transport services, which works very well.
    When I create a set of data files and the users on the main site, and then create a control journal, the journal of alerts to the backup site is written with error: * ORA-01274 *.

    I have attributed this to a configuration problem and did the whole excerceise from the creation of the primary database of Eve databe and configure the dataguard, this time with * ARCH * transport services.

    But the problem still persists. Is this normal? I was told that new tablespaces/data files will not be replicated on the site of Eve by transport services. Is this true? If so, please tell me how to reproduce them on the backup site.
    If not, please help me solve the problem.

    I also write, the alert log sleep here for a better understanding of the problem. Kindly go through it...
    +
    Clearing online redo logfile 1 /u02/app/oracle/oradata/asridb/redologs/r01.log
    Clearing online log 1 of thread 1 sequence number 37
    Sun Mar 22 12:47:42 2009
    Errors in file /u02/app/oracle/admin/asridb/bdump/asridb_mrp0_20176.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u02/app/oracle/oradata/asridb/redologs/r01.log'
    Clearing online redo logfile 1 complete
    Media Recovery Waiting for thread 1 sequence 39
    Sun Mar 22 12:47:43 2009
    Completed: alter database recover managed standby database disconnect from session
    Using STANDBY_ARCHIVE_DEST parameter default value as /u02/app/oracle/asridb/archival
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 20213
    RFS[1]: Identified database type as 'physical standby'
    Sun Mar 22 12:49:04 2009
    RFS LogMiner: Client disabled from further notification
    Sun Mar 22 12:49:40 2009
    RFS[1]: No standby redo logfiles created
    RFS[1]: Archived Log: '/u02/app/oracle/asridb/archival/1_39_682125307.arc'
    Sun Mar 22 12:49:42 2009
    Media Recovery Log /u02/app/oracle/asridb/archival/1_39_682125307.arc
    Media Recovery Waiting for thread 1 sequence 40
    Sun Mar 22 12:56:33 2009
    RFS[1]: No standby redo logfiles created
    RFS[1]: Archived Log: '/u02/app/oracle/asridb/archival/1_40_682125307.arc'
    Sun Mar 22 12:56:38 2009
    Media Recovery Log /u02/app/oracle/asridb/archival/1_40_682125307.arc
    File #5 added to control file as 'UNNAMED00005' because
    the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
    The file should be manually created to continue.
    Errors with log /u02/app/oracle/asridb/archival/1_40_682125307.arc
    MRP0: Background Media Recovery terminated with error 1274
    Sun Mar 22 12:56:38 2009
    Errors in file /u02/app/oracle/admin/asridb/bdump/asridb_mrp0_20176.trc:
    ORA-01274: cannot add datafile '/u02/app/oracle/oradata/asridb/datafiles/asrim_master.dbf' - file could not be created
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail
    Sun Mar 22 12:56:39 2009
    Errors in file /u02/app/oracle/admin/asridb/bdump/asridb_mrp0_20176.trc:
    ORA-01274: cannot add datafile '/u02/app/oracle/oradata/asridb/datafiles/asrim_master.dbf' - file could not be created
    Sun Mar 22 12:56:39 2009
    MRP0: Background Media Recovery process shutdown (asridb)
    +
    Thanks in advance,
    Aswin.

    Note this line:

    because the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
    The file must be created manually to continue.

    If you want to have the automatic creation of files on the side of the watch, set this pfile/spfile to AUTO.

    Werner

  • Real as for again time doubt REALITY apply to the Dataguard

    Friends, how to check if "TIME REAL REDO APPLY" is set in my configuration of dataguard. If it is not "active", how do I activate the "TIME REAL REDO APPLY" on the use of dataguard broker.

    Thanks in advance.

    This will help you

    http://aprakash.WordPress.com/2012/03/14/how-to-check-real-time-apply-is-enabled-on-standby-database/

    http://easyoradba.com/2011/01/10/real-time-apply-in-Oracle-Data-Guard-10G/

  • Active Dataguard passage puts new Eve in time real query

    Hi gurus,

    If you use Active Dataguard, after swicthover/failover using observer and dg broker no sthe new Eve will be time real query mode (ADG) or manually having to open the db in read-only mode.

    Please let me know.

    Thank you

    Yes, it is:

    [uhesse]$ dgmgrl sys/oracle@prima
    DGMGRL for Linux: Version 11.2.0.1.0 - Production
    
    Copyright (c) 2000, 2009, Oracle. All rights reserved.
    
    Welcome to DGMGRL, type "help" for information.
    Connected.
    DGMGRL> show configuration
    
    Configuration - myconf
    
      Protection Mode: MaxAvailability
      Databases:
        prima - Primary database
        logst - Logical standby database
        physt - Physical standby database
    
    Fast-Start Failover: DISABLED
    
    Configuration Status:
    SUCCESS
    
    DGMGRL> show database physt
    
    Database - physt
    
      Role:            PHYSICAL STANDBY
      Intended State:  APPLY-ON
      Transport Lag:   0 seconds
      Apply Lag:       0 seconds
      Real Time Query: ON
      Instance(s):
        physt
    
    Database Status:
    SUCCESS
    
    DGMGRL> switchover to physt;
    Performing switchover NOW, please wait...
    New primary database "physt" is opening...
    Operation requires shutdown of instance "prima" on database "prima"
    Shutting down instance "prima"...
    ORA-01109: database not open
    
    Database dismounted.
    ORACLE instance shut down.
    Operation requires startup of instance "prima" on database "prima"
    Starting instance "prima"...
    ORACLE instance started.
    Database mounted.
    Database opened.
    Switchover succeeded, new primary is "physt"
    DGMGRL> show configuration
    
    Configuration - myconf
    
      Protection Mode: MaxAvailability
      Databases:
        physt - Primary database
        prima - Physical standby database
        logst - Logical standby database
    
    Fast-Start Failover: DISABLED
    
    Configuration Status:
    SUCCESS
    
    DGMGRL> show database prima
    
    Database - prima
    
      Role:            PHYSICAL STANDBY
      Intended State:  APPLY-ON
      Transport Lag:   0 seconds
      Apply Lag:       0 seconds
      Real Time Query: ON
      Instance(s):
        prima
    
    Database Status:
    SUCCESS
    

    Kind regards
    Uwe Hesse

    http://uhesse.WordPress.com

  • Y at - it time to dataguard

    Hello

    I'm new to dataguard so please can someone help me understand the concept.

    Suppose my primary database is down cash then I do my database as main will there be a downtime?

    So yes - there is a minimum downtime is required.

  • Small questions about Dataguard

    Hello

    I have a few questions about Dataguard. I'm new to DG, carry me so for the display of these fundamental questions:

    We plan to install Oracle 12 c to Win 2012 R2 with primary and physical intelligence on different physical servers. We are looking for HA solution, but cannot afford to license CARS. The two primary & Eve are going to be in the same data center connected via a 1 gigabit network. So I have a few questions related to it.

    (a) since both of our primary & Eve is going to be in the same data center with good connectivity. Can I assume that although Data guard is more DR solution, in our case it would be HA solution since we have no network latency.

    (b) is it safe to assume that where primary fails, then the day before can automatically take the role of primary education without any manual intervention, possibly using Dataguard broker?

    (c) so I understand that where primary breaks down, the existing connections transfer automatically from primary to standby db (most recent primary), but how my web based java application will know that more recent connections must be sent to the standby db Server (more recent primary)? I guess net Oracle has a provision to handle this? Who can be automated?

    (d) given that I have only 2 physical servers, can I deploy broker Dataguard on a normal PC (since it is a thin client) assuming the PC is kept in the data center and is online 24/7?

    (e) I was reading about the modes of Protection, account required to our current situation & infrastructure, I choose 'Maximum availability Mode' instead of 'maximum Performance '.

    (f) what is your point of view about Oracle integrated security? I hear too much on Oracle failsafe, because people generally go to a combination of CARS & dataguard for HA? We have a few additional storage that can be shared between the two servers, but I feel with literally no DG network latency can provide us HA.

    Concerning

    Learner

    (a) since both of our main & secondary is going to be in the same data center with good connectivity. Can I assume that although Data guard is more DR solution, in our case it would be HA solution since we have no network latency.

    Well it will not provide the level of HA that is RAC. RAC is a Transparent Application failover. With a physical standby, you need to apply some delay for a failover operation. You can implement the observer that can automate the failover and reduce the time.

    (b) is it safe to assume that where primary fails, then the day before can automatically take the role of primary education without any manual intervention, possibly using Dataguard broker?

    This isn't really the DG broker, but rather the observer you will need to implement. The DG broker automate failover. It will be the observer who "sees" (where its name) that the principal is down and initiate the failover process. To do this, the observer will use the DG broker, so it will be necessary.

    (c) so I understand that where primary breaks down, the existing connections transfer automatically from primary to standby db (most recent primary), but how my web based java application will know that more recent connections must be sent to the standby db Server (more recent primary)? I guess net Oracle has a provision to handle this? Who can be automated?

    You'll want to read on the QuickStart failover. http://www.Oracle.com/technetwork/articles/smiley-fsfo-084973.html

    (d) given that I have only 2 physical servers, can I deploy broker Dataguard on a normal PC (since it is a thin client) assuming the PC is kept in the data center and is online 24/7?

    The DG broker is required to run on the database server. The DG broker will run on the primary and standby. I think that what you're asking really anything is if the observer can run on a PC. Yes it can. However, it is probably not a good idea. A PC will not have the internal hardware redundancy, a server can have. If the PC can fail more often than to a server. And if the gods are bad, it will fail when you most need.

    (e) I was reading about the modes of Protection, account required to our current scenario & infrastructure, I choose 'Maximum availability Mode' instead of 'maximum Performance '.

    Your choice should depend on the amount of data loss is acceptable.

    (f) what is your point of view about Oracle integrated security? I hear too much on Oracle failsafe, because people generally go to a combination of CARS & dataguard for HA? We have a few additional storage that can be shared between the two servers, but I feel with literally no DG network latency can provide us HA.

    Oracle integrated security only works on Windows with a MS Failover Cluster. Real DBAs do not have Oracle on MSFC.

    See you soon,.
    Brian

  • DataGuard passage failed: impossible to failover, primary database is always "PRIM".

    Hi all


    DataGuard digital switchover is Getting failed with the below error:

    DGMGRL > passage to the "dry";

    Continue to pass, please wait...

    Error: ORA-16664: impossible to receive the result of a database

    Failed.

    Impossible to failover, primary database is always "PRIM".

    Note:it comes to node unique database with physical styandby.

    =====================================================

    In alert log file provides, I am getting below the error during the failover operation:

    Fatal OR connect 12514 error, connect to:

    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rac1.localdomain)(PORT=1524)))(CONNECT_DATA=(SERVICE_NAME=PRIM_DGB)(INSTANCE_NAME=PRIM)(CID=(PROGRAM=oracle)(HOST=rac2.localdomain)(USER=oracle)))

    Please suggest to solve this problem.

    Thank you.

    Problem is fixed - value StaticConnectIdentifier checked to a database of primary and standby in dgmgrl ==> primary port and standby was wrong wrt to the listening port value.

    Step 1 > error ORA-16664 and ora-12514

    ==> check StaticConnectIdentifier value for a primary database and a standby in dgmgrl ==> primary port and standby had value default IE 1521

    Primary:

    SEE THE VERBOSE "PRIM" DATABASE

    StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac1.localdomain) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = PRIM_DGMGRL) (INSTANCE_NAME = PRIM)(SERVER=DEDICATED)))'

    Standby time:

    SEE THE DETAILED "DRY" DATABASE

    StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac2.localdomain) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = SEC_DGMGRL)(INSTANCE_NAME=SEC) (SERVER = DEDICATED)

    Step 2 > listening port for the primary and standby is 1524 and 1525, so change these manually.

    Primary:

    SQL > show parameter local_listener

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    LOCAL_LISTENER chain

    SQL > alter system set local_listener ='(ADRESSE = (PROTOCOL = TCP) (HOST = rac1.localdomain) (PORT = 1524))

    Standby time:

    ALTER system set local_listener = '(ADDRESS = (PROTOCOL = TCP) (HOST = rac2.localdomain) (PORT = 1525))';

    #edit database 'PRIM' set the property StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac1.localdomain) (PORT = 1524)) (CONNECT_DATA = (SERVICE_NAME = PRIM_DGMGRL) (INSTANCE_NAME = PRIM)(SERVER=DEDICATED)))'

    #edit database 'DRY' set the property StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac2.localdomain) (PORT = 1525)) (CONNECT_DATA = (SERVICE_NAME = SEC_DGMGRL)(INSTANCE_NAME=SEC) (SERVER = DEDICATED)))'

  • DataGuard failover

    Hi all

    I nam using Oracle 11 g on RHEL 5 2.

    I had implemented the DataGuard (database physical Standby).

    I just want to know in case of failover, my Eve becomes primary, and after some time my first back, how will I do that primary to new standby/primary.

    I mean, that is, after the failover if the failed node comes up, what is the best way to do is tandby again.

    I'll reconfigure the dataguard setup?

    Kind regards.

    This reinstante can be so configured DGMGRL, right?

    If the broker is configured, the reinstatement may be made.

    If the broker is not configured, then you have to flashback to the "old primary" database to the value "Eve became primary YVERT" and then convert pending database. (Please note that you must have active flashbacks).

    Please see the I posted in my previous answer. Which don't use a broker.

    -Jonathan Rolland

  • Fact Eve DataGuard between (Source site) 11.2.0.3.0 and (target site) 11.2.0.4.0 taken in charge?

    Hello gurus

    Fact Eve DataGuard between (Source site) 11.2.0.3.0 and (target site) 11.2.0.4.0 taken in charge?

    My environment:

    Site source OS: RHEL 5.6 Database: v11.2.0.3.0

    Target site OS: RHEL 7.1 Database: v11.2.0.4.0

    The database size is 100 GB

    What about

    Hitgon

    As I mentioned, again the DG transport and apply the will to work in mixed versions. But it is not supported by Oracle for longer period. When I say not supported which means lets say if you hit any bugs in mixed environment associated with DG, then you can't get a support to connect to a new bug... etc... However, mixed versions are supported bby Oralce for 30 days. This is because any time the migration/upgrade that you can keep primary and standby in different versions.

    For more details refer,

    1.

    search for lines,

    The maximum length supported for different database software house between primary and Nightlight is 31 days.

    Insurance of Patch Oracle - Data Guard standby-first Patch applied (Doc ID 1265700.1)

    2. with regard to Cloud Control Support.

    SUBJECT: Set up and manage Oracle DataGuard, using Oracle Enterprise Manager Cloud control 12 c

    search for "the obligation for the Oracle software is stricter. The Oracle software must be the same version - including the release of the patches Oracle group. »

    Set up and manage to Oracle Data Guard with Oracle Enterprise Manager Cloud control 12 c

  • Speed of transfer network for dataguard

    Hi all

    Database 11.2.0.4

    RHEL6

    I'll put up dataguard PROD at the DR site.

    What is the network speed required between servers in site/two for dataguard?

    Is enough 1 MB/s?

    Thank you very much

    JC

    You may consider setting up to use a time based on check-in.  In order to keep the size of 1 G, but the archive size is just what data is there when the archive is created.  It's much smaller than I'm used to it, so apologies for that.  See the init parameter archive_lag_target.  There are, of course, to many ways to set up DG.

    ALS is a document that defines (among other things) the speed at which you can recover.  15 or 20 minutes is often suggested for when companies are unable to arrive at a precise definition.   So every 15 minutes, the db spits out a newspaper, DG move more and the applied.  Some deliberately put places in a lag time too much, then you can "pull the plug" If you know someone has screwed up bigtime, without having to make a recovery.  You also must define exactly how you will apply newspapers (there are a number of options, make sure that you understand the concepts) and expectations for the digital switchover and how to deal with the app and substitution.

  • Stop listener as part of the transition to the DataGuard?

    I have a database of primary and Standby, configured with DataGuard. A third server runs the process of observation to monitor from the database when the principal becomes unavailable. It all works and we are happy with it from the point of the DB of the things. The database version is 11.2.0.4 running on RedHat 6.4

    The demand side, we use WebLogic and have set up the connection string of JDBC using the following format:

    (DESCRIPTION=(ADDRESS_LIST=(FAILOVER=ON)(LOAD_BALANCE=OFF)(ADDRESS=(PROTOCOL=TCP)(HOST=production-db-a)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=production-db-b)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=abc)))

    When the primary database server is stopped, then the observer notices and will be a change occurs and just continues to work.

    However, what's happened is that there are delays in network that caused the observer make the pass on the eve (production-db-b) and makes it the main. What is expected (except for wait times of network that is under review). Finally, the network problem disappeared and the original primary server (production-db-a) is back on the network and he opted to be a watch. So far so good. If all goes well on the side of the things database. However, on the side of the demand of the things, the application attempts to connect to production-db-a, since it is now available again, but service is on production-db-b because he has fallen.

    If we move off the coast of the production-db-a listener, then all is good again. We have configured listeners, LISTENER to database service and LISTENER_DGMGRL for dataguard that runs on port 1522. So just stop LISTENER while LISTENER_DGMGRL running on production-db-a seems to fix the problem.

    The question is now, peut LISTENER stop automatically DataGuard during the passage of the day before and started for the primary, or is there another solution for this problem?

    Your tnsnames.ora connection string refers to

    (CONNECT_DATA = (SERVICE_NAME = abc))

    What is the deault for the database service? If so, do not use it. On the contrary, create another service with and start it by calling DBMS_SERVICE. START_SERVICE in a trigger to start (or after triggering change in role) which checks if the database is currently a primary or secondary.

  • Upgrade of dataguard 11.2.0.3 to 11.2.0.4

    Hello

    We would like to upgrade 11.2.0.3 dataguard to 11.2.0.4, but there are differences in the 2 official documents:

    (a) less than document it says that major version upgrades are not eligible, and we must first convert logical physical standby standby for upgrade (standby logical transitional upgrade spread)

    Data Guard standby and -first Patch applies (Doc ID 1265700.1()

    (b) below to document, it is said that we can stop primary and standby, apply the hotfix and then run catupgrade:

    How do you apply a group of patches, the power supply or the CPU in a configuration of data secondary physical custody (Doc ID 278641.1()

    (1) Please can you confirm that we can move from 11.2.0.3 to 11.2.0.4 the physical dataguard without converting to logic by using option b?

    (2) if we change the compatible parameter and we apply different versions of oracle, the newspaper working properly?

    I found that note 2 to upgrade. The minimum time using rolling fashion "using standby logic" is more aggressive and you must ensure that your platform is compatible with the logical pending changes.


    Oracle Database - Enterprise Edition - Version 8.1.7.4 to 10.2.0.1 [version 8.1.7 to 10.2]

    How to level one database and secondary physical to Oracle10gR2 (10.2) (Doc ID 407040.1)

    1. stop the database pending the application of recovery logs

    2. stop the recovery of his expedition logs

    3. upgrade the primary database server executable files

    4 level database server executable files shall ensure that

    5. switch to level the main database using DBUA or upgrade scripts (see Note: 316889.1)

    6 mount the backup database

    7 reactivate shipping again Eve elementary school

    8 restart the recovery process run on the standby database again progress apply

    Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.4 [Release 10.1 to 11.2]

    How do you apply a group of patches, the power supply or the CPU in a configuration of data secondary physical custody (Doc ID 278641.1)

    1. primary level disable sending newspapers to the backup site.

    2. stop the backup site and

    Apply provisional patchsets for RDBMS binaries according to the README file. This includes the update of the Group of hotfixes/patches (PSU) / Critical Patch Update (CPU). You will not be able to and do not need to run scripts (catpatch.sql etc.) against the eve RDBMS itself.  Start the standby site to climb only, do not restart managed recovery.

    3 judgment of the main site,

    Apply the patch from group fixes/PSU/CPU for the RDBMS binaries and patch the RDBMS itself by following the instructions in the README file (run catpatch/catbundle/catcpu etc.).

    4. start the primary site, re - activate the standby log shipping.

    5. on-site the day before restart recovery redo apply / managed and RDBMS changes implemented in the main Site through catpatch/catbundle/catcpu will also apply to the wait.

  • Guaranteed environmental Dataguard restore points

    Hi all

    Can send all the steps to make guaranteed points in Dataguard recovery environment.

    Thanks in advance.

    Hello

    This is a Version of Oracle 11.2.0.4.

    on implementing standby

    ALTER database recover managed standby database cancel;

    CREATE pre_upgrade WARRANTY FLASHBACK DATABASE RESTORE POINT.

    change recover managed standby database disconnect log file using current;

    Check if the restore point has been created

    SELECT flashback_on, log_mode FROM v$ database;

    Col name format a30

    Col hour format a32

    col 999999999999 SNA format

    SELECT name, SNA, time, database_incarnation #, guarantee_flashback_database, storage_size FROM v$ restore_point;

    soon in the primary

    CREATE pre_upgrade WARRANTY FLASHBACK DATABASE RESTORE POINT.

    Check if created

    SELECT flashback_on, log_mode FROM v$ database;

    Col name format a30

    Col hour format a32

    col 999999999999 SNA format

    SELECT name, SNA, time, database_incarnation #, guarantee_flashback_database, storage_size FROM v$ restore_point;

    concerning

  • DataGuard: MRP still in WAIT_FOR_GAP after incremental backup recover

    Hello

    I'm new to the dataguard configuration, and recently, I connected on a dataguard configuration to test the object.

    I have deleted stupidely some archive my primary database logs, thereby breaking the standby update (due to the fact that the database has not been started for a long time, the gap is now about 130 days ).

    I have to try to recover the situation re-synchronized the RCS of the day before using an incremental backup (and create eve of primary control files).

    After restoration, the SNA were the same, but restarting the recovery service (MRP), it is still indicating WAIT_FOR_GAP and still waiting for my missing archive logs.

    New archive logs is well shipped to the waiting however.

    No idea what I missed or what should I do?

    The database version is a 12.1.0.1.

    DGMGRL > see Configuring

    Configuration - g12dggo

    Protection mode: MaxPerformance

    Databases:

    g12dggop - primary database

    Error: ORA-16724: could not resolve the deficit for one or more databases in waiting

    g12dggos - physical of the standby database

    Fast-Start Failover: DISABLED

    The configuration status:

    ERROR

    DGMGRL > validate database g12dggop

    Database role: primary database

    Ready for the digital switchover: Yes

    Flashback Database Status:

    g12dggop: Off

    DGMGRL > validate database g12dggos

    Role of data: physical database ensures

    Primary data: g12dggop

    Ready for the digital switchover: No.

    Ready for failover: Yes (main stream)

    Flashback Database Status:

    g12dggop: Off

    g12dggos: Off

    Apply information in standby mode:

    Apply a State: running

    Apply the Lag: 143 days 14 hours 18 minutes 26 seconds

    Apply the delay: 0 minutes

    Database backup:

    SQL > select process, sequence #, status from v$ managed_standby;

    STATUS OF PROCESS SEQUENCE #.

    --------- ---------- ------------

    ARCH CONNECTED 0

    ARCH CONNECTED 0

    RFS 0 IDLE

    MRP0 1965 WAIT_FOR_GAP

    RFS 3526 IDLE

    More small sequence of table v$ archived_log is corresponding to the last recovery made.

    SQL > select sequence #, applied to the order of v$ archived_log by sequence #.

    SEQUENCE # APPLIED

    ---------- ---------

    3441 NO.

    SQL > select * from v$ archived_log where sequence #= 3441; Select * from v$ archived_log where sequence #= 3441;

    RECID STAMP

    ---------- ----------

    NAME

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    DEST_ID THREAD # SEQUENCE # RESETLOGS_CHANGE # RESETLOGS_TIME RESETLOGS_ID FIRST_CHANGE # FIRST_TIME NEXT_CHANGE # NEXT_TIME BLOCKS BLOCK_SIZE CREATOR

    ---------- ---------- ---------- ----------------- ------------------- ------------ ------------- ------------------- ------------ ------------------- ---------- ---------- -------

    REGISTR STA ARC APPLIED S DEL COMPLETION_TIME DIC DIC END BACKUP_COUNT ARCHIVAL_THREAD # ACTIVATION # IS_ COM FAL END_OF_RED BIN CON_ID

    ------- --- --- --------- --- - ------------------- --- --- --- ------------ ---------------- ----------- --- --- --- ---------- --- ----------

    1 880046905

    /oravar/G12DGGO/Archiv/1_3441_865786197.dbf

    2 1 1 08/12/3441 2014 16:09:57 865786197 7004011 18/05/2015 17:21:17 7005043 18/05/2015 17:29:22 509 512 ARCH

    RFS NO NO YES NO A 17:28:25 05/18/2015 NO NO NO 0 1 2523036437 NO NO NO YES 0

    Thank you in advance for your help!

    Problem solved.

    In Oracle 12 c, roll forward is more to do "by hand".

    There are a few commands to RMAN done automatically, by using the primary database service (G12DGGOP_DG for me).

    So back up mode:

    RESTORE DATABASE SERVICE G12DGGOP_DG WITH THE HELP OF NOREDO COMPRESSED BACKUPSET SECTION SIZE 100M;

    Then after restore controlfile in nomount (stop):

    RESTORE CONTROLFILE EVE OF SERVICE G12DGGOP_DG;

    The information comes from here:

    http://allthingsoracle.com/rolling-forward-a-physical-standby-database-using-the-recover-command/

    Reference on Oracle documentation:

    https://docs.Oracle.com/database/121/BRADV/rcmadvre.htm#BRADV685

    Thank you all for the answers and the help on this!

    Ray Zin

  • Doubt on the performance mode maximum dataguard

    HI gurus,

    We have a dataguard environment configured in 12.1.0.2.0 on 5.6 OEL. DataGuard is configured in maximum performance using following congiguration,

    18:26:26 SQL > show parameter log_archive_dest_2

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    string LOG_ARCHIVE_DEST_2 = TGOID NOAFFIRM LGWR ASYNC COMPRESSION service = ENABLE VALID_FOR =(ALL_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME = TGOID

    Here I used LGWR ASYNC and enabled real-time apply to my waiting to help,

    SQl > alter recover managed standby database disconnect log file using current;

    Here are my doubts,

    1. If we allow real time apply, the changes will reflect on the eve when a commit happens in elementary school. is this correct?

    But here I do not see this behavior, changes are get applied to the previous day only when I do a log switch. (as in the case of the mode of transport ARCH)

    2. so, if I want to get changes made to the previous day when a commit happens at the elementary level, is I need to set the following?

    First of all,

    ALTER system set log_archive_dest_2 = service = TGOID ASSERT LGWR SYNC COMPRESSION = ENABLE VALID_FOR = (ALL_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME = TGOID scope = both;

    Secondly,.

    ALTER DATABASE BASE_DE_DONNEES SLEEP TOGETHER IN ORDER TO MAXIMIZE THE AVAILABILITY/MAXIMIZE PROTECTION.

    is this correct?

    3 if its OK what is the advantage of using lgwr async in maximum performance? then, what is meant by real time applies to maximum performance?

    Thank you and best regards,

    Mahi

    If you want the data validated to be simultaneous on two sites, use maximum availability (or maximum Protection).  The 'risk' with maximum Protection, it is that if the network link fails or breaks down the day before or the day before is not able to write it again received, the primary has put an end.  The 'advantage' (but also the 'risk' If you keep monitoring it) with maximum availability is the primary can return to maximum Performance If the night before does more (for any of the reasons stated in the first sentence)

    Allow standby redo logs Oracle to write again to the backup site without waiting that the primary archive the Redo Log.  If your primary online Redo log is archived every 30 minutes and you only run on base ARCH, you may lose 30 minutes of transactions.

    Hemant K Collette

Maybe you are looking for