Examine the Data Guard configuration:
DGMGRL > show configuration;
Configuration-Animals
Protection Mode: MaxAvailabilityDatabases:
dogs- Primary database
dogsfsl –Far Sync
sheep- Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
An attempt to enable fast-start failover raises an eror:
DGMGRL> enable fast_start failover;
Error: ORA-16693: requirements not met for enabling fast-start failover
Failed.
Identify two possible reasons for this error.
A.
The FastStartFailoverTarget property is not set on Sheep.
B.
The FastStartFailoverTarget property is not set on Dogs.
C.
The FastStartFailoverTarget property is not set on DogsFS1.
D.
The LogXptMode property is set to ASYNC on Dogs.
E.
The RedoRoutes property is not set on Dogs.
F.
The RedoRoutes property is not set on DogsFS1.
Explanation:
D: Ensure that the LogXptMode property for both the primary database and the Fast-Start Failover target
standby database are SYNC.
A: If more than one physical or logical standby database exists, in this case it is the sheep database, you must
specify the FastStartFailoverTarget value explicitly, prior to enabling fast-start failover. The indicated target is
verified when fast-start failover is enabled.
Note: DGMGRL> enable fast_start failover;
Error: ORA-16651: requirements not met for enabling fast-start failover
Failed.
SOLUTION
1) Check whether the flashback database is enabled on primary & standby database
Select flashback_on from gv$database;
2) Check whether you have set the FastStartFailoverTarget parameter.
https://docs.oracle.com/cd/E11882_01/server.112/e40771/dbpropref.htm#DGBKR862
http://psoug.org/oraerror/ORA-16651.htm
Correct Ans: D, E
You don’t have to set FastStartFailoverTarget if only one physical standby in the configuration even though it uses Far-Sync instance. When you enable fast_start failover it automatically assigns the physical standby as the failover target. In this case correcting LogXptMode and RedoRoutes properties for the Primary will take care of the issue.
I have tested this
so why we can say that The RedoRoutes property is not set on DogsFS1. is incorrect?
Based on the below we can also said that:A,B are correct
6.8 Scenario 7: Enabling Fast-Start Failover When a Far Sync Instance Is In Use
Fast-start failover can be enabled in maximum availability mode when the fast-start failover target is a logical or physical standby database that receives redo data from a far sync instance.
To enable fast-start failover when a far sync instance is used to ship redo data to the standby database, the FastStartFailoverTarget property must first be set on both the primary and target standby database, as follows:
DGMGRL> EDIT DATABASE ‘North_Sales’ SET PROPERTY FastStartFailoverTarget=’South_Sales’;
DGMGRL> EDIT DATABASE ‘South_Sales’ SET PROPERTY FastStartFailoverTarget=’North_Sales’;
Then, fast-start failover can be enabled, as follows:
DGMGRL> ENABLE FAST_START FAILOVER;
Note that the far sync instance database is not specified as the fast-start failover target for either North_Sales or South_Sales.
https://docs.oracle.com/database/121/DGBKR/cli.htm#DGBKR-GUID-B56AA048-02D8-49F4-819C-0B7064E37826
DE
Any one suggest another solution for this question instead of A,B as i prove above?
If there is only one standby database, you don’t need to define a FAilover Target.
D and E are correct Answers
D – If you are using MAX AVAILABILITY, LogXptMode should be set to SYNC
E- RedoRoutes property has to be defined
D,E