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

Similar Questions

• Pending passage of the primary database to database

  Hi Experts,
  
  There is a database of oracle 10 g on a windows server and the database pending 1 * 0 g on another windows server *. The archivelogs in the primary database are generated on a network drive and they are applied on a regular basis of the primary database to the standby database, but now the primary database server broke down. If someone can tell me how to failover the database ensures the primary. I followed these steps but still Iam unable to move forward
  
  on the standby server:
  
  1 rman target sys/oracle@standby catalog rman/rman@catalog
  2 recover database;
  3 output
  4 sqlplus sys/oracle@standby as sysdba
  5 change the recovery of database managed standby database disconnect from the session;
  6 alter database recover managed standby database finish;
  7 change the database for validation at the grade crossing;
  
  All records of the primary database in the backup catalog are applied with success, until no 6 but not 7 would give me an error indicating that the required media recovery. Can someone help me?
  
  Thanks in advance...

  HI srp.

  As u mentioned above you are primary database server crashed.

  Now, you want to switch to mode ensures primary school.

  Use the following commands to go to primary school

  1 startup nomount
  2. change the mounting base pending;
  3. recover standby database managed disconnect from the session.
  4 recover managed standby database finish skip standby logfile;
  5 change the database for validation at the grade crossing;
  6. immediate cessation
  7. starting

  Otherwise, you need to activate the standby database using the command sequence

  SQL > recover managed database finish pending;
  SQL > alter database activate standby database;
  SQL > stop & start.

  Kind regards
  Praful K

• Passage of the roles - ensures primary school

  Hi all

  We have a requirement in our environment to switch mode on primary eve. This is to stop the machine from primary database since it is now more than 350 days.

  I have a few crossing the reg of doubts.

  We have two servers

  1 Server1-Prim - main database hosts with SID - LPBT

  LISTENER - WITH SID-LPBT ON 1521 PORT WITH HOST = 80.0.1.187

  TNSNAMES with entries for the two services LPBT and STBYLPBT

  2 Server2-Stby - secondary database hosts with SID - STBYLPBT

  LISTENER - WITH SID-STBYLPBT ON PORT 1521 WITH HOST = 80.0.0.240

  TNSNAMES with entries for the two services LPBT and STBYLPBT

  Our is a physical standby and passage procedure below of the manually using SQL commands instead of dataguard

  Digital allows a primary and standby to switch roles without data loss.

  No need to recreate the old primary school. Conducted for a scheduled maintenance.

  Steps to follow:

  1. check if primary can be switched to sleep mode

  SQL > select switchover_status from database v$.

  If returns the value "TO_STANDBY", its good to pass the primary role of Eve.

  2 convert primary to standby

  SQL > alter database validation to the transition to physical standby mode;

  If the value is "ACTIVE SESSIONS" in step 1, then

  SQL > alter database validation to the transition to physical standby with the stop of the session;

  3. stop and restart the old primary as before

  SQL > shutdown immediate;

  SQL > startup nomount;

  At this point, we now have two databases, such as the day before.

  4. on the basis of data target standby, check status of the digital switchover. If the value is "TO_PRIMARY" then

  SQL > alter database validation at the grade crossing;

  If the value is "ACTIVE SESSIONS", then add "WITH the STOP of the SESSION" to above the command.

  5. stop and restart the new primary database

  SQL > shutdown immediate; start-up;

  6. start back on new database (former primary) pending

  SQL > alter database mount standby

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

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

  My question is after the transition to digital, if we connect as 'conn sys@lpbt as sysdba' since sqlplus window from another pc, how the request will go to the new primary database server (80.0.0.240) since tnsnames only will point to the old principal server (80.0.1.187).

  can you please explain how it works, or should we add a few more entries to the listener or files tnsnames.

  Please notify

  We have three databases and we use the db_links inside these three db for transactions

  so can we not use as main stbylpbt, as db_links does refer to db_link-host - lpbt solve in tnsnames who will fail.

  Yes, you are right. You have to re-create these links db to point to your new primary database ("old Standby") using guests as "STBYLPBT".

  As mentioned previously, you must redirect all your applications and users to point to the new primary database by making use of the "STBYLPBT" entry TNS.

  in this case, after the success, if we need to change db_names (vice_versa) and listeners as was before

  You don't have to do anything with regard to the 'db_name' or with the listener. Db_name remains the same on the primary and implementing standby.

  I don't understand the reason for you to change the listener. 1 listener on the server must be able to accept connections.

  80.0.0.240 is your host before and there is a listener on this. After a failover, it becomes your primary database. You would try to connect to the new primary database with input TNS "STBYLPBT." It reminds the host '80.0.0.240' which is your new primary database. Hope this clears.

  STBYLPBT =

  (DESCRIPTION =

  (ADDRESS_LIST =

  (ADDRESS = (PROTOCOL = TCP) (HOST = 80.0.0.240)(PORT = 1521))

  )

  (CONNECT_DATA =

  (SERVICE_NAME = stbylpbt)

  )

  )

  -Shivananda

