Redo Log apply after reboot pending

Similar Questions

• How do I know the delay in the redo log apply on Active 11g Dataguard

  Hi all
  
  How do I know the delay in the redo log apply on Active Dataguard 11 g...
  
  Do we need to wait until the log switch occurs?
  
  Or is it recommended to provide a switch to log every 15 min, regardless of data is updated / inserted in primary school or not?
  
  Please suggest...
  
  Oracle: oracle 11g Release 2
  OS: RHEL 5.4
  
  Thank you
  
  Published by: user1687821 on February 23, 2012 12:02

  apply for time of arrival + 00 00:00:00.0 day (2) to second (1) interval February 23, 2012 03:02:16

  Here apply finish time is 'Zéro' if there are gaps in log files, this parameter shows the time it will take to resolve the discrepancy.

  apply the offset + 00 01:50:49 day (2) second (0) interval February 23, 2012 03:02:16
  transportation of shift + 00 01:50:49 day (2) second (0) interval February 23, 2012 03:02:16

  the time that redo data is not available (or) on the basis of data behind pending with the primary database.

  SQL >! date
  Thu Feb 23 03:03:34 CST 2012

  If you see your date system current and last does the end is not even a second. So probably there is no delay I would say.
  You can test by setting the timeout setting in log_archive_dest_2 (or) disable log_archive_Dest_2 for a while do two or three switches of newspaper and made attention to discrepancies between primary & eve and how does it point of view.

• Redo log shipping after a stop pending physical

  Hallo,

  I just have a question for redo log shipping

  in a configuration simple primary/secondary 11g.

  In a shutted down an instance physical standby, redoshipping is active? Primary redo file transfer is still ongoing?

  Thanks in advance

  Hello;

  I'm not going to say no. I still SEE on the primary side before I shutdown, maintains false alarms from happening.

  Test

  Using this query

  http://www.mseberg.NET/data_guard/monitor_data_guard_transport.html

  DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP

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

  TDBGIS01B PRIMARY 5558 5557 21-OCT/12:51 1

  Stop waiting

  SQL > alter database recover managed standby database cancel;

  Database altered.

  SQL > shutdown

  ORA-01109: database is not open

  The database is dismounted.

  Journal of strength comes on primary side

  SQL > alter system switch logfile;

  Modified system.

  (3)

  Journal of before was 5558 check so make sure 5559 or higher

  Last log is

  o1_mf_1_5558_c2hn5vdf_.arc

  Wait a few minutes, no change

  Best regards

  mseberg

• Question on create Redo log after restoring files and recover

  Log files to rebuild RMAN backup? Below the blog describes the steps to restore and recover a RMAN backup in a new host.
  http://blog.CSDN.NET/sweethouse1128/article/details/6948273
  
  
  RMAN seems to have backed up and restored the redo log files
  
  
  After the resumption, blogger issues

  select * from v$logfile;

  and the result obtained some log files. The rows returned are restored files redo log. right? Redo of RMAN backup and restore log files?

  Redo of RMAN backup and restore log files?

  N ° never. Even when you do a 'coherent' backup (i.e. with the database MOUNT but the mode is not OPEN).

  When you restore a full RMAN on a new server backup, RMAN restore REDO LOG files in the respective directories

  Does not apply because RMAN does not save logs in restoration online.

  Isn't better to manually create redo log files after restoration

  When you perform incomplete recovery, you must issue an ALTER DATABASE OPEN RESETLOGS.
  The RESETLOGS creates log files remake it, if they are not present OR reset them if they are present.
  In a scenario of complete restoration, the online redo log files are already present on the drive (i.e. they are not lost or destroyed and they are not restored a backup).

  Hemant K Collette

