Overall commit latency is increased by the round-trip network latency. Maximum Availability mode uses synchronous redo transfer and FSFO imposes the additional requirement that the redo is recorded in the standby redo log (SRL) of the target standby (AFFIRM option of log_archive_dest_ n). The price for this guarantee is increased commit latency ( log file sync waits). In Maximum Availability mode, FSFO guarantees that no transaction that has received a commit acknowledgment will be lost during a failover. Maximum Availability Mode (Oracle Database 10 g Rel 2 and later) The following paragraphs describe the supported availability modes. The standby can be physical or logical and there can be multiple standbys, but only one of the standbys can be the failover target at any given time. The foundation of FSFO is Data Guard - a primary and at least one standby. FSFO builds upon a number of other Oracle technologies and features such as Data Guard, Flashback Database, and Data Guard Broker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |