Database recover time

Similar Questions

• recover database until time - do not recover as expected

  Hello
  
  We have an Oracle 9i db (9208) running on AIX.
  
  We had a problem and allowed to restore all dbf files and control of the backup of the night on the server by replacing the currently damaged system.
  
  Once this is done, we opened then the DB in order to check some things.
  
  Once done we then closed and mounted and issued the «recover database until time...» "command.
  
  Logs archiving we need are in the location default archive. They cover the period just before the files restored until the moment that we need the DB found.
  
  However, when you run the recover log alerts just shows
  
  «ALTER DATABASE RECOVER database until time ' 2010-08 - 11:16:30:00'»»
  Mon Aug 16 14:33:57 2010
  Start of recovery Media
  Recovery media not required.
  
  Can someone tell us why the recover command is not the files of newspapers in the Archives until we are specifying. It doesn't look like its even looking at them.
  
  The command runs in less than a second.
  
  Is it because we opened the DB between the restoration and the recovery so his already written a journal of latest checking in the file, so the PB think its already up to date?

  Since you opened the database and media recovery finished, he will get no more. Is why he mentions "Media Recovery is not necessary. If you want to start the recovery media up to the hour, and then start a new restoration and then recover.

  Concerning

• Database ALTER DATABASE RECOVER using backup controlfile with AUTO option

  Hello. I was recovering a database today and had a little blip.

  I have published the following:

  Database ALTER DATABASE RECOVER using backup controlfile

  I then chose the AUTO option, allowing Oracle to select all available log files so that it would recover to the last log found in the destination of archive

  However... has performed the following:

  ORA-00289: suggestion:
  /U03/Oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf
  ORA-00280: change 30031145558 thread 1 is in sequence #242449
  ORA-00278: log file
  ' / u03/oracle/stk2proddata/archived_logs/arch1_242448_737547185.dbf' is no longer
  necessary for this recovery

  
  ORA-00308: cannot open archived log
  ' / u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf'
  ORA-27037: unable to get file status
  Linux-x86_64 error: 2: no such file or directory
  Additional information: 3

  Two messages above that I expected. However, I made then this:

  SQL > alter database open resetlogs;

  ALTER database open resetlogs

  *

  ERROR on line 1:

  ORA-01113: file 1 needs media recovery

  ORA-01110: data file 1: ' / u02/oracle/stk2proddata/system01.dbf'

  This is not what I expected. What I've done wrong? Should I once received the message "cannot open archived log", launched to CANCEL?

  I then recovered again, but used

  SQL > restore database using backup controlfile until cancel;

  ORA-00279: change 30031145558 generated at 30/04/2014 09:58:34 needed to
  thread 1
  ORA-00289: suggestion:
  /U03/Oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf
  ORA-00280: change 30031145558 thread 1 is in sequence #242449

  
  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

  ORA-00279: change 30031157768 generated at 30/04/2014 10:06:07 needed to
  thread 1
  ORA-00289: suggestion:
  /U03/Oracle/stk2proddata/archived_logs/arch1_242450_737547185.dbf
  ORA-00280: change 30031157768 thread 1 is in sequence #242450
  ORA-00278: log file
  ' / u03/oracle/stk2proddata/archived_logs/arch1_242449_737547185.dbf' is no longer
  necessary for this recovery

  
  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
  Cancel
  Cancelled media recovery.
  SQL > alter database open resetlogs;

  Database altered.

  No problem then here. Could someone please explain what I did wrong the first time and the second time right? Is this a problem with the car and using CANCEL?

  Thank you!

  DA

  11.2.0.2

  RHEL 5.5

  Bug: 4178579

