Question 4
Examine the Data Guard configuration:
DGMGRL> show configuration;
Configuration –Animals
Protection Mode: MaxAvailability
Databases:
dogs- Primary database
cats- Snapshot standby database
sheep- Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
ORA-01034: ORACLE not available
ORA-16625: cannot reach database “dogs”
DGM-17017: unable to determine configuration status
You wish to perform a failover to Sheep.
Which command, or sequence of commands, should you issue to the broker before executing “failover to sheep”, using the broker?
DGMGRL> convert database cats to physical standby;
DGMGRL> convert database sheep to physical standby;
DGMGRL> convert database sheep to physical standby;
DGMGRL> convert database cats to physical standby;
DGMGRL>edit configuration set protection mode as maxperformance;
DGMGRL> convert database sheep to physical standby;
None, because you can directly failover to a Snapshot Standby Database.
Correct answer: C
Explanation:
Note: Oracle Error: ORA-16625Error Description:Cannot reach the database Error Cause:The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database. Action:Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database. References: http://psoug.org/oraerror/ORA-16625.htm
Note: Oracle Error: ORA-16625
Error Description:
Cannot reach the database
Error Cause:
The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database.
Action:
Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database.
References: http://psoug.org/oraerror/ORA-16625.htm