Data Guard - journal not attributed to primary school

Similar Questions

• Can a weird question we use Data Guard to apply the bidirectional log?

  Hi I have a question about Data Guard, can we use Data Guard to apply the bidirectional log? I mean keeping the two of them primary and standby to Active status (read write Mode).
  
  Maybe my question seems silly, but I just wanted to check on it.
  
  Thank you

  Laughing out loud

  That Golden Gate or water courses that will work in two ways. One or the other. Puts additional requirements on the hardware is the downside.

  Data Guard does not do that.

• Data Guard versus Active Data Guard?

  Environment:
  
  Oracle on Solaris 5.10 EA 11.2.0.3 database
  
  I have read several threads here and paid through the documentation, but this point still escapes me.
  
  When Data Guard to become Active Data Guard?
  
  When Eve is OPEN and in read mode ONLY all redo logs are actively applied?
  
  If I stop log apply and OPEN the day before for READONLY access, is this just regular Data Guard?
  
  I want to of course use Data Guard but not pay for Active Data Guard at this stage.
  
  Where this is documented?
  
  Michael, if you listen, it's well to the top of your driveway! :-)
  
  Thank you very much!!
  
  -gary

  Hello;

  When a database of the previous day is opened read-only for queries, sorting and reporting.

  Requires a license.

  The day before still applies again.

  http://www.Oracle.com/technetwork/database/features/availability/DS-activedataguard-11gr2-130305.PDF

  See also - 9.2 open a physical database from the previous day-

  Oracle® DataGuard of Concepts and Administration 11 g Release 2 (11.2) E10700-02

  Best regards

  mseberg

  Published by: mseberg on January 29, 2013 08:03

• Repeat applies without using Data Guard

  Hello everyone,
  
  I would like to redo apply to a database of pending. Unfortunately, the DB's standard edition for Data Guard is not an option. Is there documentation on how to achieve something like the roll forward apply without using Data Guard?
  
  Kind regards
  Frank

  There are a lot of threads on this same forum on this specific topic.
  Please use the search (top right of page), and see the list of threads returned:
  https://forums.Oracle.com/forums/search.jspa?threadID=&q=%2Bstandby+%2Bstandard+%2Bedition&objid=F61&DateRange=all&userid=&NumResults=15

  Nicolas.

• How to move from Data Guard time really apply (restore) to archive the journal

  Hello
  
  Standby database configured with broker and application really remake in time; However, I want to change it to archive the journal apply mode without losing the broker configuration. Is this possible? If it is not possible to use the broker to make archive log apply, I can remove the broker and use Data Guard to set up the day before to use the archive log apply?
  
  Concerning

  Hello;

  Broker automatically allows real-time applies to databases on hold if the standby database has standby redo logs configured.

  Stop repeat applies

  DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-OFF';
  

  Repeat restart applies broker

  DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-ON';
  

  In order to get rid of standby redo logs would be a way. I would like to leave myself alone. Real time assistance to prevent the loss of data.

  Best regards

  mseberg

• Several primary and physical databases Configuration ensures in Data Guard Broker

  Hello

  Is it possible to add two or several primary and physical databases configuration ensures in data guard broker?

  I have 1 primary databases and two databases physical standby that is

  (1) primary that is pri - (database primary)

  (2) secondary i, e, s (physical pending)

  (3) Secondary2 i.e. sec2 (physical pending)

  Practical AM sinister place, my scenario is my pri and dry machines are in seat, if the pri crashed it switch to s that works very well and my S2 is in another area office. Suppose that if my two siege machines pri and sec crashed, so I want to do my mahcine sec2 as primary.

  I have two separate computers to the broker a headquarters and a District Office

  Use failure of quick start on Data Guard Broker, broker headquarters machine I have configured pri and dry but in sector office broker not able congifured pri and S2 and the machine.

  can be done several primary database configuration with data bases on hold?

  Has anyone done this before, or has a perform a recovery after loss of place...

  need help or suggestion

  thanx

  No.... It is not possible. When you use the DG broker, the first thing you can do in the DGMGRL utility is to deliver CONFIGURATION to CREATE. You can see on the doc of this command that you define here the PRIMARY DATABASE.

  The command to add a DATABASE to the broker, adds a new database pending. You cannot add an another primary.

  The broker configuration is explicitly for a primary and all standby databases is supported. If you have an another primary, you create a separate DG broker configuration.

  See you soon,.
  Brian

