This content has been marked as final. Show 2 replies
It works better from the primary side.
try this :
If you have a gap larger than 5 or 6 I would check the alert log on the standby first. Generally you will see a message with the sequence number "Waiting for log..."
If you have an issue you may see an error message, if nothing check the primary alert log next.
spiral wrote:As MSeberg said, first visit alert log files
Platform : RHEL 5.4
Are the below queries your step1 in determining a gap at a physical standby side?
If you do find a difference in the sequence from the above query , what should be the next thing one should be looking for (for further diagnosis ) ?
-- on primary select max(sequence#) from v$archived_log; -- on Standby select max(sequence#) from v$archived_log where applied='YES';
second dynamic views
Ex:- SQL> select severity,error_code,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') from v$dataguard_status where dest_id=<>;
Mention remote destination number above, also you can check view for the current log what is writing and applying from v$managed_standby