V$archived noy sync in Dataguard

Question

Hi,
My question is about a doubt that I had y my Dataguard.
Few days ago I did a scn incremental restore in order to sync Primary and Standby instances, the problem is v$archived_log is not updated. Let me show you
Primary:
select max(sequence#), to_char(next_time,'DD-MON-YY:HH24:MI:SS'), applied from v$archived_log group by to_char(next_time,'DD-MON-YY:HH24:MI:SS'), applied order by 1 desc
923426 17-FEB-13:07:16:38 NO
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
915252
Standby:
select max(sequence#), to_char(next_time,'DD-MON-YY:HH24:MI:SS'), applied from v$archived_log group by to_char(next_time,'DD-MON-YY:HH24:MI:SS'), applied order by 1 desc
923426 17-FEB-13:07:16:38 YES
When I do automatic recover the gap is:
Fetching gap sequence in thread 1, gap sequence 923427-923526
My question is why I have different values on that queries?
Thanks a lot!
Edited by: 970676 on Feb 21, 2013 4:31 PM

Answer 1

Hello;
If I understand the question correctly its because of how you query v$archived_log. The max(sequence#) hurts the query because it does not allow you see the different values of DEST_ID.
Try changing the query to include DEST_ID and use WHERE sysdate > -1 ( on one of the date columns ) to see a smaller range.
clear screen
set linesize 100
column STANDBY format a20
column applied format a10
SELECT 
  name as STANDBY,
  SEQUENCE#,
  applied,
  completion_time
from
  v$archived_log
WHERE 
  DEST_ID = 2 AND NEXT_TIME > SYSDATE -1;The try this query from your Primary :
http://www.visi.com/~mseberg/data_guard/monitor_data_guard_transport.html
Best Regards
mseberg
Edited by: mseberg on Feb 21, 2013 6:49 PM