• 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

• RMAN-06820: WARNING: unable to archive the current log on the primary database

  I got the following exception when I try to backup the data files and the archivelogs on the physical by uisng RMAN standby database.

  RMAN-06820: WARNING: unable to archive the current log on the primary database

  Target ORACLE database error:

  ORA-17629: unable to connect to the remote database server

  ORA-17627: ORA-00942: table or view does not exist

  It's the backup script

  "

  connection target sys/oracle

  Configure controlfile autobackup on;

  Run {}

  nocfau together;

  allocate channel ch01 device type disc format ' / test/%U';

  allocate channel ch02 device type disc format ' / test/%U';

  backup database copy archivelog;

  backup copy current controlfile;

  }

  "

  And there is no error ora in the primary alert log.

  I was able to tnsping two server (primary/secondary) properly and could also primary of the remote login on standby db server and switch logfile. I read there is a very similar thread, but it has failed so I post again and hope I could get a few clues. Thank you.

  Hello again;

  Try to change this:

  connection target sys/oracle

  to something like this:

  RMAN target sys/password@PRIMARY auxiliary.

  Complete example:

  http://www.Visi.com/~mseberg/data_guard/duprman2.html

  Best regards

  mseberg

• Delete pending roll forward primary database journal

  Hi all
  
  I'm trying to drop the standby logfiles on the primary database (database that I am setting the DG).
  Members of the groups of newspaper pending exists on the file system.
  Someone has deleted these files. His old configuration where the files are in the file system. They are now in ASM.
  When I try to delete the logs on hold I got the following error:
  

  SQL> alter database clear logfile group 7;
  alter database clear logfile group 7
  *
  ERROR at line 1:
  ORA-19528: redo logs being cleared may need access to files

  SQL> select * from v$logfile order by 1;
  
      GROUP# STATUS  TYPE    MEMBER                                                                           IS_
  ---------- ------- ------- -------------------------------------------------------------------------------- ---
           1         ONLINE  +REDO1/proj/onlinelog/group_1.256.340558657                                     NO
           1         ONLINE  +REDO2/proj/onlinelog/group_1.256.340558659                                     NO
           2         ONLINE  +REDO1/proj/onlinelog/group_2.257.340558879                                     NO
           2         ONLINE  +REDO2/proj/onlinelog/group_2.259.340558879                                     NO
           3         ONLINE  +REDO1/proj/onlinelog/group_3.258.340558707                                     NO
           3         ONLINE  +REDO2/proj/onlinelog/group_3.257.340558709                                     NO
           4         ONLINE  +REDO2/proj/onlinelog/group_4.258.340558713                                     NO
           4         ONLINE  +REDO1/proj/onlinelog/group_4.259.340558711                                     NO
           5         ONLINE  +REDO2/proj/onlinelog/group_5.260.340558965                                     NO
           5         ONLINE  +REDO1/proj/onlinelog/group_5.260.340558963                                     NO
           6         ONLINE  +REDO1/proj/onlinelog/group_6.261.340558967                                     NO
           6         ONLINE  +REDO2/proj/onlinelog/group_6.261.340558967                                     NO
           7         STANDBY /oracle/proj/onlinelog2/redo_702.log                                            NO
           7         STANDBY /oracle/proj/onlinelog1/redo_701.log                                            NO
           8         STANDBY /oracle/proj/onlinelog2/redo_802.log                                            NO
           8         STANDBY /oracle/proj/onlinelog1/redo_801.log                                            NO
           9         STANDBY /oracle/proj/onlinelog2/redo_902.log                                            NO
           9         STANDBY /oracle/proj/onlinelog1/redo_901.log                                            NO
          10         STANDBY /oracle/proj/onlinelog1/redo_1001.log                                           NO
          10         STANDBY /oracle/proj/onlinelog2/redo_1002.log                                           NO
  
  20 rows selected.
  
  SQL> select * from v$standby_log order by 1;
  
      GROUP# DBID            THREAD#  SEQUENCE#      BYTES       USED ARC STATUS     FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
  ---------- ------------ ---------- ---------- ---------- ---------- --- ---------- ------------- --------- ------------ ---------
           7 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0
           8 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0
           9 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0
          10 UNASSIGNED            0          0  104854601        512 YES UNASSIGNED             0                      0

  What can I do to make it give up these reference?
  Any other solution instead of modify the controlfile and stop/start the database?
  
  Thank you!!!

  Hello;

  Think that Oracle, the files are there, but I still have a bug on metalink where the controlfile had them again, but they were not on the file system. Can you confirm that they exist?

  Meanwhile, I'm checking my notes for the Oracle number of doc.

  Bug 6128242: TRY TO drop the STANDBY LOG FAILED WITH ORA-19528

  So if you're Oracle 10, this could be the problem.

  workaround is to re-create the controlfile without the incorrect log file. (Ugh!)

  ORA-01156 when adding or deleting Redo Logs [ID 452152.1]

  Best regards

  mseberg

  Published by: mseberg on October 31, 2011 17:09

