List of Examples

• 3-1 Modifying Initialization Parameters for a Physical Standby Database
• 4-1 Primary Database: Logical Standby Role Initialization Parameters
• 4-2 Modifying Initialization Parameters for a Logical Standby Database
• 5-1 Some of the Initialization Parameters Used for Far Sync Instances
• 5-2 Configuring for Single Destination Failover
• 5-3 Configuring for Multiple Standby Database Redo Destination Failover
• 5-4 Parameters Used to Set Up the High Availability Far Sync Instance
• 5-5 Parameters Used to Set Up Protection After a Role Change
• 7-1 Some of the Initialization Parameters Used When Cascading Redo
• 14-1 Setting Switchover to Enforce Apply Lag Requirements
• 14-2 Resetting Logging Back to Its Default Value
• 14-3 Designating a Database as an Optional Participant
• 14-4 Setting a Database to Protect the Transient Logical Standby
• 14-5 Basic Rolling Upgrade Steps
• 14-6 Rolling Upgrade Between Two Databases
• 14-7 Rolling Upgrade Between Three Databases
• 14-8 Rolling Upgrade Between Four Databases
• 14-9 Rolling Upgrade on a Reader Farm
• 14-10 Rolling Upgrade for Application Testing
• 14-11 Resuming a Rolling Upgrade After a Failover to a New Primary
• 14-12 Resuming a Rolling Upgrade After a Failover to a New Transient Logical
• 15-1 Primary and All Standbys Are Mounted or Open and DBCOMP Is Executed From the Primary
• 15-2 Primary and All Standbys Are Mounted or Open and DBCOMP Is Executed From a Standby
• 15-3 Primary Is Mounted or Open, But Not All Standbys Are, and DBCOMP is Executed From the Primary
• 15-4 Primary Is Mounted or Open, But Not All Standbys Are, and DBCOMP is Executed From a Standby
• 15-5 Primary is Not Mounted, But Multiple Standbys Are Mounted or Open
• 15-6 Primary Is Mounted or Open, But No Standbys Are Mounted or Open
• 17-1 Automatically Failing Over to an Alternate Local Destination
• 17-2 Automatic Local Alternate Fallback
• A-1 Setting a Retry Time and Limit
• A-2 Specifying an Alternate Destination
• C-1 PL/SQL Skip Procedure for RegisterSchema