Re: DataGuard: verify recovery progress

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).

At 11:12 PM 7/7/2004, 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.>> From the documentation:>>v$archive_dest_status.APPLIED_SEQ#>NUMBER>Identifies the log sequence number of the most recent applied redo log>received at the destination>>>v$archived_log.APPLIED>VARCHAR2(3)>(YES|NO) Indicates whether or not the archivelog has been applied to its>corresponding standby database. YES indicates it has been applied; NO>indicates it has not. The value is always NO for local destinations>>>SQL> select name,sequence#,archived,applied from v$archived_log;>NAME SEQUENCE# ARC APP>-------------------------------------------------- ---------- --- --->...>...>...>C:\ORACLE\ADMIN\PSTUR\RARCHDEST\ARC00878.001 878 YES YES>C:\ORACLE\ADMIN\PSTUR\RARCHDEST\ARC00879.001 879 YES YES>C:\ORACLE\ADMIN\PSTUR\RARCHDEST\ARC00880.001 880 YES YES>C:\ORACLE\ADMIN\PSTUR\RARCHDEST\ARC00881.001 881 YES YES>>>>SQL> select dest_name,archived_seq#,applied_seq# from v$archive_dest_status;>>DEST_NAME ARCHIVED_SEQ# APPLIED_SEQ#>------------------------------ ------------- ------------>LOG_ARCHIVE_DEST_1 560 0>LOG_ARCHIVE_DEST_2 0 0>LOG_ARCHIVE_DEST_3 0 0>LOG_ARCHIVE_DEST_4 0 0>LOG_ARCHIVE_DEST_5 0 0>LOG_ARCHIVE_DEST_6 0 0>LOG_ARCHIVE_DEST_7 0 0>LOG_ARCHIVE_DEST_8 0 0>LOG_ARCHIVE_DEST_9 0 0>LOG_ARCHIVE_DEST_10 0 0>LOG_ARCHIVE_DEST_11 881 880>>>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>>_________________________________________________________________>Is your PC infected? Get a FREE online computer virus scan from McAfeeŽ>Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963>>---------------------------------------------------------------->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>-----------------------------------------------------------------

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.