RE: ORACLE 10GR2 dataguard "real-time apply" mode setup?

What level of a protection are you using?

 

If you're sending archive logs, that seems to be Max Performance and
using the archive log writer. So, in that case, unless you happen to
query the DB at the exact instance a log is being applied, you will
always be in the "waiting for log" state, since it is waiting for a log
from the primary.

 

 

 

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of dba1 mcc
Sent: Monday, April 05, 2010 10:42 AM
To: TESTAJ3@xxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: ORACLE 10GR2 dataguard "real-time apply" mode setup?

 

yes.  3 primary redo logs and 3 standby redo logs.


--- On Mon, 4/5/10, TESTAJ3@xxxxxxxxxxxxxx <TESTAJ3@xxxxxxxxxxxxxx>
wrote:


From: TESTAJ3@xxxxxxxxxxxxxx <TESTAJ3@xxxxxxxxxxxxxx>
Subject: Re: ORACLE 10GR2 dataguard "real-time apply" mode setup?
To: mccdba1@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Date: Monday, April 5, 2010, 11:38 AM


real time apply is using LGWR of course and NOT archive logs. 

Do you have standby logs built on the primary and standby? 

joe 

_______________________________________
Joe Testa, Oracle Certified Professional 
Senior Engineering & Administration Lead
(Work) 614-677-1668
(Cell) 614-312-6715






From: 

dba1 mcc <mccdba1@xxxxxxxxx> 

To: 

oracle-l@xxxxxxxxxxxxx 

Date: 

04/05/2010 11:36 AM 

Subject: 

ORACLE 10GR2 dataguard "real-time apply" mode setup? 

Sent by: 

oracle-l-bounce@xxxxxxxxxxxxx

 

________________________________




I am doing ORACLE 10GR2 (10.2.0.4 X86_64) dataguard testing on Redhat
5.4.

The dataguard currently can transfer log files to standby DB.  The
problem I have now is 'real-time apply" still NOT successful.  I change 
init.ora setup on Primary/Standbt DB to:

log_archive_dest_2='SERVICE=SPROSTY lgwr async
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DBprim'

and I also using:

SQL> alter database recover managed standby database using current
logfile disconnect.

SQL> select process, status from v$managed_standby;
PROCESS   STATUS
--------- ------------
ARCH      CLOSING
ARCH      CONNECTED
RFS       IDLE
RFS       IDLE
MRP0      WAIT_FOR_LOG     <===

It still show "wait_for_log".  Any ideal?

Thanks.





     
--
http://www.freelists.org/webpage/oracle-l
<http://www.freelists.org/webpage/oracle-l>

Other related posts: