Re: DataGuard: verify recovery progress

From: Carel-Jan Engel <cjpengel.dbalert_at_xs4all.nl>
Date: Thu, 08 Jul 2004 00:46:50 +0200
Message-Id: <6.0.1.1.0.20040708003830.4427f5f0@pop.xs4all.nl>

Hi Ivan
I've seen this behaviour of Data Guard before. When you perform both queries right after a log switch, you'll see dat the archived log view shows 'NO' to applied for a while, until the standby completes the recovery from the archived logfile. The archived_log_dest view doesn't get updated at that moment, appearently it is only updated at log-switch time. Because of this I always use the archived_log view for monitoring DG configurations.

I think you have a good point with your question. Documentation doesn't make a difference between both views. I think it is a bug, at least a documentation bug.

Regards, Carel-Jan

===
If you think education is expensive, try ignorance. (Derek Bok) ===

At 05:12 PM 7/7/2004 -0400, you wrote:
>Hi,
>I tried to verify if archived logs get applied correctly to my standby
>database via v$archived_log and v$archive_dest_status but they both returned
>different results.
>
>if v$archived_log.applied=YES for sequence#881, I would expect that
>v$archive_dest_status.applied_seq#=881 too, isn't it? Instead it reports
>that the max
>sequence that has been applied is 880. Am I making the right comparision?
>Which view should I rely on?
>
>DB: 9.2.0.4
>
>thanks.
>
>Ivan

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Wed Jul 07 2004 - 17:36:56 CDT