• issue of database creation time

  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11 g Enterprise Edition Release 11.1.0.7.0 - 64 bit Production
  PL/SQL Release 11.1.0.7.0 - Production
  CORE Production 11.1.0.7.0
  AMT for Solaris: 11.1.0.7.0 - Production Version
  NLSRTL Version 11.1.0.7.0 - Production
  
  I think this would be a specific query about the creation of db real time after refresh
  
  Select RESETLOGS_TIME, PRIOR_RESETLOGS_TIME, v status $ database_incarnation
  When status = "CURRENT";
  Also, I've seen a database in which v$ database.created < v$ database_incarnation.resetlogs_time.
  What I did for this database was that
  
  (a) update from the production
  (b) renamed the database using nest
  and I noticed the above. No idea why in this case the control file create time is less than the resetlogs_time
  
  Thank you
  MSK

  If you have restored only a control file to restore a database THAT RMAN has no reason to change the database creation time because it assumes that you just want to restore the same database on the same site or to move it to another location (but it's always the same database). Using RMAN DUPLICATE is different.

• The amendments are not expected to be replaced by "restore database; recover the database; » ?

  Hello

  I just have to experience.

  I create a test table and some inserted rows. The I took a full backup of the database more archivelog. Then I insert more than a few lines in the test table. Then the database to stop and he started in the State of EDITING.

  Then RMAN, I made the following two commands after connection to this database as target database:

  RMAN > restore database;

  RMAN > restore database;

  After the success of the recovery operation, I opened the database. Then, I questioned the test table. I expected to see only the rows that have been inserted before the last full backup, but I can see all rows that were inserted into the table of this test. I am little confused - I thought that "restore and recover" a full backup will overwrite the existing State of the database. I expect that the State of data (database) will be exactly the same as it was at the full backup.

  Now I think I got a bad concept, but could someone please clarify this?

  Best regards

  Since you did not specify a point in time recovery Oracle used the rman backup files including archivelogs and redo to roll forward to the top in its last consistent state.

  Do not know what you were doing to the database before you did the recovery, but if you were to try again but to delete all data files, file archivelog and repeat then try recover again you would only see then the first set of rows.

• Problem with backup of database recover command

  Hi all
  
  Operating system: solaris sparc 9
  
  DB version 11 GR 2
  
  Too many archives were generated on the prod instance so BCP went out of sync and unfortunately we had to remove the archives too. We went to the front in the run-up to rollforward. But now we are faced with a strange question, issuing recover standby database now we get the error below:
  

  SQL> recover standby database;
  ORA-00279: change 10505773008414 generated at  needed for thread 1
  ORA-00289: suggestion : /archive/oracle/1_1_718997430.dbf
  ORA-00280: change 10505773008414 for thread 1 is in sequence #1

  Now archive which is it ask is the first archive which has been generated in the comic book.
  
  Can anyone suggest it please how do I solve the problem? We are unable to find any docs on metalink/net support.
  
  Concerning
  KK

  Hello;

  There is a note on what can help:

  How to retrieve and open the database if necessary the archivelog collection is missing, lost or damaged? [465478.1 ID]

  Best regards

  mseberg

• The database recovered to sleep, he's still looking for the gap sequence

  I lost the archive logs in the primary and standby (deleted because of the small footprint).
  So follow the steps below.
  
  1 identified minimum database pending YVERT.
  2A took inremental primary database backup according to the SNA (nnnnn)
  3. transfer the backup file to the side sleep
  4 cataloged database backups and recover the database.
  
  But the medial recovery is looking for lack of archived newspapers. Please advice.

  Hello

  Please refer to this http://www.shivanandarao.wordpress.com/2012/03/26/roll-forward-physical-standby-database-using-rman-incremental-backup/

  It may be useful...

• Database startup time using DPL

  Before solving the problem, I ran into the other...
  
  Get a primary index speaks extraordinarily long .
  
  Configuration:
  
  * Large cache with about 12 million admissions.
  * Cache not, everything will be in memory.
  * Allocation of memory must be large enough to hold all internal nodes.
  * The cache was deliberately not closed to test the ability of BDB to recover from crashes. (kill-9 PID)
  
  Comment:
  
  * EntityStore.getPrimaryIndex () takes a long time to return. Random sampling required 2200 and 1800 seconds on this method to return.
  Help of IAN seems to not help about this.
  * EnvironmentStats shows that memory cache is used to the top and expels the executions were necessary.
  
  Stack trace:
  
  sun.nio.ch.FileDispatcher.pread0 (Native Method)
  sun.nio.ch.FileDispatcher.pread(FileDispatcher.java:31)
  sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:230)
  sun.nio.ch.IOUtil.read(IOUtil.java:206)
  sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:625)
  com.sleepycat.je.log.FileManager.readFromFileInternal(FileManager.java:1434)
  com.sleepycat.je.log.FileManager.readFromFile(FileManager.java:1386)
  com.sleepycat.je.log.FileSource.getBytes(FileSource.java:54)
  com.sleepycat.je.log.LogManager.getLogEntryFromLogSource(LogManager.java:691)
  com.sleepycat.je.log.LogManager.getLogEntry(LogManager.java:661)
  com.sleepycat.je.tree.IN.fetchTarget(IN.java:1215)
  com.sleepycat.je.dbi.CursorImpl.fetchCurrent(CursorImpl.java:2320)
  com.sleepycat.je.dbi.CursorImpl.getCurrentAlreadyLatched(CursorImpl.java:1427)
  com.sleepycat.je.dbi.CursorImpl.getNextWithKeyChangeStatus(CursorImpl.java:1573)
  com.sleepycat.je.dbi.CursorImpl.getNext(CursorImpl.java:1499)
  com.sleepycat.je.Cursor.retrieveNextAllowPhantoms(Cursor.java:2181)
  com.sleepycat.je.Cursor.retrieveNext(Cursor.java:1991)
  com.sleepycat.je.SecondaryDatabase.init(SecondaryDatabase.java:245)
  com.sleepycat.je.SecondaryDatabase.initExisting(SecondaryDatabase.java:195)
  com.sleepycat.je.Environment.setupDatabase(Environment.java:602)
  com.sleepycat.je.Environment.openSecondaryDatabase(Environment.java:509)
  com.sleepycat.compat.DbCompat.openSecondaryDatabase(DbCompat.java:326)
  com.sleepycat.persist.impl.Store.openSecondaryIndex(Store.java:698)
  com.sleepycat.persist.impl.Store.openSecondaryIndexes(Store.java:630)
  com.sleepycat.persist.impl.Store.getPrimaryIndex(Store.java:382)
  com.sleepycat.persist.EntityStore.getPrimaryIndex(EntityStore.java:257)
  ... my code initialization here...
  
  A later invocation after a clean shutdown causes the same long startup delay.
  
  Is there something that can be done to minimize this problem? After recovery, is there a way to tell BDB to "clean" so that the next call does not have the same amount of time.

  Based on the stack trace I'm 99% certain that you experience this problem:

  getPrimaryIndex is slow

  Workaround is mentioned in the thread. This problem has been fixed for the next major version and workaround will not be necessary.

  -mark

