Question 20:
Examine the Data Guard configuration: DGMGRL> show configuration: Configuration-Animals - Protection Mode: MaxAvailability Databases: Sheep- Primary database - Warning: ORA-16817: unsynchronized fast-start failover configuration Dogs(*) Physical standby database (disabled) ORA- 16661: the standby database needs to be reinstated Fast-Start Failover: ENABLED - Configuration Status: WARNING - And the fast-start failover configuration: DGMGRL> show fast_start failover; Fast-Start Failover: ENABLED - Threshold : 30 seconds - Target: dogs - Observer : 017.example.com - Lag Limit: 30 seconds (not in use) Shutdown Primary: TRUE - Auto-reinstate: TRUE - Observer Reconnect: 10 seconds - Observer Override: FALSE - Configurable Failover Conditions Health Conditions: Corrupted ControlfileYES - Corrupted DictionaryYES - Inaccessible Logfile NO - Stuck ArchiverNO - Datafile OfflineYES - Oracle error Conditions: ORA-01578: ORACLE data block corrupted (file # %s, block # %s) And finally the reason for the fail over: SQL> select last_failover_reason from v$fs_failover_stats; LAST_FAILOVER_REASON - ORA-01578: ORACLE data block corrupted (file # %s, block # %s) Identify the task, or sequence of tasks, to bring the configuration into the SUCCESS state.
Answer options:
A. Bring Dogs to the NOMOUNT state and let the broker reinstate Dogs automatically. B. MOUNT DOGS and issue "reinstate database dogs:" at the DGMGRL prompt while connected to Dogs. C. MOUNT DOGS and issue "reinstate database dogs:" at the DGMGRL prompt while connected to Sheep. D. Open Dogs and let the broker reinstate Dogs automatically.