• Purge logs archiving on things primary and Standby and for Data Guard RMAN

  
  Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

  Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

  Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

  Q1. The above only removes logs archiving to the primary or primary and Standby?

  Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  I also saw

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

  Q3. That what precedes, and once again it is something that you re primary side?

  I saw the following advice in the manual of Concepts of data protection & Admin

  Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

  Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

  Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  Any idea greatly appreciated,

  Jim

  The above only removes logs archiving to the primary or primary and Standby?

  When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

  including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

  You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

  If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  Its a configuration, it will not erase by itself.

  If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

  1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

  2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

  If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

  Great example:

  http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

  All Oracle is worth a peek here:

  http://emrebaransel.blogspot.com/

  That what precedes, and once again it is something that you re primary side?

  I would never use it. I always had it put it this way:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

  Why would I want my primary ro connect to the RMAN Repository?

  Because if you break down, you want to be able to backup there, too.

  Also if it remains idle for awhile you want.

  Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Always use a database of catalog RMAN with Data Guard.

  If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Same answer as 5, use a catalog database.

  Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Same answer as 5, use a catalog database.

  What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

  Best regards

  mseberg

  Summary

  Always use a database with RMAN catalog.

  Always use CRF with RMAN.

  Always set the deletion «To APPLY ON ALL STANDBY» policy

  DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

  Post edited by: mseberg

• Removal of RMAN, Data Guard, and Archives journal

  Our DG Environment running Oracle 11 g R2
  We have a 3 node DG Environment with
  A primary being
  B and C being Active Data Guard Standby
  Backups are taken out of B and go directly to tape.
  Standby Redo Logs and fast recovery area are used
  
  
  
  Holding the recommendation of "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
  RMAN primary control ('A')
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING
  
  RMAN standby ("B") where the backup is performed
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY
  
  RMAN set the other Standby ("C")
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING
  
  How can we know what newspaper Archives are eligible to be removed from 'A' and 'C '?
  When remove it takes place?
  How can say us when archiving logs are deleted from the 'A' and 'C '?

  Dear user10260925,

  The documentation that you read is reliable but not enough.

  The Oracle can handle the archivelog directory and know that you are eligible for deletion. Stuff you posted here was derived from the books online and is supported and can be used when the Oracle knows and manages the archivelogs. This is simply called the flash recovery area. Please read the FRA at this very moment.

  Under the personal component normal circumstances in the industry use a few scripts to achieve on backup archivelog deletion.

  Here's a useful example to you;

  # Remove old archivelogs
  ######################################
  00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
  ######################################
  
  vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
  export ORACLE_SID=optstby
  export ORACLE_HOME=/oracle/product/10.2.0/db_1
  cd /db/optima/archive/OPTPROD/archivelog
  
  /oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
  grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
  chmod 755 delete_applied_redo_logs_1.sh
  sh delete_applied_redo_logs_1.sh
  rm delete_applied_redo_logs_1.sh
  rm delete_applied_redo_logs.lst
  

  vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
  vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
  set echo off
  set heading off
  spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
  select 'rm -f ' || name from v$archived_log where applied = 'YES';
  spool off
  exit
  vals3:/db/optima/archive/OPTPROD/archivelog#
  

  Hope that helps.

  Ogan

