Data Guard Broker

and Enterprise Manager

Copyright © 2005, Oracle. All rights reserved.

 Objectives

After completing this lesson, you should be able to do

the following:
Describe the Data Guard broker architecture
Describe the Data Guard broker components
Explain the benefits of the Data Guard broker
Explain Data Guard broker configurations
Use Enterprise Manager to manage your Data
Guard configuration
Invoke DGMGRL to manage your Data Guard
configuration

3-2 Copyright © 2005, Oracle. All rights reserved.

Oracle Database 10g: Data Guard Administration 3-2

 Features of Data Guard Broker

The Data Guard broker is a distributed

management framework.
The broker automates and centralizes the creation,
maintenance, and monitoring of Data Guard
configurations.
With the broker, you can perform all management
operations locally or remotely through easy-to-use
interfaces:
Oracle Enterprise Manager 10g Grid Control
A command-line interface: DGMGRL

3-3 Copyright © 2005, Oracle. All rights reserved.

Features of Data Guard Broker

The Oracle Data Guard broker is a distributed management framework that automates and
centralizes the creation, maintenance, and monitoring of Data Guard configurations. The
following are some of the operations that the broker automates and simplifies:
Automated creation of Data Guard configurations incorporating a primary database, a new
or existing (physical or logical) standby database, log transport services, and log apply
services
Note: Any of the databases might be RAC databases.
Adding up to eight additional new or existing (physical or logical, RAC or non-RAC)
standby databases to each existing Data Guard configuration, for a total of one primary
database, and from one to nine standby databases in the same configuration
Managing an entire Data Guard configuration (including all databases, log transport
services, and log apply services) through a client connection to any database in the
configuration
Invoking switchover or failover with a single command to initiate and control complex role
changes across all databases in the configuration
Monitoring the status of the entire configuration, capturing diagnostic information,
reporting statistics such as the log apply rate and the redo generation rate, and detecting
problems quickly with centralized monitoring, testing, and performance tools

Oracle Database 10g: Data Guard Administration 3-3

 Data Guard Broker: Components

Client-side:
Oracle Enterprise Manager 10g Grid Control
DGMGRL (command-line interface)
Server-side: Data Guard monitor
DMON process
Configuration files

3-4 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker: Components

The Oracle Data Guard broker consists of components that reside on the client and the server in
the configuration.
On the client, you can use the following Data Guard components to define and manage a
configuration:
Oracle Enterprise Manager
DGMGRL, which is the Data Guard command-line interface (CLI)
On the server, Data Guard monitor is a broker component that is integrated with the Oracle
database. Data Guard monitor comprises the Data Guard monitor process (DMON) and broker
configuration files, with which you can control the databases of that configuration, modify their
behavior at run time, monitor the overall health of the configuration, and provide notification of
other operational characteristics.
The configuration file contains profiles that describe the states and properties of the databases in
the configuration. Associated with each database are various properties that the DMON process
uses to control the database s behavior. The properties are recorded in the configuration file as a
part of the database s object profile that is stored there. Many database properties are used to
control database initialization parameters related to the Data Guard environment.

Oracle Database 10g: Data Guard Administration 3-4

 Data Guard Broker: Configurations

The most common configuration is a primary database

at one location and a standby database at another
location.

Chicago Boston

Oracle Net

Primary Standby
site site

3-5 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker: Configurations

A Data Guard configuration consists of one primary database and up to nine standby databases.
The databases in a Data Guard configuration are typically dispersed geographically and are
connected by Oracle Net.
A Data Guard broker configuration is a logical grouping of the primary and standby databases in
a Data Guard configuration. The broker s DMON process configures and maintains the broker
configuration components as a unified group of resource objects that you can manage and
monitor as a single unit. When you enter a command through Enterprise Manager or the CLI, the
appropriate DMON process does the following:
Carries out your request on its local database resource object and site object
Updates the broker configuration file
Communicates with the DMON process on the other site

