Home » Server Options » Data Guard » Difficulty in detecting Archive gap on Physical Standby (Oracle 10.2.0.4 on RHEL)
Difficulty in detecting Archive gap on Physical Standby [message #573492] Sat, 29 December 2012 12:33 Go to next message
new_oradba
Messages: 1
Registered: December 2012
Junior Member
Hi

which of the following views on the physical standby will us correct information on synchronization with Pimary database?

For example, when I checked v$archived_gap it did not return any rows but the max(applied_seq#) on v$archive_dest_status was lagging far behind from the max(sequence#) on Primary database

select max(applied_seq#) from v$archive_dest_status where dest_id=2;

select max(sequence#) from v$archived_log where applied='YES';

select * from v$archive_gap;



Thanks in advance

Kind Regards
new_oradba
Re: Difficulty in detecting Archive gap on Physical Standby [message #573520 is a reply to message #573492] Sun, 30 December 2012 02:43 Go to previous message
John Watson
Messages: 4610
Registered: January 2010
Location: Global Village
Senior Member
All those views give you correct information. You need to think about what the information means. That will tell you whether your problem is with redo transport or with redo apply.
Previous Topic: Snapshot standby
Next Topic: Issue in finding logs applied on Standby database
Goto Forum:
  


Current Time: Wed Oct 01 06:11:36 CDT 2014

Total time taken to generate the page: 0.06371 seconds