High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Question on LGWR writing to standby redologs in the Primary instance.

edited Jan 17, 2013 7:39AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered
Hello Experts,

  As I was going through the alertlog of our primary database(we have a mixed dataguard setup with FSFO configured) I observed that the LGWR in the primary database is writing to Standby redologs which I suspect it has to be writing to redo log files and standby redo logs in the standby environments. The log_archive_dest parameters as in the primary database are as below

   log_archive_dest_2       = "service=xxxxxxFO LGWR SYNC AFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name=xxxxxxxFO register net_timeout=180  valid_for=(online_logfile,primary_role)"
  log_archive_dest_3       = "SERVICE=xxxxxxRO LGWR SYNC AFFIRM REOPEN=300 valid_for=(online_logfiles,primary_role) db_unique_name=xxxxxxRO"

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center