• Re-instantiate a primary database with 10 g Release 1

  How can you re-instiate the primary database with 10g Release 1. I'm studying how the failover process works and have switched successfully to a wait.
  
  I want now to re-instantiate the primary... I know in Release 2 there is a re-instantiate DGMGRL command... but the command is not in Release 1 that I can see.

  Hello

  You must do it manually

• Retrieve the primary database before database

  Hi all
  I'm trying to understand how to use databases of physical sleep in order to have a backup from a primary database.
  
  The first part is very clear. I guess I have a loan of the physics of the standby database and primary database archiving, but the second part is the problem.
  
  1. now, I guess my primary database went... not only a logical corruption but a physical disaster such an o fire something worse.
  How to recover the main site of the physical database ensures?
  
  2. just logical changes in the primary database. How to synchronize with the database on hold that he is one who has the right data?
  
  
  Thanks in advance.
  
  Published by: jsfelix on November 18, 2009 04:48
  
  Published by: jsfelix on November 18, 2009 04:51

  If you lose the database, then you normally would failover to the standby mode it becomes the main new.

  So you take a backup of the first news and use it to create a watch on the former primary server. When it is updated, you can then pass to the original configuration.

• MyFileName.mdf is not a primary database file.

  When accessing an .mdf file, I get this: MyFileName.mdf is not a primary database file. This means that the file is corrupted?

  Please help fix this file. I learned a few manual things to fix the SQL database, but I'm not aware of it.

  Please share it.
  Thank you.

  Philippe

  This issue is beyond the scope of this site and must be placed on Technet or MSDN

  http://social.technet.Microsoft.com/forums/en-us/home

  http://social.msdn.Microsoft.com/forums/en-us/home

• Error blackBerry software - synchronization failed, impossible to deal with organizing data

  I had a Q10 Blackberry last week.  I downloaded and installed the PC of Blackberry link 1.2.2.13 version.  Two-way sync USB worked fine.  Now, all of a sudden, I get the error message "synchronization failed, impossible to deal with organizing data."   I tried to reset the synchronization options, but not joy.  Also tried to uninstall and reinstall the software Link 1.2.2.13, once again no joy.  Any suggestions?

  UPDATE: I spent 4 hours on the phone and the remote session with the help of Blackberry last night.  After doing some troubleshooting to isolate the problem, determined that something on the device caused the problem of Outlook synchronization. One thing I've learned, it's that it can take a long time to synchronize and even though the progress of the screen may appear frozen, let it go until the end - sometimes it took 20-25 minutes, but eventually completed. Here's the process we went through - I would recommend appellant help BB and work with them to make sure you have not accidentally delete Outlook contacts and calendar of important information of your PC or BB device!.

  (1) we tried an uninstall/reinstall the PC Link BB software and that did not fix the problem.

  (2) to isolate the problem of synchronization.  We first did a synchronization of 2 channels 'contacts' and 'calendar' and who was a failure.  Then did a synchronization of only 2 channels 'contacts' and managed.  Then did a synchronization of only 2-way 'calendar' and that was a failure - so the problem was linked to calendar data and something on the device has been the cause of the problem or corrupted.

  (3) link BB allowing us to make a backup complete unit.

  4) then decided to do a 'Wipe security' on the device of BB Q10 to erase all the data and settings and return to a clean boot device configuration.  I was nervous about it - make double sure that Outlook all contacts and calendar data on the device and the PC are completely backed up in case something bad happens.  Nothing serious happened, but I was gald, we made the backup!

  (5) has the 'Security Wipe' feature (on the device, the settings > Security and privacy > wipe security) and phone rebooted without problems (takes a while to do).
  

  (6) then used link BB to do a sync test 1 channel 'contacts and calendar' from PC to device.  It worked without problem.

  (7) we then used BB link do a "restore" full backup of device, as we did in step 3 above.  It takes a while to make and was a success.

  (8) once the restoration of the aircraft was complete, BB link configured to perform a synchronization of 2 channels of the two 'contacts' and 'calendar '.  Does the synchronization and was a success.  Did a test by adding the new entry of the calendar on PC and did another 2-way sync - all worked very well.  Seems that the problem has been corrected, but will follow in the coming days.

  Lessons learned:

  (1) If you have a lot of Outlook contacts and calendar entries, the synchronization may take a long time.  Be patient and let it run - even if it seems stuck, etc!

  (2) save all Outlook data on the device and the PC to make sure that you have a backup something bad happened during troubleshooting.  We had not something bad happens, but I was gald we made a backup anyway.

  (2) call BB help - support person, I worked with was fabulous, even if it took some time to work through a patch.

   

• I used to work with Interbase and Firebird and used databases the keyword "domain". I am now switchig to Oracle as a primary database and would like to find an alternative appropriate "domain" in Oracle, as it appears he does ' t taken in charge the stand

  I used to work with Interbase and Firebird and used databases the keyword "domain".

  I am now switchig to Oracle as a primary database and would like to find a suitable

  Variant of 'area' in Oracle such that it appears he does ' t support the standard SQL syntax.

  for example:

  Create the int2 smallint field;

  create domain id2 int2 default 0 not NULL; / * for the primary key * /.

  create domain rel2 int2 default 0 not NULL; / * foreign key * /.

  I tried a couple of approaches to achieve this "area" is:

  1. create synonym - cannot be used with the basic types;

  2. create the type - type of work, but the implementation is rather clumsy

  and can be costly in terms of performance.

  Is there something else to Oracle that can emulate the feature "domain"?

  Thanks in advence, I got really approciate any help on this.

  Alex.

  Your best approximation is CREATE TYPE, but their is nothing of what is a 100% adjustment.

  For example, if you create a domain with a check constraint you need to implement than separately on each table.

• logfile missing watch on the primary database

  In a 11.2.0.4 database, we have configured Data Guard, so they created pending log files, but it has been deleted in ASM + accidentally.

  Thus, research in the database primary, the newspaper observed log pending files, but is not in ASM +.

  In the alert log has not been recorded event.

  I can do the recreation of the eve logfiles?

  What role can have on the primary database?

  Our configuration:

  BECAUSE with 4 cases

  --

  logonline 5 groups for example

  each group of logonline with 2 members

  --

  6 standby of the group e.g.

  each group watches with 2 members

  Total 48 asm file missing

  Select *-Group #, Member

  v $ logfile where type = "STANDBY".

  order by group #.

  GROUP # STATUS TYPE MEMBER IS_RECOVERY_DEST_FILE

  No. 51 +DATA_EXA/prep/onlinelog/group_51.1613.804140169 EVE

  No. 51 +RECO_EXA/prep/onlinelog/group_51.2918.804140175 EVE

  No. 52 +DATA_EXA/prep/onlinelog/group_52.1614.804140479 EVE

  No. 52 +RECO_EXA/prep/onlinelog/group_52.4182.804140485 EVE

  ....

  .....

  74	No. +DATA_EXA/prep/onlinelog/group_74.972.875418965 day BEFORE
  74	No. +RECO_EXA/prep/onlinelog/group_74.14330.875418971 day BEFORE

  ASMCMD >

  ASMCMD > ls-l +DATA_EXA/prep/onlinelog/group_74.972.875418965

  ASMCMD-8002: entry 'group_74.972.875418965' does not exist in the directory ' + prep/DATA_EXA/onlinelog /'

  ASMCMD >

  ASMCMD >

  Redologs Eve will be active when the database is in the role of Eve, so you can drop the watch group redologfile missing for the thread and add it again.

  You have lost all the groups newspaper waiting for redo for all threads?

  On primary, you can drop all odds redolog groups because they will be unassigned State on the standby database make sure the group is unassigned status before falling

  Select Group #, THREAD #, STATUS from v$ standby_log;

• No index on the primary database. Need help with "COUNT OFF"; option

  11 GR 2 11.2.0.3 under linux

  Hi everyone,.

  It's an honor to be with you guys.

  I have a big question here and I am unable to decide on a permanent solution.

  We have a primary database that is configured to have a logical expectation.

  The logic of the day before was not built by me. But I'm now support...

  So as the title suggests, there is NO primary index / unique + not null on a large number of tables in the database of emergency primary/logic. But the application logic guarantees uniqueness values rather than null.

  Here is where the problem starts.

  Guys request DO NOT want us to create an index on the primary database.

  According to my understanding, because the database lack of clues, the apply SQL must do a full table scan whenever it changes / remove data. It is a very expensive process and consumes a lot of time. This takes hours together to apply a minute with a value of newspapers on the logic of the eve... A huge lag is created during the hours and is not acceptable.

  So as I told you earlier, the guys request do not want an index on the tables not supported.

  They use the database pending logic exclusively for information purposes and it's like production for them...

  
  Let me give an overview...

  According to the document on the creation of the logic of the day before for 11.2 as below

  http://docs.Oracle.com/CD/E11882_01/server.112/e41134/create_ls.htm#SBYDB4730

  Step 1 to find tables without identifying unique logic in the primary database.

  Query the DBA_LOGSTDBY_NOT_UNIQUE view to display a list of tables SQL may not apply be able to uniquely identify. For example:

  SQL> SELECT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_NOT_UNIQUE

   2> WHERE (OWNER, TABLE_NAME) NOT IN 

  3> (SELECT DISTINCT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED) 

  4> AND BAD_COLUMN = 'Y'; 

  The above query has 1040 tables in a particular schema. All the these have no index is not null primary / unique.

  
  Now according to the step 2 as below, we have an option to add a disabled RELY primary key constraint.

  Step 2 Add a disabled RELY primary key constraint.

  If your application provides the rows in a table are unique, you can create a primary key disabled RELY constraint on the table. This avoids the overhead of maintaining a primary key on the primary database.

  Can someone explain what this RELY constraint is disabled and how to function and help please?

  
  I have a few questions about the constraint to RELY.

  (1) change current plans of optimizer on primary for the execution price?

  (2) can help to boost the performance of SQL apply without creating index on the logical standby database?

  (3) it will change current plans of optimizer logical pending for the SQLs running?

  What are the options that I need to increase the performance and table scan complete engine AVOID SQL apply on the logic of the day before?

  Thanks a ton for reading my post.

  
  Kind regards

  Abhishek

  In fact, I've implemented a key primary rely disabled on primary and unique index on the logic of the previous day.

  The logic of Eve runs lightning fast now

