[Oracle Maintenance Engineer's Notes series] Does the Data Guard broker change attributes to be executed separately on both sides?

Does the Data Guard broker change attributes to be executed separately on both sides?

Data Guard Broker has some properties that can be seen through show configuration.
I sometimes wonder if these attributes, respectively, belong to primary and standby, and if
If you want to change, do you need to log in to primary and standby separately to modify it?

This is also a question that many customers often have. So I carried out the following experiments.

First look at the property values of the primary side:

-bash-4.1$ DGMGRL/
DGMGRL for Linux:version 12.1.0.2.0-64bit Production

Copyright (c), Oracle. All rights reserved.

Welcome to DGMGRL, type ' help ' for information.
Connected as SYSDG.

Dgmgrl> Show configuration verbose;

Configuration-drsolution

Protection mode:maxperformance
Members:
Orcl12102-primary Database
Orcl12102_stby-physical Standby Database

Properties:
Faststartfailoverthreshold = ' 30 '
Operationtimeout = ' 30 '
TraceLevel = ' USER '
Faststartfailoverlaglimit = ' 30 '
Communicationtimeout = ' 180 '
Observerreconnect = ' 0 '
faststartfailoverautoreinstate = ' TRUE '
Faststartfailoverpmyshutdown = ' TRUE '
Bystandersfollowrolechange = ' All '
Observeroverride = ' FALSE '
ExternalDestination1 = ' '
ExternalDestination2 = ' '
primarylostwriteaction = ' CONTINUE '

Fast-start failover:disabled

Configuration Status:
SUCCESS

Dgmgrl>

Then look at the properties of the standby side:

-bash-4.1$ DGMGRL/
DGMGRL for Linux:version 12.1.0.2.0-64bit Production

Copyright (c), Oracle. All rights reserved.

Welcome to DGMGRL, type ' help ' for information.
Connected as SYSDG.

Dgmgrl> Show configuration verbose;

Configuration-drsolution

Protection mode:maxperformance
Members:
Orcl12102-primary Database
Orcl12102_stby-physical Standby Database

Properties:
Faststartfailoverthreshold = ' 30 '
Operationtimeout = ' 30 '
TraceLevel = ' USER '
Faststartfailoverlaglimit = ' 30 '
Communicationtimeout = ' 180 '
Observerreconnect = ' 0 '
faststartfailoverautoreinstate = ' TRUE '
Faststartfailoverpmyshutdown = ' TRUE '
Bystandersfollowrolechange = ' All '
Observeroverride = ' FALSE '
ExternalDestination1 = ' '
ExternalDestination2 = ' '
primarylostwriteaction = ' CONTINUE '

Fast-start failover:disabled

Configuration Status:
SUCCESS

Dgmgrl>

The property values that you see from both primary and standby are the same. So I have a guess that these attribute values are common.
The following is validated by modifying the value of the Communicationtimeout:

On the primary side modify:

Dgmgrl> EDIT CONFIGURATION SET property communicationtimeout=120;
Property "Communicationtimeout" updated

After the change, verify that:

Dgmgrl> Show configuration verbose;

Configuration-drsolution

Protection mode:maxperformance
Members:
Orcl12102-primary Database
Orcl12102_stby-physical Standby Database

Properties:
Faststartfailoverthreshold = ' 30 '
Operationtimeout = ' 30 '
TraceLevel = ' USER '
Faststartfailoverlaglimit = ' 30 '
Communicationtimeout = ' 120 ' ******
Observerreconnect = ' 0 '
faststartfailoverautoreinstate = ' TRUE '
Faststartfailoverpmyshutdown = ' TRUE '
Bystandersfollowrolechange = ' All '
Observeroverride = ' FALSE '
ExternalDestination1 = ' '
ExternalDestination2 = ' '
primarylostwriteaction = ' CONTINUE '

Fast-start failover:disabled

Configuration Status:
SUCCESS

Dgmgrl>

So, on the standby side, what kind of results do you see?

Dgmgrl> Show configuration verbose;

Configuration-drsolution

Protection mode:maxperformance
Members:
Orcl12102-primary Database
Orcl12102_stby-physical Standby Database

Properties:
Faststartfailoverthreshold = ' 30 '
Operationtimeout = ' 30 '
TraceLevel = ' USER '
Faststartfailoverlaglimit = ' 30 '
Communicationtimeout = ' + ' <<<<<<<<<<<<< from the standby side, this value can also be seen, it has indeed been changed.
Observerreconnect = ' 0 '
faststartfailoverautoreinstate = ' TRUE '
Faststartfailoverpmyshutdown = ' TRUE '
Bystandersfollowrolechange = ' All '
Observeroverride = ' FALSE '
ExternalDestination1 = ' '
ExternalDestination2 = ' '
primarylostwriteaction = ' CONTINUE '

Fast-start failover:disabled

Configuration Status:
SUCCESS

Dgmgrl>

In fact, it is also possible to change other property values from the standby side, and we can also connect to the data guard broker from the primary side to see the same change.

So, after the Data Guard Broker is built, if you want to change its property values, either from the primary side or from the standby side, after the login is connected to the broker,
At which end the modification is possible.

[Oracle Maintenance Engineer's Notes series] Does the Data Guard broker change attributes to be executed separately on both sides?