List of Figures

1-1 Typical Data Guard Configuration

1-2 Automatic Updating of a Physical Standby Database

1-3 Automatic Updating of a Logical Standby Database

1-4 Data Guard Overview Page in Oracle Enterprise Manager

2-1 Possible Standby Configurations

5-1 Transmitting Redo Data

5-2 Primary Database Archiving When There Is No Standby Database

5-3 Archiving to Local Destinations Before Archiving to Remote Destinations

5-4 LGWR SYNC Archival to a Remote Destination with Standby Redo Log Files

5-5 LGWR ASYNC Archival with Network Server (LNSn) Processes

5-6 Archival Operation to an Alternate Destination Device

5-7 Data Guard Configuration with Dependent Destinations

6-1 Applying Redo Data to a Standby Destination Using Real-Time Apply

7-1 Data Guard Configuration Before Switchover

7-2 Standby Databases Before Switchover to the New Primary Database

7-3 Data Guard Environment After Switchover

7-4 Failover to a Standby Database

8-1 Standby Database Open for Read-Only Access

9-1 SQL Apply Processing

9-2 Progress States During SQL Apply Processing

11-1 Data Guard Configuration Before Upgrade

11-2 Upgrade the Logical Standby Database Release

11-3 Running Mixed Releases

11-4 After a Switchover

11-5 Both Databases Upgraded

12-1 Primary and Physical Standby Databases Before a Role Transition

12-2 Primary and Physical Standby Databases After a Role Transition

12-3 Configuring Destinations for a Primary Database and a Logical Standby Database

12-4 Primary and Logical Standby Databases After a Role Transition

12-5 Configuring a Primary Database with Physical and Logical Standby Databases

12-6 Primary, Physical, and Logical Standby Databases After a Role Transition

12-7 Using a Physical Standby Database As a Testing and Reporting Database

12-8 Manual Recovery of Archived Redo Log Files in an Archive Gap

D-1 Transmitting Redo Data from a Multi-Instance Primary Database

D-2 Standby Database in Real Application Clusters

E-1 Cascaded Destination Configuration Example