Configurable Properties

Configurable properties control the behavior of broker configuration members.

You can view and dynamically update the values of these properties using either DGMGRL or Cloud Control. However, some properties can only be updated through DGMGRL.

These properties control certain database initialization parameters and SQL statements that the broker uses to manage an Oracle Data Guard broker configuration. Therefore, you should not manually set those initialization parameters or issue those SQL statements on a broker configuration.

In most cases, the configurable property is said to apply to the entire member, meaning the value you set for the property applies to each instance of the member (that is, database or far sync instance). However, in a few cases, the configurable property is said to have instance-specific scope which means that for a multiple-instance database or far sync instance, it is possible that the values of some particular properties may differ between instances. The following table lists each configurable property and indicates whether the scope of the property is member-wide or instance-specific. If the Scope column contains:

Member—The value of the property is database or far sync instance-wide, not instance or configuration specific.
Instance—The value of the property is instance specific.

If there is an asterisk (*) present, it indicates that the property value can be set for all instances of an Oracle RAC database using the EDIT INSTANCE * ON DATABASE command.
Configuration—The value of the property is configuration wide, not instance or member specific.

Table 12-1 Configurable Properties

Configurable Property Name	Scope	Pertains To
AlternateLocation	Member	Redo transport services
ApplyInstances	Member	Redo Apply
ApplyInstanceTimeout	Member	Redo Apply and SQL Apply
ArchiveLocation	Member	Redo transport services
ApplyParallel	Member	Redo Apply
Binding	Member	Redo transport services
DelayMins	Member	Redo Apply and SQL Apply
DGConnectIdentifier	Member	Broker communication, Redo transport services
Encryption	Member	Redo transport services
FastStartFailoverTarget	Member	Fast-start failover
LogShipping	Member	Redo transport services
LogXptMode	Member	Redo transport services
MaxFailure	Member	Redo transport services
NetTimeout	Member	Redo transport services
ObserverConnectIdentifier	Member	Fast-start failover
PreferredApplyInstance	Member	Redo Apply and SQL Apply
PreferredObserverHosts	Member	Fast-start failover
RedoCompression	Member	Redo transport services
RedoRoutes	Member	Redo transport services
ReopenSecs	Member	Redo transport services
StandbyAlternateLocation	Member	Redo transport services
StandbyArchiveLocation	Member	Redo transport services
StaticConnectIdentifier	Instance	Instance Startup and Shutdown
TransportDisconnectedThreshold	Member	Redo transport services
TransportLagThreshold	Member	Redo transport services

Note:

Starting with Oracle Database Release 19c, configurable properties that map directly to database initialization parameters and logical standby attributes are not maintained within the broker configuration file. See the "Deprecated Features" section in Changes in Oracle Database Release 21c for Oracle Data Guard Broker for a list of deprecated initialization parameters and logical standby attributes.

Note:

When a broker configuration with its primary database is created and members are added to the configuration, the broker imports existing settings from the members to set many of the properties. If importing an existing setting fails, or if a property value is not imported, then the broker uses a broker default value. The default values and whether or not a property is imported is indicated within each property description.