• Create the REDO Logs after restoration of RMAN

  Version 11.2
  Platform: Solaris 10
  
  We restore the cold RMAN backup to a new server. It's a basic restore RMAN where DB name remains the same.
  
  I understand that RMAN backup online redo logs, and for good reason.
  
  We have restored our datafiles successfully. The control file still has the old entries so the query below shows old information about recovery logs
  
  -Display of the configuration of the log file the old control file data

  SYS > select * from v$logfile;         ------------> The below output shows the result of the source server
  
      GROUP# STATUS  TYPE    MEMBER                              IS_
  ---------- ------- ------- ----------------------------------- ---
           1         ONLINE  /DATAM/DB/oradata/slmps/redo1.log      NO
           2         ONLINE  /DATAM/DB/oradata/slmps/redo2.log      NO
           3         ONLINE  /DATAM/DB/oradata/slmps/redo3.log      NO

  I have to use ALTER DATABASE RENAME FILE command as below to update the control file.

  alter database rename file '/DATAM/DB/oradata/slmps/redo1.log' to '/data/oradata/slmps/slmps_log01.dbf' ;
  alter database rename file '/DATAM/DB/oradata/slmps/redo2.log' to '/data/oradata/slmps/slmps_log02.dbf' ;
  alter database rename file '/DATAM/DB/oradata/slmps/redo3.log' to '/data/oradata/slmps/slmps_log03.dbf' ;  

  Currently, in the new server, at the level of the BONE there is no physical file above to
  

  /data/oradata/slmps

  I need to create physically redo new logs using the command or the command ALTER DATABASE RENAME above key create a physical file at the level of the BONE?

  Salvation in spiral,

  Surely, RMAN will search for redo logs when RECOVER is issued.

  When you issue the command RECOVER after restore, RMAN does not check online redo logs. During RECOVERY, RMAN will try to apply the archivelogs or incremental L1 if it has been saved on the source server. RMAN Backup restorations online redo logs or never.

  Here OP tries to restore the backup from the cold to a new server. In this case the RECOVER command is not necessary. The example of the Oracle doc you mentioned should do a restore, recovery of a backup hot. In this case, during the RESTORATION, RMAN will try to apply archivelogs or L1 of the incremental backups.

  In both cases (cold backup restore or restore, recover from Hot Backup), it is the

  alter database open resetlogs
  

  command that will create the online redo log, so it is absent in the location specified by the control file. Because it is a restoration to a new server, recovery logs is missing because it has not been restored (because it has not been saved)

• Reg apply log archiving after the transfer of data files

  Hi all
  
  That I reinstalled the main server of the D-Drive E-reader data files using the command line.

  C:\>Move <source_path> <destination_path>

  The redo logs for the move operation will apply on the eve of the database?
  In addition, what happens if the data files are moved manually in the primary database (i.e. without using the command prompt)?
  
  
  Thank you
  Madhu

  See this doc. Keyword search Rename a data file in the primary database

  http://docs.Oracle.com/CD/B28359_01/server.111/b28294/manage_ps.htm#i1034172

  Also, you need to update primary database controlfile if some moment of the file made...

  And also close this thread

  Reg apply log archiving after the transfer of data files

  As it would help in the forum of maintenance to clean.

• "Can not open AsIO.sys (2)" I get this message when I log in after a reboot. I have search for the file, but can't find it with the research or the command prompt. What do do in this file, and can be created and put into the appropriate folder?

  "Can not open AsIO.sys (2)" I get this message when I log in after a reboot.  I have search for the file, but can't find it with the research or the command prompt.  What do do in this file, and can be created and put into the appropriate folder?

  Hi Jack,

  This driver belongs to AsIO.sys Asus Probe. Try to uninstall Asus Probe and if you need, install again. If this does not help, uninstall Asus Probe and other tools of control such as Speedfan. Open the registry (regedit.exe) editor and search for AsIO.sys and remove all the entries that you can find.

  André
  "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• How to replace the members of the Group missing redo log after the failure of a support

  Hello

  I'm testing a disk failure scenario.  I had recovery multiplexes on three sites (Windows drive letters) logs; one of the three locations also contained the data files.  I deleted the Windows player that contained data files and saw a restoring with RMAN.   All is well except that redo log members who are found on the occult Windows disk are of course still missing; the database opens, etc., but puts messages like this in the ALERT.log:

  ORA-00321: log thread 2 1, cannot update log file header
  ORA-00312: wire 2 1 online journal: ' F:\APP\NGORA12CR2SRV\ORADATA\ORATEST5\ONLINELOG\O1_MF_2_BW4B5MY0_. JOURNAL"

  
  

  What is the 'right' way to replace missing limbs?  Just get all the new groups of newspapers with new members on all three discs?  Carefully copy the LOG files representing missing members of one of the other sites?  I add new members at this location and remove existing members (missing)?

  
  

  Is how important it?

  
  

  Thank you!

  
  

  Martin
  

  See 'Recover after losing a member of a group of Redo Logs online multiplexed'

  at http://docs.oracle.com/cd/E11882_01/backup.112/e10642/osadvsce.htm#sthref2205

  Hemant K Collette