Oracle Database 10g: Data Guard Administration 3-5

 Data Guard Broker: Management Model

Data Guard Broker Configuration

Standby database
Broker-controlled Standby database
databases Standby database
Standby database
Standby database
Standby database
Standby database
Primary database Standby database
Standby database

Instances
Instances

3-6 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker: Management Model

The Data Guard broker performs operations on logical objects:
Configuration of databases
A single database
A broker configuration consists of:
A configuration object: A named collection of database profiles. A database profile is a
description of a database object, including its current state, current status, and properties.
Database objects: Objects corresponding to primary or standby databases
Instance objects: A database object may be comprised of one or more instance objects if it
is a RAC database.
The broker supports one or more Data Guard configurations, each of which includes a profile for
one primary database as well as profiles for up to nine physical, logical, RAC or non-RAC
standby databases.

Oracle Database 10g: Data Guard Administration 3-6

 Data Guard Broker: Architecture
Graphical user interface
or
command-line interface
Data Guard Configuration
Standby site 9
Standby site 2
Primary site Standby site 1
Configuration Configuration
files files Standby
Archived database
redo logs
Primary Log
database apply
Standby services
Online DMON DMON
redo logs
redo logs Archived
redo logs
Log Oracle
transport Net
services

3-7 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker: Architecture

The Data Guard broker helps you create, control, and monitor a Data Guard configuration. This
configuration consists of a primary database that is protected by one or more standby databases.
After the broker has created the Data Guard configuration, the broker monitors the activity,
health, and availability of all systems in the Data Guard configuration.
The Data Guard monitor process (DMON) is an Oracle background process that runs on every site
that is managed by the broker. When you start the Data Guard broker, a DMON process is created.
When you use Enterprise Manager or the Data Guard command-line interface (CLI), the DMON
process is the server-side component that interacts with the local instance and the DMON
processes that are running on other sites to perform the requested function. The DMON process is
also responsible for monitoring the health of the broker configuration and for ensuring that every
site has a consistent copy of the configuration files in which the DMON process stores its
configuration data. There are two multiplexed versions of the configuration file on each site.

Oracle Database 10g: Data Guard Administration 3-7

 Life Cycle of a Broker Configuration

Create
configuration

Enable
configuration

Make state or Update database

role changes properties

Monitor and tune

configuration

3-8 Copyright © 2005, Oracle. All rights reserved.

Life Cycle of a Broker Configuration

You can use the Add Standby Database Wizard in Enterprise Manager to add an existing standby
database to the configuration or create a new standby database and add it to the configuration.
The standby database can be either a physical or a logical database.
Note: If you are creating a new database, it must be a non-RAC database.
If you are using the CLI, the primary database and standby database must already exist. You
must construct the standby database from backups of the primary database control files and data
files, and then prepare it for recovery.
One way to think of this life cycle is in the context of creating and staging a play. In the create
configuration phase, you define the actors (resources) and the roles they play (primary or
standby), as well as where they should be on the stage (the site).
When you have made all your decisions and preparations, you go to opening night for the show s
debut ( enable configuration ).
During the run of the show, changes may be required because the actor playing the main
character falls ill ( make state or role changes, in which a standby becomes primary) or because
your show is in a new theater ( update database properties ). And as the director, you constantly
watch to make sure the play maintains your standards, so you make modifications as needed
( monitor and tune configuration ).

Oracle Database 10g: Data Guard Administration 3-8

 Data Guard Broker: Requirements

Enterprise Edition of Oracle Database 10g Release 1

Single-instance or multi-instance environment
COMPATIBLE must be set to 9.2.0 or higher for
primary and standby databases.
Oracle Net network files must be configured for
databases that you add to the configuration.
LOCAL_LISTENER on each instance must resolve to
an address that is reachable by all members.
GLOBAL_DBNAME attribute must be set to a
concatenation of:
db_unique_name_DGMGRL.db_domain

3-9 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker: Requirements

