4 Managing the Members of a Broker Configuration
Learn how to manage broker configuration members, and monitor the state of each member of the configuration.
- Managing Broker Configuration Members
The broker uses information in its configuration file to manage and monitor the state of each member of the configuration. - Managing States of Broker Configuration Members
The members of a configuration can be in various states which, in an enabled configuration, determine the behavior of Oracle Data Guard. - Managing Database Properties
There are two types of database properties: monitorable and configurable. - Managing Redo Transport Services
To manage redo transport services, you specify configurable properties on each configuration member. - Managing Redo Transport Services for Recovery Appliance
Redo transport services for a Zero Data Loss Recovery Appliance (Recovery Appliance) are managed in the same way as for a standby database. - Managing Log Apply Services
You can manage Redo Apply and SQL Apply on physical and logical standby databases by using database properties related to log apply. - Managing Data Protection Modes
You can use the broker to set up a configuration having any of the different data protection modes. - Managing Far Sync Instances
An Oracle Data Guard far sync instance is a redo transport destination that accepts redo from a primary database and forwards that redo to one or more redo destinations in the configuration. - Managing Fast-Start Failover
You can enable fast-start failover to allow the broker to determine if a failover is necessary and to initiate a failover to a standby database from a list of one or more pre-specified target standby databases. - Managing Database Conversions
You can use the DGMGRLCONVERT DATABASEcommand to convert a physical standby database to a snapshot standby database. - Managing Configuration and Member Tagging
Tagging enables teams to organize configuration members according to business needs. - Database Status
In general, the broker checks the health of a database by verifying that the actual database state and settings match those described in the broker configuration file.