OraFAQ Forum: Data Guard » Difficulty in detecting Archive gap on Physical Standby

Home » Server Options » Data Guard » Difficulty in detecting Archive gap on Physical Standby (Oracle 10.2.0.4 on RHEL)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Difficulty in detecting Archive gap on Physical Standby [message #573492]

Sat, 29 December 2012 12:33

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

Code: [Select all] [Show/ hide]

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

Report message to a moderator

Re: Difficulty in detecting Archive gap on Physical Standby [message #573520 is a reply to message #573492]

Sun, 30 December 2012 02:43

John Watson
Messages: 8978
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.

Report message to a moderator

Previous Topic:	Snapshot standby
Next Topic:	Issue in finding logs applied on Standby database

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jun 15 17:28:51 CDT 2025