To use the Data Guard broker, you must comply with the following requirements:
You must use the Enterprise Edition of Oracle Database 10g Release 1.
You can use a single-instance or multi-instance environment.
You must set the COMPATIBLE initialization parameter to 9.2.0 or higher for the primary
and standby databases.
Enterprise Manager automatically configures the Oracle Net network files when it creates a
standby database. If you configure an existing standby database in the broker
configuration, you must configure the network files. You must use TCP/IP protocol.
The value of the LOCAL_LISTENER initialization parameter on each instance that is part
of your Data Guard broker configuration must resolve to a listener address that is reachable
by all members of the configuration.
To enable the Data Guard broker CLI to restart instances during the course of broker
operations, a service with a specific name must be statically registered with the local
listener of each instance. The value of the GLOBAL_DBNAME attribute must be set to a
concatenation of db_unique_name_DGMGRL.db_domain.
Note: Oracle Enterprise Manager 10g can manage a 9.2 Data Guard configuration.

Oracle Database 10g: Data Guard Administration 3-9

 Data Guard Broker: Requirements

DG_BROKER_START = TRUE
The primary database must be in ARCHIVELOG
mode.
All databases must be in MOUNT or OPEN mode.
Configure DG_BROKER_CONFIG_FILEn for any
RAC databases.
START_OPTIONS for any RAC databases must be
set to MOUNT in the Oracle Cluster Repository
(OCR).

3-10 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker: Requirements (continued)

You must set the DG_BROKER_START initialization parameter to TRUE. This enables the
DMON process.
Note: Enterprise Manager sets this parameter automatically.
The primary database must be in ARCHIVELOG mode.
Any database that is managed by the broker (including, for a RAC database, all instances
of the database) must be mounted or open. The broker cannot start an instance.
If any database in your configuration is a RAC database, you must configure the
DG_BROKER_CONFIG_FILEn initialization parameters for that database so that they
point to the same shared files for all instances of that database. You cannot use the default
values for these parameters.
Note: The shared files could be files on a cluster file system, if available, or on raw
devices.
If any database in your configuration is a RAC database, the START_OPTIONS for that
database must be set to MOUNT in the Oracle Cluster Repository (OCR) using SRVCTL, as
follows:
SRVCTL ADD DATABASE -d <db_unique_name> -o <$ORACLE_HOME> -s MOUNT
or
SRVCTL MODIFY DATABASE -d <db_unique_name> -o <$ORACLE_HOME> -s MOUNT

Oracle Database 10g: Data Guard Administration 3-10

 Data Guard Broker and the SPFILE

You must use a server parameter file (SPFILE) for

initialization parameters.
Using the SPFILE enables the Data Guard broker
to keep its configuration file and the database
SPFILE consistent.
If you use the broker, use Enterprise Manager or
DGMGRL to update database parameter values.

3-11 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker and the SPFILE

To ensure that the broker can update the values of parameters in both the database instance itself
and in the configuration file, you must use the persistent server initialization parameter file
(SPFILE) to control static and dynamic initialization parameters. Use of the SPFILE gives the
broker a mechanism that enables it to reconcile property values that you have selected when
using the broker with any related initialization parameter values that are recorded in the SPFILE.
Also, the SPFILE permits persistent Data Guard settings, so that Data Guard continues to work
even after the broker is disabled.
When you set definitions or values for database properties in the broker configuration, the broker
records the change in the configuration file and also propagates the changes to the related
initialization parameters in the SPFILE file in the Data Guard configuration.
When the configuration is enabled, the broker keeps the database property values in the Data
Guard configuration file consistent with the values of the database initialization parameters in
the SPFILE.
Even when the configuration is disabled, you can update database property values through the
broker. The broker retains the property settings (without validating the values) and updates the
database initialization parameters in the SPFILE and the in-memory settings the next time you
enable the broker configuration.

Oracle Database 10g: Data Guard Administration 3-11

