Re: DataGuard: verify recovery progress
- From: Carel-Jan Engel <cjpengel.dbalert@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Wed, 14 Jul 2004 12:01:50 +0200
Apologies, I mixed up V$ARCHIVED_LOG and V$ARCHIVE_DEST_STATUS. I shouldn't
work that late.
V$ARCHIVE_DEST_STATUS is the untrusted source, V$ARCHIED_LOG contains the
actual 'APPLIED' status of the standby.
TAR is still open, TBC.
Regards, Carel-Jan
===
If you think education is expensive, try ignorance. (Derek Bok)
===
At 01:28 AM 7/14/2004, I wrote:
>The DG-configuration of one of my customers showed the same behaviour. I've
>opened a TAR.
>Oracle Support states that the delayed update of V$ARCHIVED_LOG is
>expected/documented behaviour. They base this on the fact that in the
>comments of the diagnostics script for primary databases (metalink note
>Note 241374.1) the delayed update is described. So, as soon as something is
>written down in the maze of metalink, it is considered as documented. Quite
>unsatisfactory. Despite the fact that a column with the name 'APPLIED"
>keeps the value 'NO' until the next log_switch, and the fact that the
>correct information is available, regarding V$ARCHIVE_DEST_STATUS, it is
>not a bug. (says support).
>
>So, stick to V$ARCHIVE_DEST_STATUS as trusted source of information.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