• Database startup time

  Hello

  We have a database running oracle 11.1.0.7 on Solaris 11, which takes 10 minutes start... The database is very small (a little less than 3 GB) that hosts b2b software patterns.

  
  

  Stop the database with "stop immediately" and then he started through 'start-up' and we noticed that its takes a while. We had a glance on the alert log and it doesn't show much:

  MMNL started with pid = 62 OS id = 25708

  Mon Aug 24 11:59:44 2015

  DISM started, OS id = 25721

  Mon Aug 24 12:09:03 2015

  Here is an excerpt for the complete startup out of the instance's alert log log:

  Oracle@b2bbd02:/Home/Oracle > f tail /u01/app/oracle/product/11.1.0/db_1/log/diag/rdbms/b2bd/b2bd/trace/alert_b2bd.log

  Mon Aug 24 11:58:35 2015

  Starting ORACLE instance (normal)

  LICENSE_MAX_SESSION = 0

  LICENSE_SESSIONS_WARNING = 0

  SNA system picked latch-free 3

  Mon Aug 24 11:58:47 2015

  Using the default for the LOG_ARCHIVE_DEST_10 as USE_DB_RECOVERY_FILE_DEST parameter value

  Autotune undo retention is enabled.

  IMODE = BR

  ILAT = 73

  LICENSE_MAX_USERS = 0

  SYS audit is disabled

  Mon Aug 24 11:59:15 2015

  Commissioning ORACLE RDBMS Version: 11.1.0.7.0.

  Using parameters in Server pfile /u01/app/oracle/product/11.1.0/db_1/dbs/initb2bd.ora-side

  Parameters of the system with default values:

  process = 600

  sessions = 665

  SPFile = "/ u01/app/oracle/admin/b2bd/spfileb2bd.ora".

  memory_target = 4G

  control_files = "/ oradata/b2bd/control01.ctl".

  control_files = "/ oradata/b2bd/control02.ctl".

  control_files = "/ oralog/b2bd/control03.ctl".

  DB_BLOCK_SIZE = 8192

  compatible = "11.1.0.

  db_file_multiblock_read_count = 16

  db_recovery_file_dest = ' / orabkup/flash_recovery_area.

  db_recovery_file_dest_size = 10G

  UNDO_MANAGEMENT = 'AUTO '.

  undo_tablespace = 'UNDOTBS1.

  Remote_login_passwordfile = "EXCLUSIVE."

  db_domain = "reg.gov.ab.ca."

  JOB_QUEUE_PROCESSES = 40

  PARALLEL_MAX_SERVERS = 10

  audit_file_dest = ' / u01/app/oracle/admin/b2bd/adump.

  db_name = "b2bd".

  open_cursors = 1000

  pga_aggregate_target = 256 M

  aq_tm_processes = 2

  Mon Aug 24 11:59:16 2015

  PMON started with pid = 2, OS id = 25070

  Mon Aug 24 11:59:18 2015

  VKTM started with pid = 6, OS id = 25086

  VKTM clocked in accuracy (100ms)

  Mon Aug 24 11:59:18 2015

  DIAG started with pid = 10, OS id = 25135

  Mon Aug 24 11:59:19 2015

  DBRM started with pid = 14, OS id = 25153

  Mon Aug 24 11:59:20 2015

  PSP0 started with pid = 18, OS id = 25160

  Mon Aug 24 11:59:21 2015

  DIA0 started with pid = 22, OS id = 25171

  Mon Aug 24 11:59:22 2015

  MA started with pid = 26, OS id = 25211

  Mon Aug 24 11:59:23 2015

  DBW0 started with pid = 30, OS id = 25219

  Mon Aug 24 11:59:25 2015

  DBW1 started with pid = 3, OS id = 25228

  Mon Aug 24 11:59:27 2015

  DBW2 started with pid = 4, OS id = 25261

  Mon Aug 24 11:59:28 2015

  DBW3 started with pid = 5, OS id = 25280

  Mon Aug 24 11:59:29 2015

  DBW4 started with pid = 34, OS id = 25323

  Mon Aug 24 11:59:31 2015

  DBW5 started with pid = 7, OS id = 25358

  Mon Aug 24 11:59:32 2015

  DBW6 started with pid = 8, OS id = 25387

  Mon Aug 24 11:59:33 2015

  DBW7 started with pid = 9, OS id = 25406

  Mon Aug 24 11:59:35 2015

  DBW8 started with pid = 38, OS id = 25462

  Mon Aug 24 11:59:36 2015

  DBW9 started with pid = 11, OS id = 25545

  Mon Aug 24 11:59:38 2015

  Csilla started with pid = 12, OS id = 25554

  Mon Aug 24 11:59:39 2015

  DBWb started with pid = 13, OS id = 25561

  Mon Aug 24 11:59:39 2015

  DBWc started with pid = 42, OS id = 25567

  Mon Aug 24 11:59:39 2015

  DBWd started with pid = 15, OS id = 25570

  Mon Aug 24 11:59:39 2015

  DBWe started with pid = 16, OS id = 25574

  Mon Aug 24 11:59:39 2015

  DBWf started with pid = 17, OS id = 25586

  Mon Aug 24 11:59:40 2015

  LGWR started with pid = 19, OS id = 25598

  Mon Aug 24 11:59:42 2015

  CKPT started with pid = 46, OS id = 25608

  Mon Aug 24 11:59:42 2015

  SMON started with pid = 50, OS id = 25638

  Mon Aug 24 11:59:43 2015

  RECCE has started with pid = 54, OS id = 25663

  Mon Aug 24 11:59:43 2015

  MMON started with pid = 58, OS id = 25691

  Mon Aug 24 11:59:44 2015

  MMNL started with pid = 62 OS id = 25708

  Mon Aug 24 11:59:44 2015

  DISM started, OS id = 25721

  Mon Aug 24 12:09:03 2015

  ORACLE_BASE is not set in the environment. It is recommended that

  as ORACLE_BASE be defined in the environment

  Mon Aug 24 12:09:03 2015

  ALTER DATABASE MOUNT

  The incarnation of recovery setting target 1

  Mon Aug 24 12:09:07 2015

  Mount of redo thread 1, with mount id 462930143

  Database mounted in exclusive Mode

  Disabled lost write protect

  Completed: ALTER DATABASE MOUNT

  Mon Aug 24 12:09:08 2015

  ALTER DATABASE OPEN

  LGWR: FROM PROCESS ARCH

  Mon Aug 24 12:09:08 2015

  Arc0 started with pid = 66, OS id = 11683

  Mon Aug 24 12:09:08 2015

  Arc1 started with pid = 27, OS id = 11686

  Mon Aug 24 12:09:09 2015

  ARC2 started with pid = 20, OS id = 11688

  Arc0: Started archiving

  Mon Aug 24 12:09:09 2015

  ARC3 started with pid = 21, OS id = 11690

  Arc1: Started archiving

  ARC2: Started archiving

  ARC3: Started archiving

  LGWR: FROM PROCESS ARCH COMPLETE

  Thread 1 is open to the sequence of journal 7869

  Currently Journal # 4, seq # 7869 mem # 0: /oralog/b2bd/redo01a.log

  Currently Journal # 4, seq # 7869 mem # 1: /oralog/b2bd/redo01b.log

  Opening of redo thread 1

  View MTTR is disabled, because FAST_START_MTTR_TARGET is not defined

  ARC3: become the "no FAL' ARCH

  ARC3: become the "no SRL" ARCH

  Arc0: Become the heartbeat ARCH

  Mon Aug 24 12:09:09 2015

  SMON: enabling cache recovery

  Successfully online 2 undo Tablespace.

  Check the compatibility of the header files for tablespace 11g encryption...

  Compatibility check header files 11g for tablespace encryption completed

  SMON: enabling the recovery of tx

  Database character set is AL32UTF8

  Opening with the internal resources management plan: 4 X 32 DIGITAL system

  From FBDA background process

  Mon Aug 24 12:09:11 2015

  FBDA started with pid = 31, OS id = 11711

  off replication_dependency_tracking (no replication multimaster async found)

  From QMNC background process

  Mon Aug 24 12:09:11 2015

  QMNC started with pid = 70, OS id = 11726

  Completed: ALTER DATABASE OPEN

  Mon Aug 24 12:09:14 2015

  10240 MB db_recovery_file_dest_size is 60.90% used. It is a

  user-specified limit on the amount of space that will be used by the present

  for the files related to the recovery of databases and does not reflect the amount of

  space available in the underlying file system or ASM diskgroup.

  Mon Aug 24 12:14:19 2015

  From OCMS background process

  Mon Aug 24 12:14:20 2015

  OCMS started with pid = 78, OS id = 20505

  Memory_target/memory_max_target has the value 4 GB.

  Any idea to understand what is happening please?

  Thank you

  Problems starting database with DISM. Tuning knife Consulting

