Re: Dataguard logs

Posted by ErmanArslansOracleBlog on
URL: http://erman-arslan-s-oracle-forum.114.s1.nabble.com/Dataguard-logs-tp1478p1483.html

Also, check,

1. Check for gaps in logs on standby;

On standby -> SQL>select * from v$archive_gap;

Reference: Business Continuity for Oracle Applications Release 11i, Database Releases 9i and 10g (Doc ID 216212.1)

If this query returns a row, it indicates at least one archived redo log is missing from the standby.
If you still have access to your production database, you can determine the full name of the redo logs by querying v$archived_log, using the low_sequence# and high_sequence# returned above:

SQL>select name from v$archived_log
  where thread# = <thread# from above query>
and sequence# between <low_sequence# above> and <high_sequence# above>;

Locate the missing logs and copy them to the standby server’s standby redo log destination, then register them:Check for maximum possible log

If you still have access to your production database, or if there are other standby databases available, find the maximum possible log that could be applied to the standby you will fail over to. On the available databases, issue this query:

SQL>select unique thread# as thread, max(sequence#)
  over (partition by thread#)
  as last from v$archived_log;
If you identify more missing logs, copy them to the appropriate directory and register them as described above.