This preface lists changes in Oracle Data Guard Broker.
The following are changes in Oracle Data Guard Broker for Oracle Database 12c Release 1 (12.1.0.2).
The following features are new in this release:
The ExternalDestination1 and ExternalDestination2 configuration properties let you set up a redo transport destination that can receive redo data from the current primary database. See "ExternalDestination1" and "ExternalDestination2". (These properties are available in Oracle Database 12c Release 1 (12.1.0.2) and later. They are also available in Oracle Database 11g Release 2 (11.2.0.4), but not in Oracle Database 12c Release 1 (12.1.0.1).)
The new PrimaryLostWriteAction configuration property determines what action is taken if a standby database detects that a lost write has occurred at the primary database. See "PrimaryLostWriteAction". (This property is available in Oracle Database 12c Release 1 (12.1.0.2) and later. It is also available in Oracle Database 11g Release 2 (11.2.0.4), but not in Oracle Database 12c Release 1 (12.1.0.1).)
You can now use the information provided in the new V$FS_OBSERVER_HISTOGRAM view for help in determining an appropriate value for the FastStartFailoverThreshold configuration property. See "FastStartFailoverThreshold." (This view is available in Oracle Database 12c Release 1 (12.1.0.2) and later. It is also available in Oracle Database 11g Release 2 (11.2.0.4), but not in Oracle Database 12c Release 1 (12.1.0.1).)
You can now use the RedoRoutes property to specify an alternate destination to ship redo data to if the first destination fails. To see an example of how to do this, see "Advanced Redo Transport Settings."
The new SHOW CONFIGURATION WHEN PRIMARY IS command displays the redo transport configuration that would be in effect if the specified database were the primary database. See "SHOW CONFIGURATION WHEN PRIMARY IS."
The new VALIDATE FAR_SYNC command performs a comprehensive set of checks to validate a far sync instance. The optional WHEN PRIMARY clause allows you to validate a far sync instance based upon a different database being the primary database. See "VALIDATE FAR_SYNC."
As of Oracle Database 12c release 1 (12.1.0.2), Data Guard broker configurations support redo transport from the current primary database to a Zero Data Loss Recovery Appliance (Recovery Appliance) through the use of the ExternalDestination1 and ExternalDestination2 configuration properties.
Recovery Appliance is an enterprise-level backup solution that provides a single repository for backups of all of your Oracle databases.
See "ExternalDestination1" and "ExternalDestination2". (These properties are available in Oracle Database 12c Release 1 (12.1.0.2) and later. They are also available in Oracle Database 11g Release 2 (11.2.0.4), but not in Oracle Database 12c Release 1 (12.1.0.1).
The following are additional changes in the release:
An Oracle Data Guard broker configuration can now contain up to 253 members, including one primary database and a combination of standby databases and far sync instances that receive redo directly from the primary database.
You now need to define and register a static service only if Oracle Clusterware or Oracle Restart is not being used.
Application Continuity is supported for Oracle Data Guard switchovers to physical standby databases. It is also supported for fast-start failover to physical standbys in maximum availability data protection mode. Note that primary and standby databases must be licensed for Oracle RAC or Oracle Active Data Guard in order to use Application Continuity. See "Application Continuity."
The following properties are no longer available:
LsbyASkipCfgPr
LsbyASkipErrorCfgPr
LsbyAskipTxnCfgPr
LsbyDskipCfgPr
LsbyDSkipErrorCfgPr
LsbyDSkipTxnCfgPr
LsbySkipTable
LsbySkipTxnTable
The following are changes in Oracle Data Guard Broker for Oracle Database 12c Release 1 (12.1.0.1).
The following features are new in this release:
Oracle Data Guard broker supports multitenant container databases (CDBs) within a broker configuration.
Support for the new Oracle Data Guard SYSDG administrative privilege when using DGMGRL to connect to a database.
See "CONNECT".
A new DGMGRL command, VALIDATE DATABASE, enables you to quickly and easily determine whether a database is ready to perform a role change.
See "VALIDATE DATABASE".
New DGMGRL commands enable you to add far sync instances to an Oracle Data Guard configuration and to manage them.
See Chapter 7 for information on commands related to management of far sync instances in a broker configuration.
A new configurable property, RedoRoutes, supports redo cascading and far sync instances.
See "RedoRoutes".
You can use the new EDIT CONFIGURATION (RENAME) command to change the name of an Oracle Data Guard broker configuration. You no longer have to remove and re-create the configuration using a different name.
You can now easily reset an Oracle Data Guard broker property back to its default value. You can do this at the configuration, database, or instance level.
See "Resetting Broker Configurable Properties to Default Values".
A new high performance redo transport mode, FASTSYNC, supports the maximum availability data protection modes.
See "LogXptMode" for information about setting redo transport modes.
An Oracle Data Guard broker configuration can be preserved during a rolling upgrade so that it does not have to be rebuilt after the upgrade is complete.
See "Preserving Broker Configurations During Rolling Upgrades".
You can now execute a SQL statement or a PL/SQL stored procedure from the Data Guard command-line interface (DGMGRL) so that you do not have to exit and restart command line interfaces multiple times for routine tasks.
See "SQL".
Oracle Data Guard broker supports the new Oracle Global Data Services (GDS) feature of Oracle Database 12c Release 1 (12.1).
See "Oracle Data Guard Broker and Oracle Global Data Services".
See Also:
Oracle Database Global Data Services Concepts and Administration Guide for more information about GDS.
You can now call the DBMS_DG PL/SQL procedure from a fast-start failover target standby database.
You can now resume a switchover after a failure.
See "Troubleshooting Problems During a Switchover Operation".
You can now control the amount of tracing performed by the broker for every database in the configuration.
See the "TraceLevel" configuration property.
The new ObserverReconnect configuration property allows you to specify an interval at which the observer disconnects and reconnects to the primary and standby database.
See the "ObserverReconnect" property.
The new ObserverOverride configuration property allows you to specify whether the observer should initiate an automatic failover when it loses connectivity to the primary, even if the standby has a healthy connection to the primary.
See the "ObserverOverride" configuration property.
The new ApplyLagThreshold configurable property allows you to set a maximum value for the apply lag on physical and logical standbys. A warning is issued if the limit is exceeded.
See the "ApplyLagThreshold" property.
The new TransportDisconnectedThreshold configurable property allows you to set a limit on the amount of time that can elapse without communication from the primary. A warning is issued if the limit is exceeded.
See the "TransportDisconnectedThreshold" property.
The TransportLagThreshold configurable property allows you to set a limit for a database's transport lag. A warning is issued if the limit is exceeded.
See the "TransportLagThreshold" property.
The following features are deprecated in this release, and may be desupported in a future release:
The following configurable properties have been deprecated:
LsbyASkipCfgPr
LsbyASkipErrorCfgPr
LsbyAskipTxnCfgPr
LsbyDskipCfgPr
LsbyDSkipErrorCfgPr
LsbyDSkipTxnCfgPr
The following monitorable properties have been deprecated:
LsbySkipTable
LsbySkipTxnTable
Oracle Restart is deprecated. Oracle Restart is a feature provided as part of Oracle Grid infrastructure. It is currently restricted to managing single instance Oracle databases and Oracle ASM instances only, and is subject to desupport in future releases. For more information, see the My Oracle Support note 1584742.1 at http://support.oracle.com.
Some features previously described in this document are desupported in Oracle Database 12c Release 1 (12.1). See Oracle Database Upgrade Guide for a list of desupported features.
The following are additional changes in the release:
You cannot create a broker configuration if the primary database for that configuration has any remote redo transport destinations, unless those remote redo transport destinations have the NOREGISTER attribute.
If the primary database has any remote redo transport destinations that do not have the NOREGISTER attribute, then you must clear them before proceeding. You can then configure remote redo transport destinations after a broker configuration has been created.