Data Guard Broker and the SPFILE (continued)
For dynamic initialization parameters, the broker keeps the value of the database parameter
consistent in the System Global Area (SGA) for the instance, in the Data Guard configuration
files, and in the SPFILE.
For static initialization parameters, the value in the SGA may differ from what is in the
configuration files and in the SPFILE. Typically, the broker reconciles the differences by
updating all parameter and property values the next time the database instance is stopped and
restarted.
Note: When using the broker (with Enterprise Manager or the CLI), do not attempt to manually
set the parameters the broker controls. If you set them manually, one of two things happens.
Either you render your configuration inoperable, or the broker simply resets the parameter to the
setting it has recorded at the next opportunity. If you want to change a parameter value, you
must change it by using one of the broker interfaces.

Oracle Database 10g: Data Guard Administration 3-12

 Data Guard Monitor: DMON Process

Server-side background process

Part of each database instance in the
configuration
Created when you start the broker
Performs requested functions and monitors the
resource
Communicates with other DMON processes in the
configuration
Updates the configuration file

3-13 Copyright © 2005, Oracle. All rights reserved.

Data Guard Monitor: DMON Process

The Data Guard monitor comprises two components: the DMON process and the configuration
file.
The Data Guard Monitor process (DMON) is an Oracle background process that is part of each
database instance managed by the broker. When you start the Data Guard broker, a portion of the
SGA is allocated and a DMON process is created. The amount of memory allocated is typically
less then 50 KB per site; the actual amount on your system varies.
When you use Enterprise Manager or the CLI, the DMON process is the server-side component
that interacts with the local instance and the DMON processes running on other sites to perform
the requested function.
The DMON process is also responsible for monitoring the health of the broker configuration and
for ensuring that every database has a consistent copy of the broker configuration files in which
the DMON process stores its configuration data.

Oracle Database 10g: Data Guard Administration 3-13

 Data Guard Monitor: Configuration File

Automatically created and named using a default

path name and file name when the broker is
started
Override default path name and file name by
setting DG_BROKER_CONFIG_FILEn
Two files at each managed site
Managed automatically by the DMON process
Default names are operating system specific:
Default names for Unix and Linux: dr1<SID>.dat
and dr2<SID>.dat
Default location for Unix and Linux:
ORACLE_HOME/dbs
Default location for Windows:
ORACLE_HOME\database

3-14 Copyright © 2005, Oracle. All rights reserved.

Data Guard Monitor: Configuration File

The DMON process maintains persistent configuration data about all databases in the broker
configuration in a broker configuration file. Every database that is part of the Data Guard broker
configuration has two broker configuration files that are maintained and synchronized for each
database in the broker configuration. One of the files is in use and the other acts as a backup. The
configuration files are binary files and cannot be edited.
When the broker is started for the first time, the configuration files are created and named
automatically by using a default name that is specific to the operating system. You can override
this default name by setting the DG_BROKER_CONFIG_FILEn initialization parameters. You
can also change the configuration file names dynamically by issuing the ALTER SYSTEM SQL
statement.
The configuration files contain entries that describe the state and properties of the databases in
the configuration. For example, the files record the databases that are part of the configuration,
the roles and properties of each of the databases, and the state of each of the databases in the
configuration. Two files are maintained so that there is always a record of the last known valid
state of the configuration. The broker uses the data in the configuration file to configure and start
the databases, control each database s behavior, and provide information to the CLI and
Enterprise Manager.

Oracle Database 10g: Data Guard Administration 3-14

 Benefits of Using the Data Guard Broker

Enhances the high-availability, data-protection,

and disaster-protection capabilities inherent in
Oracle Data Guard by automating both
configuration and monitoring tasks
Streamlines the process for any one of the
standby databases to replace the primary
database and take over production processing
Helps you to logically define and create a Data
Guard configuration consisting of a primary
database and a standby database
Enables easy configuration of additional standby
databases

3-15 Copyright © 2005, Oracle. All rights reserved.

Benefits of Using the Data Guard Broker