• Data Guard: Primary descends from secondary crashes

  Hi Oracle experts.

  IM using Oracle Data Guard to the physical configuration of HA standby.

  I have primary with 70G of political RMAN and as noted flash recovery area size:

  RMAN > show all.

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name MSEORCL are:

  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default

  CONFIGURE BACKUP OPTIMIZATION # by default

  SET UP DEFAULT DISK DEVICE TYPE; # by default

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / opt/oracle/base/product/11.2.0/dbhome_1/dbs/snapcf_mseorcl.f'; # by default

  Size of the flash area is also pending physical (secondary node) 70G. and policies as described for RMAN:

  RMAN > show all.

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name MSEOS3 are:

  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default

  CONFIGURE BACKUP OPTIMIZATION # by default

  SET UP DEFAULT DISK DEVICE TYPE; # by default

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / opt/oracle/base/product/11.2.0/dbhome_1/dbs/snapcf_mseos3.f'; # by default

  Everything works fine as long as the two sites are on the rise, & I have cron job to remove the archive log has expired.

  Now, if I stop the secondary node, the head node site also goes to error state & watch special suite:

  ERROR:

  ORA-00257: archiver error. Connect internal only, until this just released.

  I checked the size of the log archive and its just Mo 837...

  My expectation is it should continue to operate until all 70 G are used. why he throws error so early? Please give me some advice if Im missing something here...

  ~ S.

  Do you mean by reliable?

  It will be permanent if you apply via dgmgrl database pending:

  Change the property set of database my_standby_db Binding = "optional."

  See the detailed database my_standby_db

  You must ask it also on the primaries for the cases of change of role, but for now, you need to change it for the day before to take effect.

  If the archivelogs can be deleted are beeing shipped in standby mode.

  Making the optional standby destination will prevent them from beeing deleted primary until shipped it standby after the host is again.

  Concerning

  Thomas

• Insert into a primary database of Eve Active Data Guard

  I use Oracle EE 11.2.0.3.8 on Solaris 10.

  I read that it is possible to do an insert in my database for the standby Active Data Guard by redirecting the insert to get on the primary via DB link.  I GLOBAL_NAMES set to TRUE and he needs to stay that way.  This means that I can't create a DB link pointing to my first as such:

  CREATE DATABASE LINK PROD. WORLD WITH THE HELP OF "PROD_PRIM";

  How can I get around this in order to insert data in my standby ADG primary?

  Hello;

  There is an article about it here by Uwe Hesse:

  http://uhesse.files.WordPress.com/2012/03/realtimequery.PDF

  I understand that if GLOBAL_NAMES is true, then, the database link must have the same name as the database in which it connects.

  Best regards

  mseberg

• Data Guard: Pending Replication does not work.

  Experts,
  
  I ran the command on the database of the relief below:
  
  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
  
  I thought that this command would bring all the recent changes immediately. However, after the execution of this statement, the replication does not occur. I mean that if I update something on the primary, is not reproduces on standby db.
  
  Later, I realized that this command is for switching ensures primary school.
  
  How to roll back the change above in mode sleep?
  
  Thank you

  Hello again;

  A. No.

  Real-time Apply
  
  SQL> alter database recover managed standby database using current logfile disconnect from session;
  

  B. it is my understanding, but I use this mode. E10700-02 having no approach for sleep, which seems a safe bet.

  Best regards

  mseberg

• steps for Data Guard with a primary eve and 2

  Hello
  
  Database: 10.2.0.4, 11.2.0.1
  Operating system: Windows, Unix
  
  A > primary database
  B > database ensures 1
  C > database ensures 2
  
  I want to configure * 2 Eve * databases for the single primary database.
  Allows to take, A, B and C are my machines. My Data Guard configuration will be like, * archive logs will be mobile * A to B and A to C.
  
  If I do all passage between and B , now that b is primary and remaining has and C are pending data bases. At this point also, Archives of the newspapers should move from B to A and B to C. In addition, even should arrive from C to A and C to B, if I make the passage between B and C. If all goes well, then I'll do switchback to the main database (A) primary.
  
  How should I mention PFILE in all machines , parameters like
  LOG_ARCHIVE_DEST_1 = LOCATION = < PATH > - LOCAL path ARCHIVE
  LOG_ARCHIVE_DEST_2 = SERVICE =
  LOG_ARCHIVE_DEST_3 = SERVICE =
  FAL_SERVER =
  FAL_CLIENT =
  STANDBY_FILE_MANAGEMENT =
  
  In my tnsnames.ora , primary, standby1 standby2 my service entrances and are even in all of my machines.
  
  Please suggest me, how can configure my pfiles in machines?
  
  Thank you
  Therese

  Please don't forget to update the thread with useful or correct, if you find the answer either.

  Kind regards
  SQuadri

