Contents

Title and Copyright Information

List of Examples

List of Figures

List of Tables

Send Us Your Comments

Preface

Audience

Documentation Accessibility

Organization

Related Documentation

Conventions

What's New in Data Guard?

Oracle9i Release 2 (9.2) New Features in Data Guard

Oracle9i Release 1 (9.0.1) New Features in Data Guard

Oracle8i New Features in Data Guard

Part I Concepts and Administration

1 Oracle9i Data Guard Concepts

1.1 Oracle9i Data Guard Overview

1.2 Benefits of Oracle9i Data Guard

1.3 Physical and Logical Standby Databases

1.3.1 Configuring Local and Remote Standby Databases

1.3.2 Physical Standby Databases

1.3.3 Logical Standby Databases

1.4 Log Transport Services and Log Apply Services

1.5 Role Management Services

1.6 Data Guard Architecture

1.7 Data Guard Interfaces

1.8 Operational Requirements

2 Configurations and Considerations

2.1 Number of Standby Databases

2.2 Standby Databases in the Data Guard Environment

2.3 Method of Transmitting Redo Logs to the Standby Database

2.3.1 Independence of Automatic Archiving and Log Apply Services

2.3.2 Optional Manual Copy of Archived Redo Logs

2.3.3 Functions of Log Transport Services

2.4 Method of Applying Redo Logs or SQL Statements

2.4.1 Functions of Log Apply Services

2.5 Location and Directory Structure of Primary and Standby Databases

2.5.1 Number and Location of Standby Databases

2.5.2 Directory Structure of Standby Databases

2.5.3 Configuration Options

2.6 Types of Standby Databases

2.7 Examples of Using Multiple Standby Databases

3 Creating a Physical Standby Database

3.1 Checklist of Tasks

3.2 Creating a Standby Database: Basic Tasks

3.3 Creating the Standby Database Files

3.3.1 Using Backups for Standby Creation

3.3.2 Creating the Standby Datafiles

3.3.3 Creating the Standby Control File

3.3.4 Copying Files to the Standby Site

3.4 Creating the Standby Initialization Parameter File

4 Creating a Logical Standby Database

4.1 Preparing to Create a Logical Standby Database

4.2 Creating a Logical Standby Database

5 Log Transport Services

5.1 Introduction to Log Transport Services

5.1.1 Background

5.1.2 Functional Overview

5.1.3 Log Transport Services Process Architecture

5.2 Log Transport Services Capabilities

5.2.1 Permission

5.2.2 Destination

5.2.3 Transmission

5.2.4 Reception

5.2.5 Failure Resolution

5.3 Log Transport Services Interfaces

5.3.1 Database Initialization Parameters

5.3.2 SQL Interface

5.4 Configuring Log Transport Services: Basic Tasks

5.5 Configuring Log Transport Services on the Primary Database

5.5.1 Configuring Log Transport Services

5.5.2 Setting Up the Log Transport Services Environment

5.6 Configuring Log Transport Services on the Standby Database

5.6.1 Configuring the Standby Initialization Parameter File

5.6.2 Transferring the Initialization Parameter File to the Standby Database

5.6.3 Setting Up the Initialization Parameter File

5.7 Data Protection Modes

5.7.1 Maximum Protection

5.7.2 Maximum Availability

5.7.3 Maximum Performance

5.8 Configuring Log Transport Services for Data Protection

5.8.1 Specifying LGWR or ARCH for the Redo Log Writing Process

5.8.2 Specifying SYNC or ASYNC for the Network Transmission Mode

5.8.3 Specifying AFFIRM or NOAFFIRM for the Disk Write Option

5.8.4 Comparing Network and Disk I/O Methods

5.8.5 Setting the Data Protection Mode for an Overall Failure Resolution Policy

5.9 Comparing Network and Disk I/O Methods

5.10 Network Tuning for Log Transport Services

5.11 Log Transport Services Monitoring

5.11.1 Gathering Redo Log Archival Information

5.11.2 Setting Archive Tracing

6 Log Apply Services

6.1 Introduction to Log Apply Services

6.2 Applying SQL Statements to Logical Standby Databases

6.2.1 Managing SQL Apply Operations

6.2.2 Summary of the DBMS_LOGSTDBY PL/SQL Supplied Package

6.2.3 Delaying the Application of Archived Redo Logs

6.2.4 Ensuring That Redo Logs Are Being Applied

6.3 Applying Logs to Physical Standby Databases

6.3.1 Managed Recovery Mode

6.3.2 Starting Managed Recovery for Physical Standby Databases

6.3.3 Controlling Managed Recovery Mode

6.3.4 Datafile Management

6.3.5 Read-Only Mode

6.3.6 Read-Only Mode Considerations

6.4 Monitoring Log Apply Services