By automating the tasks required to configure and monitor a Data Guard configuration, the
broker enhances the high-availability, data-protection, and disaster-protection capabilities that
are inherent in Oracle Data Guard.
If the primary database fails, the broker streamlines the process for any one of the standby
databases to replace the primary database and take over production processing.
The broker helps you to logically define and create a Data Guard configuration consisting of a
primary database and a (physical or logical, RAC or non-RAC) standby database.
The broker enables easy configuration of additional standby databases. After you create a Data
Guard configuration consisting of a primary and standby database, you can add up to eight
standby databases (new or existing, physical or logical) to each Data Guard configuration.

Oracle Database 10g: Data Guard Administration 3-15

 Benefits of Using the Data Guard Broker

Provides simplified, centralized, and extended

management
Automates switchover and failover to a specified
standby database in the broker configuration
Automatically communicates between the
databases in a Data Guard configuration using
Oracle Net Services
Provides built-in validation that monitors the
health of all of the databases in the configuration

3-16 Copyright © 2005, Oracle. All rights reserved.

Benefits of Using the Data Guard Broker (continued)

The broker provides simplified, centralized, and extended management.
The broker automates switchover and failover to a specified standby database in the broker
configuration.
The broker automatically communicates between the databases in a Data Guard configuration
using Oracle Net Services. The database can be local or remote, connected by a LAN or
geographically dispersed over a WAN.
The broker provides built-in validation that monitors the health of all of the databases in the
configuration.

Oracle Database 10g: Data Guard Administration 3-16

 Data Guard Broker Interfaces

Oracle Enterprise Manager 10g Grid Control:

Contains wizards to simplify creating and managing
standby databases
Command-line interface (CLI):
Started by entering DGMGRL at the command prompt
where the Oracle server is installed
Enables you to control and monitor a Data Guard
configuration from the CLI prompt or in scripts

3-17 Copyright © 2005, Oracle. All rights reserved.

Data Guard Broker Interfaces

Oracle Enterprise Manager automates and simplifies the management of a Data Guard
configuration.
Oracle Enterprise Manager 10g Grid Control includes the following Data Guard features:
Wizard-driven creation of standby databases
Wizard-driven creation of a broker configuration based on an existing primary and standby
database
Complete monitoring and proactive event reporting through e-mail or pagers
Simplified control of the databases through their potential states. For example, with
Enterprise Manager you can take a database offline, put it online, start or stop the log
transport services, start or stop the log apply services, place a standby database in read-only
mode, and so on.
Pushbutton switchover and failover: Grid Control enables you to execute a switchover or
failover between a primary and a standby database by simply clicking a button.

Oracle Database 10g: Data Guard Administration 3-17

Data Guard Broker Interfaces (continued)
The DGMGRL command-line interface (CLI) includes:
Configuration and setup tasks
Management and control of the configuration
Commands to check the status and health of the configuration
Commands to execute role changes
For additional information about using these interfaces, see Oracle Data Guard Broker.

Oracle Database 10g: Data Guard Administration 3-18

 Using Oracle Enterprise Manager 10g
Grid Control

Click Data Guard to access

the Data Guard pages.

3-19 Copyright © 2005, Oracle. All rights reserved.

Using Oracle Enterprise Manager 10g Grid Control

Access the Data Guard features in Grid Control by performing the following steps:
1. Click the Targets tab to go to the Targets page.
2. Click Databases to go to the Databases page.
3. On the Databases page, you can see a listing of all discovered databases, including the
primary database. Click the primary database to go to the primary database home page.
4. Click Administration.
5. Click Data Guard in the High Availability section.

Oracle Database 10g: Data Guard Administration 3-19

 Data Guard Overview Page

3-20 Copyright © 2005, Oracle. All rights reserved.

Data Guard Overview Page

