8 Scenarios Using the DGMGRL Command-Line Interface

Use these scenarios to help you understand what you need to do to start creating, managing, and using an Oracle Data Guard broker configuration.

Read the information about prerequisites for getting started using the Oracle Data Guard command-line interface (DGMGRL), so that you can prepare your instances. Then read the scenarios to understand how you can use DGMGRL to create, manage, and monitor a broker configuration.

• Prerequisites for Getting Started

• Scenario 1: Creating a Configuration

• Scenario 2: Setting Database Properties

• Scenario 3: Enabling the Configuration and Databases

• Scenario 4: Setting the Configuration Protection Mode

• Scenario 5: Setting up Maximum Availability Mode with a Far Sync Instance

• Scenario 6: Enabling Fast-Start Failover and Starting the Observer

• Scenario 7: Enabling Fast-Start Failover When a Far Sync Instance Is In Use

• Scenario 8: Performing Routine Management Tasks

• Scenario 9: Performing a Switchover Operation

• Scenario 10: Performing a Manual Failover Operation

• Scenario 11: Reinstating a Failed Primary Database

• Scenario 12: Converting a Physical Standby to a Snapshot Standby

• Scenario 13: Monitoring a Data Guard Configuration

• Scenario 14: Adding a Recovery Appliance to a Broker Configuration

• Scenario 15: Exporting and Importing a Broker Configuration File

• Scenario 16: Using the Observe-only Mode for Fast-Start Failover

• Prerequisites for Getting Started
  One of the prerequisites for using DGMGRL is that a primary database and any standby databases must already exist.
• Scenario 1: Creating a Configuration
  These examples create a broker configuration named DRSolution that includes a primary and standby database named North_Sales and South_Sales.
• Scenario 2: Setting Database Properties
  After you create the configuration with DGMGRL, you can set database properties at any time.
• Scenario 3: Enabling the Configuration and Databases
  So far, the DRSolution configuration is disabled, which means it is not under the control of the Data Guard broker.
• Scenario 4: Setting the Configuration Protection Mode
  You can change the protection mode of the configuration at any time.
• Scenario 5: Setting up Maximum Availability Mode with a Far Sync Instance
  A far sync instance can be used with maximum availability protection mode if the primary and standby database are geographically far enough apart to make the use of synchronous transport mode impractical.
• Scenario 6: Enabling Fast-Start Failover and Starting the Observer
  You can enable fast-start failover from any site, including the observer site, while connected to any database in the broker configuration.
• Scenario 7: Enabling Fast-Start Failover When a Far Sync Instance Is In Use
  Fast-start failover can be enabled in maximum availability mode when the fast-start failover target is a logical or physical standby database that receives redo data from a far sync instance.
• Scenario 8: Performing Routine Management Tasks
  There may be situations in which you want to change the state or properties of the databases in a broker configuration to perform routine maintenance on one or more databases.
• Scenario 9: Performing a Switchover Operation
  You can switch the role of the primary database and a standby database using the SWITCHOVER command.
• Scenario 10: Performing a Manual Failover Operation
  You invoke a failover operation in response to an emergency situation, usually when the primary database cannot be accessed or is unavailable.
• Scenario 11: Reinstating a Failed Primary Database
  If your former primary database was configured with Flashback Database, you can easily reinstate the failed primary database as a standby database of the new primary database.
• Scenario 12: Converting a Physical Standby to a Snapshot Standby
  If you have a physical standby database that you would like to convert to a snapshot standby database, use the DGMGRL CONVERT DATABASE command.
• Scenario 13: Monitoring a Data Guard Configuration
  These steps demonstrate the tasks necessary to use the SHOW command and monitorable properties to identify and resolve a failure situation.
• Scenario 14: Adding a Recovery Appliance to a Broker Configuration
  These steps show how to add a Zero Data Loss Recovery Appliance (Recovery Appliance) to a broker configuration.
• Scenario 15: Exporting and Importing a Broker Configuration File
  The broker configuration can be exported into a text file in the trace directory. The configuration can be recreated by importing the exported configuration metadata.
• Scenario 16: Using the Observe-only Mode for Fast-Start Failover
  The observe-only mode enables you to test the impact of using fast-start failover in your configuration, without making any actual changes to the configuration. You can use the DGMGRL commands or data dictionary views to verify the observe-only mode setting.