Which three are prerequisites for enabling Fast-Start F…

Which three are prerequisites for enabling Fast-Start Failover?

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.

Explanation:
B: You enable the Flashback Mode both on the primary database and on the standby database.
D: In Maximum Availability mode, Fast-Start Failover (FSFO) guarantees that no transaction that has received
a commit acknowledgment will be lost during a failover.Oracle Database 11g FSFO adds support for Maximum Performance mode (async redo transfer), providing
the flexibility to trade durability for performance.
F: The Dataguard Broker Observer (Observer) is used when fast start failover is required. Fast start failover is
simply an automatic failover to the standby database
Incorrect Answers:
C: You enable the Flashback Mode both on the primary database and on the standby database.

http://dbasoumya.blogspot.se/2015/07/fast-start-failoverfsfo-in-oracle-11g.html
http://www.oracle.com/technetwork/articles/smiley-fsfo-084973.html

Show Hint

Leave a Reply 2

Your email address will not be published. Required fields are marked *

Chunn

Chunn

B,D,F

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.
– 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.
– Install the DGMGRL command-line interface on the observer computer
– 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.

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

Reply