On the Data Guard Overview page, you can:
View the protection mode and access the page to edit the protection mode
View a summary showing the amount of data that the standby has not received
View information about the primary database
View or access pages to change information for the standby databases:
- Add a standby database to the broker configuration
- Change the state or properties
- Discontinue Data Guard broker control
- Switch the role from standby to primary
- Transition the standby database to the role of primary database
Access pages to view performance information for the configuration and status of online
redo log files for each standby database
Perform a verification process on the Data Guard configuration
You can click Help to access information about using each page.

Oracle Database 10g: Data Guard Administration 3-20

 Enterprise Manager Metrics and Alerts

Metrics: Units of measurement used to assess the

health of your system
Thresholds: Boundary values against which
monitored metric values are compared
Alert: Generated when a threshold is reached

3-21 Copyright © 2005, Oracle. All rights reserved.

Enterprise Manager Metrics and Alerts

Metrics are units of measurement that are used to assess the health of your system. Each target
comes with a predefined set of metrics. Metrics have thresholds associated with them.
Thresholds are boundary values against which monitored metric values are compared. Some of
the thresholds are predefined by Oracle; others are not.
When a threshold is reached, an alert is generated. An alert is an indicator signifying that a
particular condition has been encountered. An alert is triggered when one of the following
conditions is true:
A threshold is reached.
An alert has been cleared.
The availability of a monitored service changes.
A specific condition occurs. For example, an alert is triggered whenever an error message
is written to a database alert log file.
Alerts are detected through a polling-based mechanism by checking for the monitored condition
from a separate process at regular, predefined intervals.
You can associate an alert with a notification, the automatic execution of a job, and so on.

Oracle Database 10g: Data Guard Administration 3-21

 Using Data Guard Metrics

Enterprise Manager includes the following Data Guard

metrics:
Data Guard Status
Data Not Applied (MB)
Data Not Applied (log
files)
Data Not Received (MB)
Data Not Received (log
files)

3-22 Copyright © 2005, Oracle. All rights reserved.

Using Data Guard Metrics

You can use Enterprise Manager to monitor the status and log file activity. In addition,
Enterprise Manager automatically monitors the status and archived redo log file activity on the
primary and standby databases and provides the following metrics:
Data Guard Status: Status of each database in the broker configuration
Data Not Applied (MB): Difference (in megabytes) between the last log file received and
the last log file applied on each standby database
Data Not Applied (log files): Difference (in number of archived redo log files) between
the last log file received and the last log file applied on each standby database
Data Not Received (MB): Difference (in megabytes) between the current log file on the
primary database and the last log file received on each standby database
Data Not Received (log files): Difference (in number of archived redo log files) between
the current log file on the primary database and the last log file received on each standby
database
You can set up Email Services to notify you with an e-mail message if any of the metrics are
triggered.
Note: These metrics are seen on the primary database only.

Oracle Database 10g: Data Guard Administration 3-22

 Managing Data Guard Metrics

1. Configure notification methods.

2. View the All Metrics page.
3. Set or change Data Guard metric thresholds.
4. View triggered metrics.

3-23 Copyright © 2005, Oracle. All rights reserved.

Managing Data Guard Metrics

You can specify that an e-mail notification be sent to you when a Data Guard metric is triggered.
Use the following procedure to configure the notification:
1. Configure notification methods in Enterprise Manager.
a. Click Setup at the top of the Database Home page.
b. Click Notification Methods on the Setup page.
c. Enter the appropriate information in the Mail Server section and click Apply. You
can click Test Mail Servers to verify your configuration.
2. View the All Metrics page by clicking All Metrics in the Related Links section on the
Database Home page. Then view all of the Oracle Enterprise Manager metrics, including
the metrics for Data Guard.
3. Set or change Data Guard metric thresholds by clicking Manage Metrics in the Related
Links section on the All Metrics page to access the Manage Metrics page. You can set and
change the five Data Guard metrics from the Manage Metrics page.
4. View triggered metrics: If a metric condition is triggered or a threshold value is exceeded,
an alert is issued. Click Data Guard on the All Metrics page to view triggered metrics. You
can click the metric and then click a particular database to see details.