• Errors of license after recovering Time machine on an external hard drive

  My internal HD failed and I'm temporarily using an external drive as my primary HD. I loaded all my data from my backup time machine external hard disk temporarily until my new mac arrives (next week). Now, I'm getting licenses 150:30 error code when I try to open Photoshop. It says restart may fix it. He has not fixed the problem. Any recommendations? I need to work on some files now and am stuck.

  Thank you!

  Yes. This is very common. Photoshop should never be moved or transferred, because the license is tied to the Mac and move breaks the license.

  The remedy is simple. Reinstall using your discs and don't forget to apply the updates. You will begin to 11.0.0.

  Gene

• Full database backup time varies after you apply the hotfix.

  Hello gurus,
  
  I applied a patch last week to my database to 10.2.0.5, initially it was 10.2.0.1.Before the patch of the database took 10 hours to finish the job of backup rman through OEM and used to seize the 590 GB of data. After the patch, that the rman job complete in 2 hours and it is only win about 220 GB without errors
  
  The total size is 590 GB but 220 used space and free is 370 gb.
  
  Magic question is why it takes 2 hours to complete and only backup 220 GB in 10.2.0.5 compare to 10.2.0.1.
  
  
  I used this query to check the size of the database.
  
  SESSION_KEY, INPUT_TYPE, STATUS,
  TO_CHAR (START_TIME, "mm/dd/yy HH24 '") start_time,
  TO_CHAR (END_TIME, "mm/dd/yy HH24 '") end_time.
  elapsed_seconds/3600 hrs
  v $ RMAN_BACKUP_JOB_DETAILS
  order by session_key;

  There are several bugs fixed in 10.2.0.5 which can realize:

  6967455 RMAN BACKUP FILE may be slow
  7119336 backup backupset RMAN does not parallelize in multiple channels
  7173341 internal cleaning RMAN can be slow

  This note MOS can provide more details:

  10.2.0.5 Patch set - list of bug fixes by problem Type [ID 1088172.1]

  Best regards

  mseberg

• Database queue time calculation.

  Hi, I use 10.2.0.4.0 oracle version.
  
  I need to find the queue time total for each day for each WAIT_CLASS and need to trace trends in the last days. I use the application below to get the details, but my results do not match with the ones I get in the AWR report. In my daily report AWR, "USER i/o" is coming in higher class waiting times, where as in my query, I get 'Application' on the highest expectation section. Total wait time is also different. Can you please help me to understand, what don't understand me in the query?
  

  SELECT  wait_class, 
       TO_CHAR (MIN (s.end_interval_time), 'DD-MON-YYYY DY HH24:MI')
           sample_end,
          SUM (WAIT_TIME + time_waited)  waittime
   FROM dba_hist_active_sess_history q, dba_hist_snapshot s
  WHERE   s.snap_id = q.snap_id
        AND s.dbid = q.dbid
        AND s.instance_number = q.instance_number
        AND s.end_interval_time >=
               TO_DATE (TRIM ('16-Oct-2012 '), 'dd-mon-yyyy hh24:mi:ss')
        AND s.begin_interval_time <=
               TO_DATE (TRIM ('18-nov-2012 '), 'dd-mon-yyyy hh24:mi:ss')
       AND wait_class in ('User I/O','System I/O','Concurrency','Commit','Other','Configuration','Network','Application','Administrative')
   GROUP BY trunc(s.end_interval_time),wait_class
  ORDER BY trunc(s.end_interval_time),waittime desc

  SELECT Trunc(end_interval_time),
         wait_class,
         SUM(time_waited)
  FROM   dba_hist_service_wait_class
         join dba_hist_snapshot USING(snap_id)
  GROUP  BY Trunc(end_interval_time),
            wait_class
  ORDER  BY Trunc(end_interval_time),
            wait_class; 
  

  Published by: JohnWatson on 7 November 2012 16:34
  Formatting.

