Which two are true about this change?

You are required to change the Data Guard Configuration protection mode from MAXPERFORMANCE to MAXAVAJLABILITY using Enterprise Manager Cloud Control
Which two are true about this change?

You are required to change the Data Guard Configuration protection mode from MAXPERFORMANCE to MAXAVAJLABILITY using Enterprise Manager Cloud Control
Which two are true about this change?

A.
If the primary database cannot write its redo to at least one synchronized standby database, then the protection level remains unchanged.

B.
The primary database instance will remain up and running, if it cannot write redo to at least one synchronized standby database.

C.
Transactions will not commit until all redo data needed to recover those transactions are written to the online redo log, and to the standby redo log on at least one synchronizes standby database.

D.
Fast start failover can be enabled when making the chance.

E.
Realtime apply will be automatically turned on.



Leave a Reply 5

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


JFK

JFK

B:
If the primary does not receive acknowledgement from at least one synchronized standby, then it operates as if it were in maximum performance mode to preserve primary database availability until it is again able to write its redo stream to a synchronized standby database.
C:
Under normal operations, transactions do not commit until all redo data needed to recover those transactions has been written to the online redo log
References:
http://docs.oracle.com/database/121/SBYDB/protection.htm#SBYDB02000

WGCM

WGCM

A – This is wrong! When in MAXAVAILABILITY and the primary database cannot write its redo to at least one synchronized standby database, their mode changes to MAXPERFORMANCE, until this problem is resolved.
B – This is true! Unlike maximum protection mode, the primary database does not shut down if a fault prevents it from writing its redo stream to a remote standby redo log
C – This is true! As with maximum protection mode, a transaction does not commit until the redo needed to recover that transaction is written to the local online redo log and to at least one remote standby redo log,
D – This is not true! You can have a fast start failover in either: MAXAVAILABILITY or MAXPERFORMANCE, so you dont need to change this only why you change the protection mode.
E – This is false! This is the default in either mode, MAXAVAILABILITY e MAXPERFORMANCE, probably, this mode is on and will stay on.

Any correction / question?

JorgeZG

JorgeZG

I think is
B: It’s correct, the primary will remain up. It’s MAX Availability

C: It’s incorrect, If the primary cannot write to the standby redo log on at least one synchronizes standby, The Commit will finish normally.

D: Correct – Can You enable Fast-Start Failover with Max Availability? YES