Preface

This document provides complete information about the Oracle9i Data Guard broker, a management and monitoring interface that helps you configure, monitor, and control an Oracle9i Data Guard configuration.

This preface contains these topics:

• Audience
• Documentation Accessibility
• Organization
• Related Documentation
• Conventions

Audience

Oracle9i Data Guard Broker is intended for database administrators (DBAs) and system administrators who want to use the Oracle9i Data Guard broker to automate many of the tasks involved in configuring and monitoring an Oracle9i Data Guard configuration.

The discussions herein assume that readers are already familiar with Oracle9i Data Guard, Oracle Enterprise Manager, and the network services provided by Oracle Net.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Organization

This document contains:

Chapter 1, "Oracle9i Data Guard Broker Concepts"

This chapter introduces Oracle9i Data Guard broker concepts and terminology.

Chapter 2, "Managing Broker Configurations"

This chapter helps you set up and install Oracle9i Data Guard and configure a Data Guard configuration. It also describes states, status, and properties of resources.

Chapter 3, "Managing Site Objects"

This chapter describes managing site resources, includes state changes, switchover operations, and failover operations.

Chapter 4, "Managing Database Resources"

This chapter describes configuring and managing database resource objects.

Chapter 5, "Data Guard Manager Scenarios"

This chapter shows how to use the Data Guard Manager graphical user interface to create, manage, and monitor a broker configuration.

Chapter 6, "Data Guard Command-Line Interface Scenarios"

This chapter describes how to use the Data Guard command-line interface to create, manage, and monitor a broker configuration.

Chapter 7, "Data Guard Command-Line Interface Reference"

This chapter provides reference information for the DGMGRL command-line interface.

Chapter 8, "Database Resource Properties"

This chapter provides reference information about database resource properties.

Glossary

Related Documentation

Refer to the following documentation for more information about Oracle9i Data Guard:

• Oracle9i Data Guard Concepts and Administration
• Oracle9i release notes specific to your operating system.
• Oracle9i installation guide specific to your operating system.
• For more information about Oracle9i Data Guard Manager, see the online help and quick tour available with this graphical user interface. To access the online help topics, click Help on the menu bar in Data Guard Manager.

Refer to the following documentation for information about related products:

• Oracle9i Database Concepts.
• Oracle9i Net Services Administrator's Guide
• Oracle Enterprise Manager product documentation set.

In North America, printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

http://www.oraclebookshop.com/

Other customers can contact their Oracle representative to purchase printed documentation.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://otn.oracle.com/admin/account/membership.html

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://otn.oracle.com/docs/index.htm

To access the database documentation search engine directly, please visit

http://tahiti.oracle.com

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

• Conventions in Text
• Conventions in Code Examples

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle9i Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
UPPERCASE monospace (fixed-width font)	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	You can specify this clause only for a NUMBER column. You can back up the database by using the BACKUP command. Query the TABLE_NAME column in the USER_TABLES data dictionary view. Use the DBMS_STATS.GENERATE_STATS procedure.
lowercase monospace (fixed-width font)	Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	Enter sqlplus to open SQL*Plus. The password is specified in the orapwd file. Back up the datafiles and control files in the /disk1/oracle/dbs directory. The department_id, department_name, and location_id columns are in the hr.departments table. Set the QUERY_REWRITE_ENABLED initialization parameter to true. Connect as oe user. The JRepUtil class implements these methods.
lowercase monospace (fixed-width font) italic	Lowercase monospace italic font represents placeholders or variables.	You can specify the parallel_clause. Run Uold_release.SQL where old_release refers to the release you installed prior to upgrading.
MixedCase monospace (fixed-width font)	Mixed-case monospace typeface indicates a Data Guard database property. The mixed case helps you visually differentiate a Data Guard property from its related database initialization parameter, which is always shown in uppercase typeface.	The StandbyFileManagement property corresponds to the STANDBY_FILE_MANAGEMENT initialization parameter.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention	Meaning	Example
[ ]	Brackets enclose one or more optional items. Do not enter the brackets.	DECIMAL (digits [ , precision ])
{ }	Braces enclose two or more items, one of which is required. Do not enter the braces.	{ENABLE | DISABLE}
|	A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.	{ENABLE | DISABLE} [COMPRESS | NOCOMPRESS]
...	Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code	CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln FROM employees;
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.
Other notation	You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.	acctbal NUMBER(11,2); acct CONSTANT NUMBER(4) := 3;
Italics	Italicized text indicates placeholders or variables for which you must supply particular values.	CONNECT SYSTEM/system_password DB_NAME = database_name
UPPERCASE	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.	SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TABLE hr.employees;
lowercase	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	SELECT last_name, employee_id FROM employees; sqlplus hr/hr CREATE USER mjones IDENTIFIED BY ty3MU9;
MixedCase monospace (fixed-width font)	Mixed-case monospace typeface indicates a Data Guard database property. The mixed case helps you visually differentiate a Data Guard property from its related database initialization parameter, which is always shown in uppercase typeface.	The StandbyFileManagement property corresponds to the STANDBY_FILE_MANAGEMENT initialization parameter.