• MS SQL database recover model for vFoglight Pro?

  Hello
  I get a question from one of our partners on the support for the different models of MS SQL recovery (Simple, full, and using newspapers).
  Are there restrictions or is this model is used by the MS SQL DB?
  
  (Table from Microsoft)
  Thank you
  Daniel

  There are no restrictions on the mode of recovery SQL but by experience, Simple recovery does not allow transaction logs to fill out and cause problems writing to the db.
  Of course, if you use the full recovery model, you could just save your db often to purge the logs.
  A SQL DBA would normally have a preference and this wouldn't be a problem.
  Again, there are no restrictions on this.
  -Larry

• recover the database to a time

  Hello
  10 g R2 on Win 2003 server. In what follows, I can recover my database using RMAN backups:

  RMAN>Run {
       allocate channel t1 type disk;
       restore database;
       recover database;
       sql "alter database open";
  }

  How can I set a time that I want to recover my database?
  For example, I have my backups of that night. My DB blocks at 11 in the morning today and I want to recover the DB as it was at 10:00. How can I indicate this time?
  
  Thanks a lot before.

  After 2500 messages you should have just searched in the internet

  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14192/flashptr006.htm

  Best regards
  Maran

• How to set up a database of Eve 'apply in real time '.

  Hi all

  11 GR 2,

  Rhel6

  How to set up real-time apply such as the transactions are updated in near real-time to the wait, even without switching to log files?

  For example, we have 1 GB size redo logs and assuming that it will take 1 day to fill these newspapers. This means that our expectation will be entitled to 1 day delay of data?

  This means we lost 1 day of a disaster at the primary data value? because the redo log was not able to move the log files?

  Thank you very much

  JC

  Hello

  Hope this helps

  Real time apply ---> all committed changes should have been applied in standby mode

  How to:

  standby mode

  SQL > alter database recover managed standby undo;

  SQL > change managed database recovery ensures assistance to disconnect log current;        --> You should have SRL and this command works up to 11g, 12 c apply by default start with real time

  At the primary level: check the recovery mode:

  SELECT DEST_ID, RECOVERY_MODE FROM V$ ARCHIVE_DEST_STATUS WHERE DEST_ID = 2;

  Read only apply with--> is called as--> ACTIVE DATA GUARD redo apply when the database is open read-only

  
  

  standby mode

  SQL > alter database recover managed standby undo;

  SQL > alter database open read-only.

  SQL > change managed database recovery ensures assistance to disconnect log current;        --> You should have SRL and this command works up to 11g, 12 c apply by default start with real time

  SQL > select name, open_mode, controlfile_type, db_unique_name from v$ database;

  Thank you