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

MOSC Banner

My archive logs being written to $ORACLE_HOME/dbs on standby database after configuring DG broker in

edited Oct 31, 2016 12:40PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 commentsAnswered

archive logs being written to $ORACLE_HOME/dbs on standby database after configuring DG broker in 12C even though log_archive_dest_n is set. what am i missing?

Primary

-----------


*.log_archive_dest_1='LOCATION=/draper/oracle valid_for=(ONLINE_LOGFILE,ALL_ROLES) DB_UNIQUE_NAME=fabz REOPEN=30 MAX_FAILURE=3 ALTERNATE=LOG_ARCHIVE_DEST_4'

*.log_archive_dest_2='service=fabz SYNC AFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name=fabz net_timeout=30 valid_for=(online_logfile,all_roles)'

*.log_archive_dest_3='LOCATION=/draper/oracle valid_for=(STANDBY_LOGFILE,STANDBY_ROLE) DB_UNIQUE_NAME=fabz REOPEN=30 MAX_FAILURE=3 ALTERNATE=LOG_ARCHIVE_DEST_5'

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