6.4.1 Accessing the V$MANAGED_STANDBY Fixed View (Physical Standby Databases Only)

6.4.2 Accessing the V$ARCHIVE_DEST_STATUS Fixed View

6.4.3 Accessing the V$ARCHIVED_LOG Fixed View

6.4.4 Accessing the V$LOG_HISTORY Fixed View

6.4.5 Accessing the V$DATAGUARD_STATUS Fixed View

6.4.6 Accessing the DBA_LOGSTDBY_LOG View (Logical Standby Databases
Only)

6.4.7 Accessing the DBA_LOGSTDBY_PROGRESS View (Logical Standby Databases Only)

6.4.8 Setting Archive Tracing

6.5 Managing Archive Gaps

7 Role Management Services

7.1 Database Roles and Role Transitions

7.2 Database Switchover

7.2.1 Preparing to Perform a Successful Switchover Operation

7.2.2 Switchover Operations Involving a Physical Standby Database

7.2.3 Switchover Operations Involving a Logical Standby Database

7.2.4 Transitioning Multiple Standby Databases to the Primary Role

7.2.5 Validating the Switchover Transition (Physical Standby Databases Only)

7.3 Database Failover

7.3.1 Planning for Database Failover

7.3.2 Primary Database No-Data-Loss Recovery

7.3.3 Graceful Failover

7.3.4 Forced Failover

8 Managing a Physical Standby Database

8.1 Backing Up the Primary Database Using the Standby Database

8.2 Monitoring Events That Affect the Standby Database

8.2.1 Dynamic Performance Views (Fixed Views)

8.2.2 Monitoring the Primary and Standby Databases

8.2.3 Determining Which Logs Have Been Applied to the Standby Database

8.2.4 Determining Which Logs Have Not Been Received by the Standby Site

8.3 Responding to Events That Affect the Standby Database

8.3.1 Adding or Dropping Tablespaces and Adding or Deleting Datafiles in the Primary Database

8.3.2 Renaming Datafiles on the Primary Database

8.3.3 Adding or Deleting Redo Logs on the Primary Database

8.3.4 Resetting or Clearing Unarchived Redo Logs on the Primary Database

8.3.5 Altering the Primary Database Control File

8.3.6 Taking Datafiles in the Standby Database Offline

8.3.7 Detecting Unlogged or Unrecoverable Operations

8.3.8 Refreshing the Standby Database Control File

8.3.9 Clearing Online Redo Logs

8.4 Standby Databases in an Oracle Real Application Clusters Configuration

8.4.1 Setting Up a Cross-Instance Archival Database Environment

9 Managing a Logical Standby Database

9.1 Configuring and Managing Logical Standby Databases

9.1.1 Controlling User Access to Tables in a Logical Standby Database

9.1.2 Skipping Tables in a Logical Standby Database

9.1.3 Adding Tables to a Logical Standby Database

9.1.4 Finding Unsupported Database Objects

9.1.5 Viewing and Controlling Logical Standby Events

9.1.6 Viewing SQL Apply Operations Activity

9.1.7 Determining How Much Redo Log Data Has Been Applied

9.1.8 Recovering from Errors

9.2 Tuning Logical Standby Databases

10 Data Guard Scenarios

10.1 Physical Standby Database Scenarios

10.1.1 Scenario 1: Creating a Physical Standby Database on the Same System

10.1.2 Scenario 2: Creating a Physical Standby Database on a Remote Site

10.1.3 Scenario 3: Accommodating Physical Changes in the Primary Database

10.1.4 Scenario 4: Recovering After the NOLOGGING Clause Is Specified

10.1.5 Scenario 5: Deciding Which Standby Database to Fail Over to in a Multiple Physical Standby Database Configuration

10.1.6 Scenario 6: Switching Over a Primary Database to a Standby Database

10.1.7 Scenario 7: Recovering After a Network Failure

10.1.8 Scenario 8: Re-creating a Physical Standby Database

10.1.9 Scenario 9: Standby Database with a Time Lag

10.1.10 Scenario 10: Using a Standby Database to Back Up the Primary Database

10.2 Logical Standby Database Scenarios

10.2.1 Scenario 1: Skipping a Transaction

10.2.2 Scenario 2: Creating or Re-creating a Table

10.2.3 Scenario 3: Failover Operations When In Maximum Availability Mode

10.2.4 Scenario 4: Switchover Operations

Part II Reference

11 Initialization Parameters

12 LOG_ARCHIVE_DEST_n Parameter Attributes

12.1 About LOG_ARCHIVE_DEST_n Parameter Attributes

AFFIRM and NOAFFIRM

ALTERNATE and NOALTERNATE

ARCH and LGWR

DELAY and NODELAY

DEPENDENCY and NODEPENDENCY

LOCATION and SERVICE

MANDATORY and OPTIONAL

