Examine the Data Guard configuration:
DGMGRL> show configuration verbose;
Configuration - Animals
Protection Mode: MaxPerformance
Databases:
cats - Primary database
dogs - (*) Physical standby database
sheep - Physical standby database
(*) Fast-Start Failover target
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
TraceLevel = 'USER'
FastStartFailoverLagLimit = '30'
CommunicationTimeout= '180'
ObserverReconnect= '10'
FastStartFailoverAutoReinstate= 'FALSE'
FastStartFailoverPmyShutdown= 'TRUE'
BystandersFollowRoleChange= 'none'
ObserverOverride = 'FALSE'
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: dogs
Observer: ol5.example.com
Lag Limit: 30 seconds
Shutdown Primary:TRUE
Auto-reinstate: FALSE
Observer Reconnect: 10 seconds
Observer Override: TRUE
Configuration Status:
SUCCESS
Which two are true? (Choose two.)
B: If fast-start failover is enabled, the observer will automatically reinstate the standby databases after failover has completed.
E: FastStartFailoverAutoReinstate= 'FALSE' means that the former primary database will not be reinstated automatically after a failover,
Note: The FastStartFailoverAutoReinstate configuration property causes the former primary database to be automatically reinstated if a fast-start failover was initiated because the primary database was either isolated or had crashed. To prevent automatic reinstatement of the former primary database in these cases, set this configuration property to FALSE.
The observer is the third party in an otherwise typical primary/standby Data Guard configuration. Only the observer can initiate FSFO failover. It's secondary job is to automatically reinstate a failed primary as a standby if that feature is enabled (the default).
Currently there are no comments in this discussion, be the first to comment!