Re: Applying logs to standby in 11g
- From: Yong Huang <yong321@xxxxxxxxx>
- To: Michael Dinh <mdinh235@xxxxxxxxx>
- Date: Sat, 27 Oct 2012 14:21:59 -0700 (PDT)
Michael,
I found a number of bugs related to delayed update of applied_seq# of
v$archive_dest_status, such as bugs 8822832, 8675089, 5678485. So it may not be
a good idea to rely on this column to check for standby lag.
Yong Huang
--- On Fri, 10/26/12, Michael Dinh <mdinh235@xxxxxxxxx> wrote:
From: Michael Dinh <mdinh235@xxxxxxxxx>
Subject: Re: Applying logs to standby in 11g
To: "Yong Huang" <yong321@xxxxxxxxx>
Cc: oracle-l@xxxxxxxxxxxxx
Date: Friday, October 26, 2012, 8:29 AM
Hello Yong,
Here is the definition for 11.2 for the 2 views
http://docs.oracle.com/cd/E11882_01/server.112/e25513/dynviews_1016.htm#REFRN30011
V$ARCHIVE_DEST_STATUS.ARCHIVED_SEQ# - Identifies the log sequence number of the
most recent applied redo log received at the destinationV$ARCHIVED_LOG.APPLIED
- Indicates whether an archived redo log file has been applied to the
corresponding physical standby database
I never understood the difference; hence, CASE WHEN archived_seq# -
applied_seq# > 10 to ignore the discrepancies. BUG???
You are correct in saying - the "GAP" column in your script may be called "LAG"
so it's different from GAP_STATUS
-Michael.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
