Skip Headers
Oracle® Data Guard Broker
12c Release 1 (12.1)

E17641-14
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

Changes in This Release for Oracle Data Guard Broker

This preface lists changes in Oracle Data Guard Broker.

Changes in Oracle Database 12c Release 1 (12.1)

The following are changes in Oracle Data Guard Broker for Oracle Database 12c Release 1 (12.1).

New Features

The following features are new in this release:

  • Oracle Data Guard broker supports multitenant container databases (CDBs) within a broker configuration.

    See "Oracle Data Guard Broker and CDBs".

  • 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.

    See "EDIT CONFIGURATION (RENAME)".

  • 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".

  • You can now call the DBMS_DG PL/SQL procedure from a fast-start failover target standby database.

    See "Directing a Fast-Start Failover From an Application".

  • 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.

  • Application Continuity is supported for Oracle Data Guard and Oracle Active 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."

Deprecated Features

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

Desupported Features

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.

Other Changes

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.