Oracle Database 12c: RAC and Grid Infrastructure Administration — Question 61
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 Controlfile YES -
Corrupted Dictionary YES -
Inaccessible Logfile NO -
Stuck Archiver NO -
Datafile Offline YES -
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.
Correct answer: C
Explanation
The correct answer is C because reinstating the standby database must be done while connected to the primary database (Sheep) to ensure proper communication and execution of the command. Options A and D are incorrect as they do not involve the necessary connection to Sheep, and option B is wrong as it attempts to reinstate while connected to the standby database, which is not permitted.