Table of Contents
- List of Examples
- List of Figures
- List of Tables
- Title and Copyright Information
- Preface
- Changes in This Release for Oracle Data Guard Broker
- 1 Oracle Data Guard Broker Concepts
- 2 Oracle Data Guard Installation
- 3 Managing Broker Configurations
-
4
Managing the Members of a Broker Configuration
- 4.1 Managing Broker Configuration Members
- 4.2 Managing States of Broker Configuration Members
- 4.3 Managing Database Properties
-
4.4
Managing Redo Transport Services
- 4.4.1 Setting Up For Redo Transport
- 4.4.2 Managing Redo Transport Services for Data Protection Modes
- 4.4.3 Advanced Redo Transport Settings
- 4.4.4 Turning Redo Transport Services On and Off
- 4.4.5 Specifying Locations for Archived Redo Log Files
- 4.4.6 Other Redo Transport Settings
- 4.4.7 Redo Transport Services in an Oracle RAC Database Environment
- 4.4.8 Transport Lag
- 4.5 Managing Redo Transport Services for Recovery Appliance
- 4.6 Managing Log Apply Services
-
4.7
Managing Data Protection Modes
-
4.7.1
Setting the Protection Mode for Your Configuration
- 4.7.1.1 Setting the Protection Mode Task 1: Determine Which Data Protection Mode You Want to Use
- 4.7.1.2 Setting the Protection Mode Task 2: Set up standby redo log files
- 4.7.1.3 Setting the Protection Mode Task 3: Set the redo transport mode
- 4.7.1.4 Setting the Protection Mode Task 4: Using DGMGRL or Cloud Control
- 4.7.2 How the Protection Modes Influence Broker Operations
-
4.7.1
Setting the Protection Mode for Your Configuration
- 4.8 Managing Far Sync Instances
- 4.9 Managing Fast-Start Failover
- 4.10 Managing Database Conversions
- 4.11 Database Status
-
5
Switchover and Failover Operations
- 5.1 Overview of Switchover and Failover in a Broker Environment
- 5.2 Choosing a Target Standby Database
- 5.3 Switchover
-
5.4
Manual Failover
- 5.4.1 Complete and Immediate Manual Failovers
-
5.4.2
Performing a Manual Failover Operation
- 5.4.2.1 Performing a Manual Failover Task 1: Determine Which of the Available Standby Databases is the Best Target for the Failover
- 5.4.2.2 Performing a Manual Failover Task 2: Start the Failover
- 5.4.2.3 Performing a Manual Failover Task 3: Reset the Protection Mode
- 5.4.2.4 Performing a Manual Failover Task 4: Re-establish a Disaster-Recovery Configuration
- 5.4.2.5 How the Broker Performs a Complete Failover Operation
- 5.4.2.6 How the Broker Performs an Immediate Failover Operation
- 5.4.3 Reenabling Disabled Databases After a Role Change
-
5.5
Fast-Start Failover
- 5.5.1 Prerequisites for Enabling Fast-Start Failover
-
5.5.2
Enabling Fast-Start Failover
- 5.5.2.1 Enabling Fast-Start Failover Task 1: Determine Which Available Standby Databases Should Be Targets for the Failover
- 5.5.2.2 Enabling Fast-Start Failover Task 2: Specify Target Standby Databases with the FastStartFailoverTarget Configuration Property
- 5.5.2.3 Enabling Fast-Start Failover Task 3: Determine the Protection Mode You Want
- 5.5.2.4 Enabling Fast-Start Failover Task 4: Set the FastStartFailoverThreshold Configuration Property
- 5.5.2.5 Enabling Fast-Start Failover Task 5: Set Other Properties Related to Fast-Start Failover (Optional)
- 5.5.2.6 Enabling Fast-Start Failover Task 6: Enable Additional Fast-Start Failover Conditions (Optional)
- 5.5.2.7 Enabling Fast-Start Failover Task 7: Using DGMGRL or Cloud Control
- 5.5.2.8 Enabling Fast-Start Failover Task 8: Start the Observer
- 5.5.2.9 Enabling Fast-Start Failover Task 9: Verify the Fast-Start Failover Environment
- 5.5.2.10 When Fast-Start Failover Is Enabled and the Observer Is Running
- 5.5.2.11 Restrictions When Fast-Start Failover is Enabled
- 5.5.2.12 Configuring Fast-Start Failover in Observe-only Mode
- 5.5.2.13 Shutting Down the Primary Database When Fast-Start Failover Is Enabled
- 5.5.2.14 Performing Manual Role Changes When Fast-Start Failover Is Enabled
- 5.5.3 Directing a Fast-Start Failover From an Application
- 5.5.4 Viewing Fast-Start Failover Configuration Statistics and Status
- 5.5.5 Disabling Fast-Start Failover
- 5.5.6 Performance Considerations for Fast-Start Failover
-
5.5.7
Managing the Observer
- 5.5.7.1 Installing and Starting the Observer
- 5.5.7.2 Viewing Information About the Master Observer
- 5.5.7.3 Viewing Information About All Observers
- 5.5.7.4 What Happens if the Master Observer Fails?
- 5.5.7.5 Managing Observer's Connection to the Primary
- 5.5.7.6 Stopping the Observer
- 5.5.7.7 Moving the Observer to Another Computer
- 5.5.7.8 How the Observer Maintains Fast-Start Failover Configuration Information
- 5.5.7.9 Managing Observers for Multiple Configurations
- 5.5.7.10 Patching an Environment When the Observer Is Running and Fast-start Failover Is Enabled
- 5.5.8 Reinstating the Former Primary Database in the Broker Configuration
- 5.5.9 Shutting Down Databases In a Fast-Start Failover Environment
- 5.6 Database Client Considerations
-
6
Scenarios Using the DGMGRL Command-Line Interface
- 6.1 Prerequisites for Getting Started
-
6.2
Scenario 1: Creating a Configuration
- 6.2.1 Creating a Configuration Task 1: Invoke DGMGRL
- 6.2.2 Creating a Configuration Task 2: Connect to the Primary Database
- 6.2.3 Creating a Configuration Task 3: Clear Existing Remote Redo Transport Destinations on Standbys and Far Sync Instances To Be Added.
- 6.2.4 Creating a Configuration Task 4: Create the Broker Configuration
- 6.2.5 Creating a Configuration Task 5: Show the Configuration Information
- 6.2.6 Creating a Configuration Task 6: Add a Standby Database to the Configuration
- 6.3 Scenario 2: Setting Database Properties
- 6.4 Scenario 3: Enabling the Configuration and Databases
- 6.5 Scenario 4: Setting the Configuration Protection Mode
- 6.6 Scenario 5: Setting up Maximum Availability Mode with a Far Sync Instance
- 6.7 Scenario 6: Enabling Fast-Start Failover and Starting the Observer
- 6.8 Scenario 7: Enabling Fast-Start Failover When a Far Sync Instance Is In Use
- 6.9 Scenario 8: Performing Routine Management Tasks
-
6.10
Scenario 9: Performing a Switchover Operation
- 6.10.1 Using the SWITCHOVER Command Task 1: Check the Primary Database
- 6.10.2 Using the SWITCHOVER Command Task 2: Check the Standby Database That is the Target of the Switchover
- 6.10.3 Using the SWITCHOVER Command Task 3: Confirm That the Database Is Ready for a Role Change
- 6.10.4 Using the SWITCHOVER Command Task 4: Issue the Switchover Command
- 6.10.5 Using the SWITCHOVER Command Task 5: Show the Configuration
- 6.11 Scenario 10: Performing a Manual Failover Operation
- 6.12 Scenario 11: Reinstating a Failed Primary Database
- 6.13 Scenario 12: Converting a Physical Standby to a Snapshot Standby
-
6.14
Scenario 13: Monitoring a Data Guard Configuration
- 6.14.1 Monitoring a Configuration Task 1: Check the Configuration Status
- 6.14.2 Monitoring a Configuration Task 2: Check the Database Status
- 6.14.3 Monitoring a Configuration Task 3: Check the LogXptStatus Monitorable Property
- 6.14.4 Monitoring a Configuration Task 4: Check the InconsistentLogXptProps Monitorable Property
- 6.15 Scenario 14: Adding a Recovery Appliance to a Broker Configuration
- 6.16 Scenario 15: Exporting and Importing a Broker Configuration File
- 6.17 Scenario 16: Using the Observe-only Mode for Fast-Start Failover
-
7
Oracle Data Guard Command-Line Interface Reference
- 7.1 Starting the Data Guard Command-Line Interface
- 7.2 Exiting the Data Guard Command-Line Interface
- 7.3 @ (at sign) Command
- 7.4 / (slash) Command
- 7.5 ADD DATABASE
- 7.6 ADD FAR_SYNC
- 7.7 ADD RECOVERY_APPLIANCE
- 7.8 CONNECT
- 7.9 CONVERT DATABASE
- 7.10 CREATE CONFIGURATION
- 7.11 DISABLE CONFIGURATION
- 7.12 DISABLE DATABASE
- 7.13 DISABLE FAR_SYNC
- 7.14 DISABLE FAST_START FAILOVER
- 7.15 DISABLE FAST_START FAILOVER CONDITION
- 7.16 DISABLE RECOVERY_APPLIANCE
- 7.17 EDIT CONFIGURATION (Property)
- 7.18 EDIT CONFIGURATION (Protection Mode)
- 7.19 EDIT CONFIGURATION (RENAME)
- 7.20 EDIT CONFIGURATION RESET (Property)
- 7.21 EDIT DATABASE (Property)
- 7.22 EDIT DATABASE (Parameter)
- 7.23 EDIT DATABASE (Rename)
- 7.24 EDIT DATABASE (State)
- 7.25 EDIT DATABASE RESET (Property)
- 7.26 EDIT DATABASE RESET (Parameter)
- 7.27 EDIT FAR_SYNC
- 7.28 EDIT FAR_SYNC RESET (Property)
- 7.29 EDIT FAR_SYNC RESET (Parameter)
- 7.30 EDIT RECOVERY_APPLIANCE (Property)
- 7.31 EDIT RECOVERY_APPLIANCE (Parameter)
- 7.32 EDIT RECOVERY_APPLIANCE (Rename)
- 7.33 EDIT RECOVERY_APPLIANCE RESET (Property)
- 7.34 EDIT RECOVERY_APPLIANCE RESET (Parameter)
- 7.35 ENABLE CONFIGURATION
- 7.36 ENABLE DATABASE
- 7.37 ENABLE FAR_SYNC
- 7.38 ENABLE FAST_START FAILOVER
- 7.39 ENABLE FAST_START FAILOVER CONDITION
- 7.40 ENABLE RECOVERY_APPLIANCE
- 7.41 EXIT
- 7.42 EXPORT CONFIGURATION
- 7.43 FAILOVER
- 7.44 HELP
- 7.45 HOST or ! (exclamation point)
- 7.46 IMPORT CONFIGURATION
- 7.47 MIGRATE PLUGGABLE DATABASE
- 7.48 QUIT
- 7.49 REINSTATE DATABASE
- 7.50 REMOVE CONFIGURATION
- 7.51 REMOVE DATABASE
- 7.52 REMOVE FAR_SYNC
- 7.53 REMOVE INSTANCE
- 7.54 REMOVE RECOVERY_APPLIANCE
- 7.55 SET ECHO
- 7.56 SET FAST_START FAILOVER TARGET
- 7.57 SET MASTEROBSERVER TO
- 7.58 SET MASTEROBSERVERHOSTS
- 7.59 SET ObserverConfigFile
- 7.60 SET TIME
- 7.61 SET TRACE_LEVEL
- 7.62 SHOW ALL
- 7.63 SHOW CONFIGURATION
- 7.64 SHOW CONFIGURATION WHEN PRIMARY IS
- 7.65 SHOW DATABASE
- 7.66 SHOW FAR_SYNC
- 7.67 SHOW FAST_START FAILOVER
- 7.68 SHOW INSTANCE
- 7.69 SHOW OBSERVER
- 7.70 SHOW ObserverConfigFile
- 7.71 SHOW OBSERVERS
- 7.72 SHOW RECOVERY_APPLIANCE
- 7.73 SHUTDOWN
- 7.74 SPOOL
- 7.75 SQL
- 7.76 START OBSERVER
- 7.77 START OBSERVER IN BACKGROUND
- 7.78 START OBSERVING
- 7.79 STARTUP
- 7.80 STOP OBSERVER
- 7.81 STOP OBSERVING
- 7.82 SWITCHOVER
- 7.83 VALIDATE DATABASE
- 7.84 VALIDATE DATABASE DATAFILE
- 7.85 VALIDATE DATABASE SPFILE
- 7.86 VALIDATE FAR_SYNC
- 7.87 VALIDATE NETWORK CONFIGURATION
- 7.88 VALIDATE STATIC CONNECT IDENTIFIER
-
8
Oracle Data Guard Broker Properties
-
8.1
Configuration Properties
- 8.1.1 BystandersFollowRoleChange
- 8.1.2 CommunicationTimeout
- 8.1.3 ConfigurationWideServiceName
- 8.1.4 ExternalDestination1
- 8.1.5 ExternalDestination2
- 8.1.6 FastStartFailoverAutoReinstate
- 8.1.7 FastStartFailoverLagLimit
- 8.1.8 FastStartFailoverPmyShutdown
- 8.1.9 FastStartFailoverThreshold
- 8.1.10 ObserverOverride
- 8.1.11 ObserverReconnect
- 8.1.12 OperationTimeout
- 8.1.13 PreferredObserverHosts
- 8.1.14 PrimaryLostWriteAction
- 8.1.15 TraceLevel
-
8.2
Monitorable (Read-Only) Properties
- 8.2.1 InconsistentLogXptProps (Inconsistent Redo Transport Properties)
- 8.2.2 InconsistentProperties (Inconsistent Properties)
- 8.2.3 LogXptStatus (Redo Transport Status)
- 8.2.4 LsbyFailedTxnInfo (Logical Standby Failed Transaction Information)
- 8.2.5 LsbyParameters (Logical Standby Parameters)
- 8.2.6 RecvQEntries (Receive Queue Entries)
- 8.2.7 SendQEntries (Send Queue Entries)
- 8.2.8 TopWaitEvents
-
8.3
Configurable Properties
- 8.3.1 AlternateLocation
- 8.3.2 ArchiveLocation
- 8.3.3 ApplyInstances
- 8.3.4 ApplyInstanceTimeout
- 8.3.5 ApplyLagThreshold
- 8.3.6 ApplyParallel
- 8.3.7 ArchiveLagTarget
- 8.3.8 Binding
- 8.3.9 DataGuardSyncLatency
- 8.3.10 DbFileNameConvert
- 8.3.11 DelayMins
- 8.3.12 DGConnectIdentifier
- 8.3.13 Encryption
- 8.3.14 FastStartFailoverTarget
- 8.3.15 InstanceName
- 8.3.16 LogArchiveFormat
- 8.3.17 LogArchiveMaxProcesses
- 8.3.18 LogArchiveMinSucceedDest
- 8.3.19 LogArchiveTrace
- 8.3.20 LogFileNameConvert
- 8.3.21 LogShipping
- 8.3.22 LogXptMode
- 8.3.23 LsbyMaxEventsRecorded
- 8.3.24 LsbyMaxServers
- 8.3.25 LsbyMaxSga
- 8.3.26 LsbyPreserveCommitOrder
- 8.3.27 LsbyRecordAppliedDdl
- 8.3.28 LsbyRecordSkipDdl
- 8.3.29 LsbyRecordSkipErrors
- 8.3.30 MaxFailure
- 8.3.31 NetTimeout
- 8.3.32 ObserverConnectIdentifier
- 8.3.33 PreferredApplyInstance
- 8.3.34 PreferredObserverHosts
- 8.3.35 RedoCompression
- 8.3.36 RedoRoutes
- 8.3.37 ReopenSecs
- 8.3.38 StandbyAlternateLocation
- 8.3.39 StandbyArchiveLocation
- 8.3.40 StandbyFileManagement
- 8.3.41 StaticConnectIdentifier
- 8.3.42 TransportDisconnectedThreshold
- 8.3.43 TransportLagThreshold
-
8.1
Configuration Properties
-
9
Troubleshooting Oracle Data Guard
- 9.1 Sources of Diagnostic Information
-
9.2
General Problems and Solutions
- 9.2.1 ORA-16596: database not part of the Oracle Data Guard broker configuration
- 9.2.2 Redo Accumulating on the Primary Is Not Sent to Some Standby Databases
- 9.2.3 Many Log Files Are Received on a Standby Database But Not Applied
- 9.2.4 The Request Timed Out or Cloud Control Performance Is Sluggish
- 9.2.5 The Primary Database is Flashed Back
- 9.2.6 Standby Fails to Automatically Start Up Due to Unknown Service (ORA-12514)
- 9.3 Troubleshooting Problems During a Switchover Operation
- 9.4 Troubleshooting Problems During a Failover Operation
- 9.5 Troubleshooting Problems with the Observer
- A Oracle Data Guard Broker Upgrading and Downgrading
- Glossary
- Index