ENABLE CONFIGURATION

The ENABLE CONFIGURATION command enables the broker to manage the broker configuration, including all of its databases.

Format

ENABLE CONFIGURATION [ <configuration_name> | ALL ];

Command Parameters

None.

Usage Notes

  • Use the ENABLE CONFIGURATION command to enable broker management of the primary database and all members of the configuration, if these members are not explicitly disabled by the user.

  • To issue this command, you must connect to a database whose control file role is primary.

  • By default, broker management of the configuration's databases is enabled in the TRANSPORT-ON state with redo transport services turned on at the primary database and APPLY-ON with log apply services started at the standby databases. Far sync instances will be enabled such that they receive redo data and send redo data. You can change the state of a database using the EDIT DATABASE (State) command, but not when the database or the entire configuration is disabled. You cannot change the state of a far sync instance.

  • Use this command to update the roles stored in the broker configuration if a failover or switchover was performed using SQL*Plus instead of DGMGRL or Cloud Control.

  • Use the SHOW CONFIGURATION command to display information about the configuration.

  • Include the ALL keyword to enable all configurations. Use this to start redo transport between the source database to the target database after you create a DB PDB configuration.

Command Example

The following example enables management of a broker configuration. 

DGMGRL> ENABLE CONFIGURATION;
Enabled.

The following command enables management of all configured broker configurations that contain one or more PDBs. It begins redo transport from the source database to the target database.

DGMGRL> ENABLE CONFIGURATION ALL;
Enabled “MyConfig1” with primary database “boston”.
Enabled “MyConfig2” with primary database “newyork”.