MAX_FAILURE and NOMAX_FAILURE

NET_TIMEOUT and NONET_TIMEOUT

QUOTA_SIZE and NOQUOTA_SIZE

QUOTA_USED and NOQUOTA_USED

REGISTER and NOREGISTER

REGISTER=location_format

REOPEN and NOREOPEN

SYNC and ASYNC

TEMPLATE and NOTEMPLATE

12.2 Attribute Compatibility for Archive Destinations

13 SQL Statements

13.1 ALTER DATABASE ACTIVATE STANDBY DATABASE

13.2 ALTER DATABASE ADD [STANDBY] LOGFILE

13.3 ALTER DATABASE ADD [STANDBY] LOGFILE MEMBER

13.4 ALTER DATABASE ADD SUPPLEMENTAL LOG DATA

13.5 ALTER DATABASE COMMIT TO SWITCHOVER

13.6 ALTER DATABASE CREATE STANDBY CONTROLFILE AS

13.7 ALTER DATABASE DROP [STANDBY] LOGFILE

13.8 ALTER DATABASE DROP [STANDBY] LOGFILE MEMBER

13.9 ALTER DATABASE [NO]FORCE LOGGING

13.10 ALTER DATABASE MOUNT STANDBY DATABASE

13.11 ALTER DATABASE OPEN READ ONLY

13.12 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE

13.13 ALTER DATABASE REGISTER LOGFILE

13.14 ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE}

13.15 ALTER DATABASE START LOGICAL STANDBY APPLY

13.16 ALTER DATABASE {STOP|ABORT} LOGICAL STANDBY APPLY

14 Views

About Views

DBA_LOGSTDBY_EVENTS (Logical Standby Databases Only)

DBA_LOGSTDBY_LOG (Logical Standby Databases Only)

DBA_LOGSTDBY_NOT_UNIQUE (Logical Standby Databases Only)

DBA_LOGSTDBY_PARAMETERS (Logical Standby Databases Only)

DBA_LOGSTDBY_PROGRESS (Logical Standby Databases Only)

DBA_LOGSTDBY_SKIP (Logical Standby Databases Only)

DBA_LOGSTDBY_SKIP_TRANSACTION (Logical Standby Databases Only)

DBA_LOGSTDBY_UNSUPPORTED (Logical Standby Databases Only)

V$ARCHIVE_DEST

V$ARCHIVE_DEST_STATUS

V$ARCHIVE_GAP

V$ARCHIVED_LOG

V$DATABASE

V$DATAFILE

V$DATAGUARD_STATUS

V$LOG

V$LOGFILE

V$LOG_HISTORY

V$LOGSTDBY (Logical Standby Databases Only)

V$LOGSTDBY_STATS (Logical Standby Databases Only)

V$MANAGED_STANDBY (Physical Standby Databases Only)

V$STANDBY_LOG

Part III Appendixes and Glossary

A Troubleshooting the Standby Database

A.1 Problems During Standby Database Preparation

A.1.1 The Standby Archive Destination Is Not Defined Properly

A.1.2 The Standby Site Does Not Receive Logs Archived by the Primary Database

A.1.3 You Cannot Mount the Physical Standby Database

A.2 Problems Switching Over to a Standby Database

A.2.1 Switchover Fails

A.2.2 Startup of Second Physical Standby Database Fails

A.2.3 Archived Redo Logs Are Not Applied to the Standby Database After
Switchover

A.2.4 Switchover Fails in a Real Application Clusters Configuration

A.2.5 Switchover Fails When SQL Sessions Are Active

A.3 What to Do If SQL Apply Operations to a Logical Standby Database Stop

B Manual Recovery

B.1 Preparing a Standby Database for Manual Recovery: Basic Tasks

B.2 Placing the Standby Database in Manual Recovery Mode

B.2.1 Initiating Manual Recovery Mode

B.2.2 When Is Manual Recovery Required?

B.3 Resolving Archive Gaps Manually

B.3.1 What Causes Archive Gaps?

B.3.2 Determining Whether an Archive Gap Exists

B.3.3 Manually Transmitting the Logs in the Archive Gap to the Standby Site

B.3.4 Manually Applying the Logs in the Archive Gap to the Standby Database

B.4 Renaming Standby Database Files Manually

C Log Writer Asynchronous Network I/O

D Standby Database Real Application Clusters Support

E Cascading Standby Databases

E.1 Background Information

E.2 Configuring Cascading Standby Databases

E.2.1 Cascading Physical Standby Databases

E.2.2 Cascading Logical Standby Databases

E.3 Examples of Cascading Standby Databases

E.3.1 Scenario 1

E.3.2 Scenario 2

E.3.3 Scenario 3

E.3.4 Scenario 4

E.3.5 Scenario 5

Glossary

Index