Appendixes

This part contains the following appendixes:

• Troubleshooting Oracle Data Guard

• Upgrading and Downgrading Databases in an Oracle Data Guard Configuration

• Data Type and DDL Support on a Logical Standby Database

• Oracle Data Guard and Oracle Real Application Clusters

• Creating a Standby Database with Recovery Manager

• Setting Archive Tracing

• Performing Role Transitions Using Old Syntax

• Using the ALTERNATE Attribute to Configure Remote Alternate Destinations

• Troubleshooting Oracle Data Guard
  These are some of the problems that can occur on a standby database, and the troubleshooting procedures to address them.
• Patching, Upgrading, and Downgrading Databases in an Oracle Data Guard Configuration
  These topics address how to upgrade and downgrade an Oracle database when a physical or logical standby database is present in the Oracle Data Guard configuration.
• Data Type and DDL Support on a Logical Standby Database
  When setting up a logical standby database, you must ensure the logical standby database can maintain the datatypes and tables in your primary database.
• Oracle Data Guard and Oracle Real Application Clusters
  An Oracle Data Guard configuration can consist of any combination of single-instance and Oracle Real Application Clusters (Oracle RAC) multiple-instance databases.
• Creating a Standby Database with Recovery Manager
  These topics describe how to use Oracle Recovery Manager to create a standby database.
• Setting Archive Tracing
  The Oracle database uses the LOG_ARCHIVE_TRACE initialization parameter to enable and control the generation of comprehensive trace information for log archiving and redo transport activity.
• Performing Role Transitions Using Old Syntax
  Prior to Oracle Database 12c Release 1 (12.1), the procedures for performing switchovers and failovers to a physical standby database were different.
• Using the ALTERNATE Attribute to Configure Remote Alternate Destinations
  As of Oracle Database 12c Release 2 (12.2), the preferred method for creating alternate log archive destinations for remote standby databases and far sync instances that take over if the active destination fails is to use the GROUP and PRIORITY attributes.