• Clusterware and/or CARS on separate storage, synchronized by applying the redo logs?

  Hello Experts,

  I am doing research on architectures high availability to meet high service LEVEL requirements (> = uptime of 99.7 percent and "without loss of important data") for a client.

  I have few resources for the implementation of this architecture: two physical database servers running 11g Standard Edition (so Data Guard is not an option), Enterprise Edition is not an option because of the price. Data storage will be on a San.

  The ideal solution would be an architecture whose node redundancy (Clusterware / RAC) and redundancy of the data (as in physical Standby: application of redo logs instead of data mirroring (corrupt physical) files).

  I did research Clusterware and CARS, but they use a shared storage. I'll use a SAN for storage, but this will not prevent physical mirroring of the corrupt data files.

  Is it possible to set up a PAP/Clusterware architecture with each separate storage node, where the two databases are synchronized by applying the redo logs?

  Is it possible to instantly apply redo logs to minimize the loss of data in case of automatic failover?

  If we need more information, I'll give you a pleasure it.

  Thanks in advance,

  Peter

  A RAC cluster still need a shared storage for database files: each cluster node cannot have its own separate storage.

  You need at least a physical database server 3rd for the standby database that can function without Data Guard as long as you use you own scripts to send and apply archived redo logs or use a product like dbvisit.

  I don't think it's possible to apply again immediately without Data Guard.

• Path of redo logs after restoring controlfile

  Hello!
  
  After restoration of the controlfile I see distorted redo logs metadata (column v$ logfile.member):

  $OH/dbs/data/ora/MY_SID/rlog/redo1a.log

  in the redo logs placed in another directory, source database
  also I should drop logfile member and log file groups, and then create them again, but may be there other way to solve this problem?
  Please notify.
  I'm usung 11.2.0.3
  
  Thank you and best regards,
  Pavel

  As I said earlier, is that your database is working well? If so, then forget those files which are present in $OH/dbs/data/ora/file/rConnectez/MY_SID. Ok?

  Suppose now, the question is what are these files? Who created/copied?
  So the answer is if these files are used by your this database (MY_SID); that can be confirmed by query:
  Select Member from v$ logfile; then the redo logs are used by this database else chances are these files were the first part of this database, but not now due to may be a corruption that happened, so another / previous DBA has left.

  And if the database is not running, then what is the error you found it please post it here; otherwise leave these files such what.

  Concerning
  Girish Sharma

• Increased repository DB redo logging after upgrade EM12cR2?

  Has anyone else noticed increased redo logging in their repository database after upgrade to EM12cR2?
  
  I'm running on Linux x 86-64 with a 11.2.0.3 repository database. Before the upgrade, I was running 12.1.0.1.0 with BP1, and my repository database produced, on average, about 80-120 MB of archived redo logs / hour. Since the upgrade to 12.1.0.2.0, my product repository database, on average, 450-500 MB of newspapers archived redo / hour.
  
  Reclassification of deployed agents of 12.1.0.1.0 to 12.1.0.2.0 has not seemed to help; I've updated about 10 of the 15 without any apparent loss of logging of redo.
  
  I was wondering if it's comparable to what others see, or if I have a local question I should study.

  The following fix has been released for this problem:

  Patch 14726136 - INCREASED REDO LOGGING ON REPOSITORY DB AFTER UPGRADING TO OEM 12.1.0.2

  Kind regards
  Vincent

• Redo Logs after duplication 3 RAC node to node 2 RAC

  I use RMAN to clone my production database 10.2.0.4 (3 node RAC) in my test database (2 node RAC). When I finished, I find myself with the Redo Logs from the 3rd node RAC in a State of "weird." Newspapers of recovery for "thread 3", which does not exist, cause no problem, I want to clean them and reclaim the space.
  
  Ideas or suggestions?
  
  Thank you!

  Have you tried: -.

  ALTER DATABASE DISABLE THREAD 3.

• Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

  Here's my question after tons of research and test without have the right solutions.

  Target:

  (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

  (2) I created physical standby database "stbydb" on the server "node2".

  (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

  (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

  (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

  (6) I do RMAN backup (database and archivelog) on the site of relief only.

  (7) I want to use this backup for full restore of the database on the primary database.

  He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

  Here is how to save, on the database pending:

  (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

  (2) RMAN > backup database;

  (3) RMAN > backup archivelog all;

  I got elements of backup and copied to primary db Server something like:

  /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

  /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

  /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

  So here's how to restore, on the main site:

  I clean all the files (data files, controlfiles oder all gone).

  (1) restore spfile from pfile

  RMAN > startup nomount

  RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  (2) modify pfile to convert to db primary content. pFile shows below

  *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

  * .audit_trail = "db".

  * full = '12.1.0.2.0'

  *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

  * .db_block_size = 8192

  * .db_domain = "

  *.db_file_name_convert='/testdb/','/testdb /'

  * .db_name = "testdb".

  * .db_recovery_file_dest ='/ orafra'

  * .db_recovery_file_dest_size = 10737418240

  * .db_unique_name = "testdb".

  *.diagnostic_dest='/opt/Oracle/DB '

  * .fal_server = "stbydb".

  * .log_archive_config = 'dg_config = (testdb, stbydb)'

  * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

  * .log_archive_dest_state_2 = 'ENABLE '.

  *.log_file_name_convert='/testdb/','/testdb /'

  * .memory_target = 1800 m

  * .open_cursors = 300

  * runoff = 300

  * .remote_login_passwordfile = "EXCLUSIVE."

  * .standby_file_management = "AUTO".

  * .undo_tablespace = "UNDOTBS1.

  (3) restart db with updated file pfile

  SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

  SQLPLUS > the judgment

  SQLPLUS > startup nomount

  (4) restore controlfile

  RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  RMAN > change the editing of the database

  (5) all elements of backup catalog

  RMAN > catalog starts by ' / home/oracle/backupset / '.

  (6) restore and recover the database

  RMAN > restore database;

  RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

  (7) open resetlogs

  RMAN > alter database open resetlogs;

  Everything seems perfect, except one of the file log roll forward pending is not generated

  SQL > select * from v$ standby_log;

  ERROR:

  ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

  ORA-27037: unable to get file status

  Linux-x86_64 error: 2: no such file or directory

  Additional information: 3

  no selected line

  I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

  So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

  And I got the same missing log file.

  The problem is:

  (1) complete alert.log filled with this error, not the concern here

  (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

  (3) I can't delete and re-create this log file

  Then I tried several and found:

  The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

  For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 19 ACTIVE 133632

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  So until I take the backup, I tried on the primary database:

  SQL > alter system set log_archive_dest_state_2 = delay;

  This was the Group of standby_log side Eve #4 was released:

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 0 0 UNASSIGNED

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  Then, the backup has been restored correctly without missing standby logfile.

  However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

  Finally, my real questions come:

  (1) what I do may not do on parameter change?

  (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

  I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

  And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

  I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

  Your idea is very much appreciated.

  Thank you!

  Hello

  1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

  2nd--> when we opened the ORL database should be deleted and created

  3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

  DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

  THREAD # SEQUENCE # GROUP # STATUS

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

  1 233 4 ACTIVE

  1 238 5 ACTIVE

  DR sys@cdb01 SQL > select * from v$ logfile;

  GROUP # STATUS TYPE MEMBER IS_ CON_ID

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

  3 /u03/cdb01/cdb01/redo03.log no. 0 online

  /U03/cdb01/cdb01/redo02.log no. 0 2 online

  1 /u03/cdb01/cdb01/redo01.log no. 0 online

  4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

  /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

  DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

  DR sys@cdb01 SQL > alter database force claire logfile 4;

  change the database group claire logfile 4

  *

  ERROR on line 1:

  ORA-01156: recovery or current flashback may need access to files

  DR sys@cdb01 SQL > alter database recover managed standby database cancel;

  Database altered.

  DR sys@cdb01 SQL > change the database group claire logfile 4;

  Database altered.

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

  DR sys@cdb01 SQL >

  If you do, you can recreate the controlfile without waiting for redo log entry...

  If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

  Thank you

• Standby database is down and redo logs is not transmitted

  Hi all
  
  I have a question about the primary recovery database logs transmition for the standby database.
  What happens if the transmition of redo logs was arrested for a period of time (1 month), if I want to re - build the database ensures what measures must be applied?
  The papers of recovery will be put on hold? and once the database pending is redo these logs will be sent again? or I have to rebuild my database Eve from scratch?
  
  Kind regards

  Hello;

  When I rebooted the month so I would change the parameter 'log_archive_dest_state_n' on the primary to postpone next it would stay like that.

  I would like to delete the database in waiting, and if the folder structure was not the same I correct it.

  When the month has increased I would use RMAN to duplicate a new sleep mode:

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

  And then I put "log_archive_dest_state_n" to Activate.

  Best regards

  mseberg

• One group of standby Redo Log is ACTIVE

  Hi guys,.

  I have successfully configured a custodian of data between a primary database (oradb) and a database ensures Physics (oradb_s8).

  However, I have noticed that in V$ STANDBY_LOG only one group of standby Redo Log is ACTIVE, regardless of how many times I go log in the primary database.

  ' The following was stated in the documentation:

  When a switch of newspaper occurs on the database of the source again, redo incoming is then written to the next group of waiting for redo log, and the group used newspaper before again Eve is archived by a foreground ARCn process.

  Source.

  So, I guess that group of standby Redo Log is turned on when the Redo Log is enabled in the primary database.

  Could you please clarify it for me?

  It's the Oracle 11 g R2 (11.2.0.1) on Red Hat Server 5.2.

  On autonomy in standby:

  SQL > SELECT GROUP #, THREAD #, SEQUENCE #, ARCHIVED, STATUS FROM V$ STANDBY_LOG

  GROUP # THREAD # SEQUENCE # ARC STATUS

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

  4 1 248 YES ACTIVE <-this is the only group that is still ACTIVE

  5 1 0 NOT ASSIGNED NO.

  6 0 YES 0 UNASSIGNED

  7 0 YES 0 UNASSIGNED

  SQL > SELECT SEQUENCE #, APPLIED, FIRST_TIME NEXT_TIME

  V $ ARCHIVED_LOG

  SEQUENCE ORDER #;

  SEQUENCE # FIRST_TIM NEXT_TIME APPLIED

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

  232 06-06-SEPT.-15-15-SEP YES

  233 06-06-SEPT.-15-15-SEP YES

  234 06-06-SEPT.-15-15-SEP YES

  235 06-06-SEPT.-15-15-SEP YES

  236 06-06-SEPT.-15-15-SEP YES

  237 06-06-SEPT.-15-15-SEP YES

  238 06-06-SEPT.-15-15-SEP YES

  239 07-06-SEPT.-15-15-SEP YES

  240 YES 15-SEP-07 07-SEVEN.-15

  241 YES 15-SEP-07 07-SEVEN.-15

  242 YES 15-SEP-07 07-SEVEN.-15

  YES 243 15-SEP-07 07-SEVEN.-15

  244 YES 15-SEP-07 07-SEVEN.-15

  245 YES 15-SEP-07 07-SEVEN.-15

  246 YES 15-SEP-08 15-SEP-07

  247 15 - SEP - 08 IN-MEMORY 15-SEP-08

  16 selected lines.

  On the primary:

  SQL > SELECT SEQUENCE #, APPLIED, FIRST_TIME NEXT_TIME

  V $ ARCHIVED_LOG

  WHERE NAME = 'ORADB_S8 '.

  SEQUENCE ORDER #;

  SEQUENCE # FIRST_TIM NEXT_TIME APPLIED

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

  232 06-06-SEPT.-15-15-SEP YES

  233 06-06-SEPT.-15-15-SEP YES

  234 06-06-SEPT.-15-15-SEP YES

  235 06-06-SEPT.-15-15-SEP YES

  236 06-06-SEPT.-15-15-SEP YES

  237 06-06-SEPT.-15-15-SEP YES

  238 06-06-SEPT.-15-15-SEP YES

  239 07-06-SEPT.-15-15-SEP YES

  240 YES 15-SEP-07 07-SEVEN.-15

  241 YES 15-SEP-07 07-SEVEN.-15

  YES 07-SEP-15 242 07-SEP-15

  YES 243 15-SEP-07 07-SEVEN.-15

  244 YES 15-SEP-07 07-SEVEN.-15

  245 YES 15-SEP-07 07-SEVEN.-15

  246 YES 15-SEP-08 15-SEP-07

  247 NO. 15-SEP-08 08 - SEPT.-15

  If you have a large DML activity on primary, you see more than one group # in v$ active standby_log.

  RFS will always try to assign the next available standby log, because your group changes # 4 are already applied, it allocates this group again after the switch.

  Check metalink doc: bug 2722195 and 219344.1