• Effects of the opening of a primary database in resetlogs on the standby database

  Hi all

  Operating system: Solaris

  DB: 11 gR 2

  Can anyone throw some light below the explanation is given in case of recovery through the OPEN RESETLOGS Statement oracle documentation

  If the database pending...	Then...	Perform these steps...
  Not asked to redo data beyond the new resetlogs SCN (after the start of the new branch of data recovery)	Redo apply automatically takes the new branch of the roll forward.	No manual intervention is required. The MRP automatically resynchronizes the database pending with the new branch of data recovery.

  Here is the link of the source:

  Manage a database of physical standby

  Kind regards

  Just to give a concrete example, I did a test on one of my VM boxes. The database currently shows:

  SQL > select sequence #, the journal of v status $;

  SEQUENCE # STATUS

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

  34 ACTIVE

  CURRENT 35

  ACTIVE 33

  While on the eve, I stopped the redo apply so the standby status is:

  SQL > select sequence #, used from v$ archived_log;

  SEQUENCE # APPLIED

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

  YES 30

  31 YES

  32 YES

  33 NO.

  34 NO.

  The database ensures in a few newspapers behind the primary.

  On the primary, I moved the journal a few sequences, close, the bootable media and restored and recovered 37 sequence:

  RMAN > run

  2 > {}

  3 > restore database;

  4 > up 37 sequence;

  5 > restore database;

  6 > alter database open resetlogs;

  {7 >}

  During the open resetlogs operation, I have to tail the log of alerts on the standby database and the following output shown:

  RFS [11]: identified the type of database such as 'physical' standby: customer is ARCH pid 17192

  RFS [11]: new branch archives REDO: 844006029 current: 843649185

  RFS [11]: Journal selected 102 for thread 1 1 dbid-204899919 branch of the 844006029 sequence

  RFS [11]: new Branch (resetlogs_id) of archive REDO: before 844006029: 843649185

  RFS [11]: ID of Activation of archives: current 0xf3d44942: 0xf3cf5ac3

  RFS [11]: effect of primary database OPEN RESETLOGS

  RFS [11]: entry of Incarnation added to Branch (resetlogs_id): 844006029 (ORCL11PS)

  Fri Apr 04 14:07:39 2014

  Definition of embodiment of recovery target 2

  Fri Apr 04 14:07:39 2014

  Archived journal 21 additional for each sequence 1 1 0xf3d44942 dest ID thread entry 1:

  So as you can see, the log shows the standby detects the resetlogs on the primary operation and the new branch of the roll forward and received the next archivelog with sequence 1.

  Audit on the eve, it shows the status following the archivelogs:

  SEQUENCE # APPLIED

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

  31 YES

  32 YES

  33 NO.

  34 NO.

  35 NO.

  36 NO.

  37 NO.

  38 NO.

  1 NO.

  2 NO.

  And after restart the managed recovery process, it now shows:

  SEQUENCE # APPLIED

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

  31 YES

  YES 30

  YES 19

  YES 33

  34 YES

  35 YES

  YES 36

  37 NO.

  38 NO.

  1 YES

  2 YES

  Archivelogs with sequence 37 and 38 were not implemented because of the CAMILLE on the main sequence until (but not including!) 37 and then properly applied the next archivelogs of the new branch of the roll forward, with sequence 1 and 2.

• How the standy database reflects the primary database?

  in the primary database create a tablespace or datafile adding / resizing then what happens to the standy database

  [url http://docs.oracle.com/cd/B14117_01/server.101/b10755/initparams206.htm] STANDBY_FILE_MANAGEMENT