Which three are prerequisites for enabling Fast-Start F…

Which three are prerequisites for enabling Fast-Start Failover?

A.
The Fast-Start Failover target standby database must receive REDO directly from the primary database

B.
Flashback Database must be enabled on both the primary database and the Fast-Start Failover target standby database.

C.
Flashback Database must be enabled only on the Fast-Start Failover target standby database.

D.
The configuration must be operating in either Maximum Performance or Maximum Availability mode

E.
The configuration must be operating in either Maximum Performance or Maximum Protection mode

F.
The Data Guard environment must be managed by the Data Guard Broker.

Show Hint

← Previous question

Next question →

Leave a Reply 13

PeraDetlic

A is also correct.

“The selected standby database that will be the fast-start failover target must receive redo directly from the primary database or from a far sync instance.”

Wim J

A is not correct, as stated by yourself: redo must come directly or Fast Sync. ‘Fast Sync’ is not mentionned in the answer.

Fran

A,B y D
Prerequisites for Enabling Fast-Start Failover

The following prerequisites must be met before the broker allows you to enable fast-start failover:

Ensure the broker configuration is operating in either maximum availability mode or maximum performance mode.

See Section 4.6.1 for information about configuring the protection mode, standby redo logs, and the redo transport mode.

The selected standby database that will be the fast-start failover target must receive redo directly from the primary database or from a far sync instance.

Ensure that the standby database you choose to be the target of fast-start failover has its LogXptMode property set to either SYNC or FASTSYNC if you wish to enable fast-start failover in maximum availability mode, or to ASYNC if you wish to enable fast-start failover in maximum performance mode. The current primary database must have its LogXptMode property set accordingly and must have standby redo logs configured. Alternatively, use the RedoRoutes property to configure the redo transport mode for the target standby and the database currently in the primary role.

To use a far sync instance with fast-start failover, the far sync instance transport mode must be set to either SYNC or FASTSYNC and the target standby database transport mode must be set to ASYNC.

Enable Flashback Database and set up a fast recovery area on both the primary database and the target standby database.

See Oracle Database Backup and Recovery User’s Guide.

Install the DGMGRL command-line interface on the observer computer as described in Section 2.1.

Configure the TNSNAMES.ORA file on the observer system so that the observer is able to connect to the primary database and to the pre-selected target standby database.

If you are not using Oracle Clusterware or Oracle Restart, then you must create static service names so that the observer can automatically restart a database as part of reinstatement. See Section 2.2, “Prerequisites” for more information.

JFK

I don’t agree with A (redo can be shipped from Far Sync)

JorgeZG

FSF has to be manage by dataguard broker. F is correct. Also B and D

Wim J

I ment Far Sync, typo above.

As stated in both documentations, you can have a far sync in a FSFO design. In that way, the FSFO targer does not receive its redo from the primary directly, but via a FS.

So A is incorrect

raul

i think,

Ensure the broker configuration is operating in either maximum availability mode or maximum performance mode.(D AND F)

Enable Flashback Database and set up a fast recovery area on both the primary database and the target standby database.(B)

NOT:
The selected standby database that will be the fast-start failover target must receive redo directly from the primary database or from a far sync instance.(NOT A).

JFK

Correct
B, D, F
Incorrect
A: (…)must receive redo directly from the primary database or from a far sync instance.
C: Enable Flashback Database and set up a fast recovery area on both the primary database and the target standby database.
E: Ensure the broker configuration is operating in either maximum availability mode or maximum performance mode.

Reference: https://docs.oracle.com/database/121/DGBKR/sofo.htm#DGBKR391

Nelz

BDF
https://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm#i1027843

Answer vary depending on version of 12c.
R1 FSFO supports only “Maximum Performance” or “Maximum Availability”
R2 FSFO support all 3 protection modes including “Maximum Protection”
12cR1 – https://docs.oracle.com/database/121/DGBKR/sofo.htm#GUID-995CED84-BEA1-4675-9C68-B37CB996924F
12cR2 – https://docs.oracle.com/database/122/DGBKR/using-data-guard-broker-to-manage-switchovers-failovers.htm#GUID-995CED84-BEA1-4675-9C68-B37CB996924F

incorrect A as standby can receive redo from “Far Sync” instance and dataguard in protection mode “Maximum Availability.
correct B and thus C incorrect
correct F as observer is managing everything using dataguard
for 12cR1 correct D and incorrect E
for 12cR2 coreect D and E