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

MOSC Banner

Data Guard Broker changes parameter log_archive_dest_2

edited Jun 3, 2010 3:42PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered
 Hello!

I'm facing a problem when configuring Broker; when I give command in dgmgrl: Enable configuration; it changes my spfile parameter "log_archive_dest_2" into a false connection string, and it breaks my redo shipping.

My original dest_2 on Primary side is: service=STANDBY.TEST.BE valid_for=(online_logfiles,primary_role) db_unique_name=STANDBY.

The service can be seen on Standby side, and I can also connect to the service name with sqlplus on both Primary and Standby.

Does anyone know, from where the Broker takes the value for the parameter? The value, which it gives, is the hostname (which is not used for redoshipping, we have another ip for that) and it's not on my listeners nor tnsnames.

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