• Using Oracle 11 g Data Guard disaster recovery

  Hi, can anyone answer if Oracle 11 g Data Guard by itself provides an option for making/switch between the main bases and emergency (back and forth) disaster and as a restoration solution, seamlessly? Here's the scenario:

  1. two databases (active and reserve)

  2 put it to sleep (make primary with read/write)

  3. restore to the original database

  Data Guard has two transitions of role... Failover and the digital switchover.

  Passage to the fact exactly what you describe. You can switch to standby and vice versa. However, this will not work unless the primary and the standby are available. If you will not be able to perform an operation of swichover when you have a failure in the main data center that makes the primary db not available.

  Failover will be the day before in a primary for the moments where the primary origin is not available. Unlike the digital switchover, failover is one-way. There is no 'restoration' of failover. If you do not failover, then once the old Center of main data is operational again and you can get the former primary database up, you must restore from the first news and make a watch for the first new. At this point, you can then make a pass to come back and run in the original data center.

  HTH,

  Brian

• Data Guard archive political deletion log

  Hi all

  I configured the data guard with 2 bases Eve in oracle 11g.

  I want to use rman to delete archives on all servers.

  I have configured no FRA, no recovery catalog.

  My question is:

  If I delete waiting til sequence # 1627 and on primary sequence til = # = 1620 or vice versa this would cause problems for Data Guard.

  I say delete until the different sequences # on primary and standby cause problems for synchronization?

  Thank you

  So if I understand delete archivelog to sysdate - or delete archivelog all completed before sysdate n is not the archivelog deletion policy you put on RMAN?

  She depends on it. The note was made at the base of the MOS document how ensure that RMAN is NOT delete archived logs that have not yet shipped to standby mode (Doc ID 394261.1)

  Delete archivelog to sysdate - depends on all of the deletion policy. If the deletion policy is set on "applied pending all", then it does not delete the archives, if they are not applied on the day before. If the deletion policy is set to none, then it does not check if the archive is applied on the eve and deletes them directly.

  Last Archive generated on primary:

  SYS@oraprim > select max(sequence#) from v$ archived_log;

  MAX(SEQUENCE#)

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

  114

  Last check-in applied in mode ensures:

  SYS@orastb > select max(sequence#) from v$ archived_log in case of application = 'YES ';

  MAX(SEQUENCE#)

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

  109

  Delete policy set to NONE on primary:

  RMAN > show archivelog deletion policy;

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name ORAPRIM are:

  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;

  RMAN > delete archivelog until 'sysdate;

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 60 type of device = DISK

  List copies of newspapers archived to database with db_unique_name ORAPRIM

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

  Thrd Seq S key low time

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

  110-1-214 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727

  216-1-111 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731

  217-1-112 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731

  113. OF 1 219 A 13 JANUARY 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733

  222 1 114 A JANUARY 13, 16

  Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737

  You sure you want to delete the items above (enter YES or NO)? NO.

  It is the removal of primary archives that have not yet been applied on the eve.

  Delete policy 'APPLIES ON STANDBY ALL' value on the primary:

  RMAN > show archivelog deletion policy;

  RMAN settings for database with db_unique_name ORAPRIM are:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  RMAN > delete archivelog until 'sysdate;

  output channel: ORA_DISK_1

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 60 type of device = DISK

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727 thread = 1 sequence = 110

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731 thread = 1 sequence = 111

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731 thread = 1 sequence = 112

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733 thread = 1 sequence = 113

  RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737 thread = 1 sequence = 114

  It checks if the archive has been applied on the day before. As the 110 to 114 sequence is not applied in the waiting, the archives are not deleted on the primary.

  Hope that gives you a clear picture of how it works.

  -Jonathan Rolland

• Mrp for RAC RAC Data guard configuration configuration

  Grid infrastructure: 11.2.0.4

  DB version: 11.2.0.4

  OS: RHEL 6.5

  Never configured dataguard to the prior CFR.

  We have a production of 3 CARS DB nodes and we plan to implement a physical standby 3-node DB with real-time applies for this prod DB.

  

  In a RAC database, we can only configure one mrp on the side waiting. Thus, apart from the day before, we decided to use Node3 to run MRP. We send redo all instances as stated above on the primary side

  Configuration side Step1.Primary

  Thus, in the all 3 instances of primary DB, we will configure LOG_ARCHIVE_DEST_2 as follows.

  Again all 3 instances should now point to Instance3 Node3 break-in:

  ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 = 'service =acmsprd_dr0_tns delay LGWR SYNC AFFIRM = 0 DB_UNIQUE_NAME = acmsprd_dr0 VALID_FOR = (primary_role, online_logfile)' scope = both;

  Where acmsprd_dr0_tns is the following entry of TNS. As you can see, this name TNS tip to the side instance3 ensures

  acmsprd_dr0_tns =

  (DESCRIPTION =

  (ADDRESS_LIST =

  (ADDRESS = (PROTOCOL = TCP) (HOST = yrmst197 - vip3.apac.strcld)(PORT = 1521) .net)

  )

  (CONNECT_DATA =

  (SERVICE_NAME = acmsprd)

  (INSTANCE_NAME = acmsprd_dr03)

  )

  )

  Configuration of Step2.Standby side:

  Instance3 side Eve in Node3 in, start the MRP with real time apply

  sqlplus / as sysdba

  bootable media;

  change the database recovery managed standby database using the current log file disconnect;

  Nothing wrong with my steps above? Is there anything else I should do with respect to mrp?

  Thus, apart from the day before, the RFS process in each node will apply again he received primary for SRls independently to know if the mrp runs in this node. Right?

  Incorrect answer. RFS does not apply again as you said. RFS receives that again. However, RFS on all standby nodes can receive redo of any process of LNS on any node of the primary.

  It is the MRP which makes it apply, no RFS.

  Hi Brian,.

  You said

  "It is not necessary to attribute a SRL to a specific thread. This means that it is possible (and this is how I set up my backup RAC databases) for a SRL be used by any instance, no thread. »

  When you configure dataguard RAC DBs Eve (or primary DBs), add you the newspapers of recovery sleep without THREAD clause as below?

  alter database add standby logfile Group 1 ('+ ORL_DG1', '+ ORL_DG2') size 500M;

  alter database add standby logfile Group 2 ('+ ORL_DG1', '+ ORL_DG2') size 500M;

  alter database add standby logfile group 3 ('+ ORL_DG1', '+ ORL_DG2') size 500M;

  I dot does not specify a thread when creating my SRls. There is no reason to do so. Just that if you have X son of your primary and each thread has groups of newspapers make there, and then create of X * Y SRL in the day before.

  While you create the SRls, remember to create in primary school as well. You'll want them at the primary level to support the transition to the future operations.

  If this is the case, in any node Eve RFS can apply again to roll forward pending any newspaper in the standby database. Right?

  Often when people have discussions like this, it hurts ensure us that we are semantically correct otherwise, we can easily get confusing terms...

  In this case, RFS can write to any SRL, since they won't be assigned to a specific thread. And the SRL is not written in alternating as the ORLs. Then you can definitely see some of the SRL files never get used if you don't have enough flow to make to justify.

  I stay away from the term applies when the MRI because apply is that means MRP. Terms of mixing can sometimes lead to confusion on the road, that's why I would make sure to use the term appropriate to the discussion at hand. I started this answer indicating that RFS is not the 'applies' because of the way the term should be used. That I get to this part of your last post, I see that maybe we get mixed up words that's why I wanted to sort them.

  See you soon,.
  Brian