List of Examples

• 3-1 Primary Database: Primary Role Initialization Parameters
• 3-2 Primary Database: Standby Role Initialization Parameters
• 3-3 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 Parameters Used to Set Up Protection After a Role Change
• 5-3 Parameters Used to Set Up High Availability Far Sync Instances
• 7-1 Some of the Initialization Parameters Used When Cascading Redo
• 13-1 Monitoring Events with DBA_LOGSTDBY_EVENTS
• 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
• 17-1 Automatically Failing Over to an Alternate Local Destination
• 17-2 Automatic Local Alternate Fallback
• 17-3 Defining an Alternate Oracle Net Service Name to the Same Standby Database
• 17-4 Automatically Failing Over to an Alternate Remote Destination
• 17-5 Automatic Remote Alternate Fallback
• 17-6 Highly Available Dual Far Sync
• A-1 Setting a Retry Time and Limit
• A-2 Specifying an Alternate Destination
• A-3 Warning Messages Reported for ITL Pressure
• C-1 PL/SQL Skip Procedure for RegisterSchema