Oracle Database 10g: Data Guard Administration 3-23

 Benefits of Using Enterprise Manager

Enables you to manage your configuration using a

familiar interface and event-management system
Automates and simplifies the complex operations
of creating and managing standby databases
through the use of wizards
Performs all Oracle Net Services configuration
changes that are necessary to support log
transport services and log apply services
Provides a verify operation to ensure that log
transport services and log apply services are
configured and functioning properly
Enables you to select a new primary database
from a set of viable standby databases

3-24 Copyright © 2005, Oracle. All rights reserved.

Benefits of Using Enterprise Manager

Managing your Data Guard configuration with Oracle Enterprise Manager 10g Grid Control
provides the following benefits:
Enables you to manage your configuration using the familiar Enterprise Manager interface
and event-management system
Provides a wizard that automates the complex tasks involved in creating a broker
configuration
Provides the Add Standby Database Wizard to guide you through the process of adding
more databases
Performs all Oracle Net Services configuration changes that are necessary to support log
transport services and log apply services across the configuration
Provides a verify operation to ensure that log transport services and log apply services are
configured and functioning properly
Enables you to select a new primary database from a set of viable standby databases when
you need to initiate a role change for a switchover or failover operation

Oracle Database 10g: Data Guard Administration 3-24

 Using the Command-Line Interface
of the Data Guard Broker
DGMGRL> connect sys/oracle
Connected.
DGMGRL> show configuration verbose

Configuration
Name: ORCL_EDRSR9P1.oracle.com
Enabled: YES
Protection Mode: MaxPerformance
Databases:
ORCL_EDRSR9P1 - Primary database
site1_edrsr9p1 - Physical standby database
site2_edrsr9p1 - Logical standby database

Current status for "ORCL_EDRSR9P1.oracle.com":

SUCCESS

3-25 Copyright © 2005, Oracle. All rights reserved.

DGMGRL Commands
The following commands are available in DGMGRL (the Data Guard CLI). Many of these
commands have additional arguments that are not described here. This is simply an overview
listing.
ADD: Adds a standby database to the broker configuration
CONNECT: Connects a given username to the specified instance
CREATE: Enables you to create broker configurations
DISABLE: Enables you to disable broker control of a configuration or database so that the
object is no longer managed by the broker
EDIT: Used to edit a configuration, database, or instance
ENABLE: Enables you to enable broker control of a configuration or database
EXIT/QUIT: Exits the Data Guard CLI (DGMGRL)
FAILOVER: Performs a database failover operation in which one of the standby databases
changes to the role of primary database. This is an unplanned transition that may result in
the loss of application data.
HELP: Displays online help for the commands in DGMGRL
REMOVE: Removes a broker configuration, including all of its database profiles, a
specified standby database profile, or knowledge of an instance

Oracle Database 10g: Data Guard Administration 3-25

DGMGRL Commands (continued)
SHOW: Displays either a brief or a detailed summary of information about the broker
configuration, database, or instance. Also can display the dependency tree and default
online states for the broker configuration, as well as the configuration log or the Oracle
database alert log.
SHUTDOWN: Shuts down a currently running Oracle database instance
STARTUP: Starts an Oracle instance with several options, including mounting and opening
a database
SWITCHOVER: Performs a switchover operation in which the current primary database
becomes a standby database and the standby database to which the CLI is currently
connected becomes the primary database
Note: The ALTER command has been deprecated in Oracle Database 10g. The new EDIT
command provides comparable functionality.

Oracle Database 10g: Data Guard Administration 3-26

 Summary

In this lesson, you should have learned how to:

Describe the Data Guard broker management
model
Describe the Data Guard broker architecture
Describe Data Guard broker components
Access Enterprise Manager
Invoke DGMGRL (the Data Guard CLI)

3-27 Copyright © 2005, Oracle. All rights reserved.

Oracle Database 10g: Data Guard Administration 3-27