Re: Applying logs to standby in 11g
- From: Saibabu Devabhaktuni <saibabu_d@xxxxxxxxx>
- To: free <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 23 Oct 2012 17:08:09 -0700 (PDT)
For determining the dataguard standbylag, relying on current_scn from
v$database is far more consistent and accurate than v$dataguard_stats.
You can use v$dataguard_stats for breakdown of transport lag versus apply lag
if the standby is falling behind.
Here is the query to get real time apply lag:
select
abs(nvl(max(ceil(
(extract(day from replication_lag)*24*60*60)+
(extract(hour from replication_lag)*60*60)+
(extract(minute from replication_lag)*60)+
(extract(second from replication_lag))
)),0)) lag_in_seconds from
(select sysdate-scn_to_timestamp(current_scn) replication_lag from v$database);
Thanks,
Sai
http://sai-oracle.blogspot.com
Re: Applying logs to standby in 11g
* From: Sandra Becker <sbecker6925@xxxxxxxxx>
* To: David Fitzjarrell <oratune@xxxxxxxxx>
* Date: Mon, 22 Oct 2012 13:17:09 -0600
Yeah, it would have helped if I had put the version in the email. I
upgraded to 11.2.0.2. When I look at the Data Guard Performance page in EM
it shows transport lag as 0.0 and apply lag of 1.0. That's pretty good so
at this point I'm going to call it "changes in 11g" and move on.
Thanks for the responses. Sandy
--
//www.freelists.org/webpage/oracle-l
Other related posts:
