Maximum Protection Mode
1. No data loss
2. Redo has to be written to both Primary redo logs and standby redo logs (of atleast one standby database) before transaction commits
3. Primary database shuts down if redo stream is prevented to write at standby redo logs of atleast one standby database
4. Configure standby redo logs on at least one standby database
5. Attribute to use in log_archive_dest_n : LGWR, SYNC and AFFIRM for at least one standby DB
Maximum Availability Mode
1. Redo has to be written to both Primary redo logs and standby redo logs (of atleast one standby database) before transaction commits.
2. If redo stream is prevented to write at standby redo logs of at least one standby database then Primary database does not shuts down unlike Maximum protection mode, instead primary database operates in Maximum Performance mode.
3. Primary database automatically resumes to operate in maximum availability mode once all gaps are resolved.
4. Configure standby redo logs on at least one standby database
5. Attribute to use in log_archive_dest_n : LGWR, SYNC and AFFIRM for at least one standby DB
Maximum Performance Mode
1. Default mode
2. Asynchronous redo data is written to at least one standby database
3. Attributes on log_archive_dest_n to set either LGWR and ASYNC or ARCH for standby DB destination
4. Minimum Requirements for Data Protection Modes
5. Maximum Protection Maximum Availability Maximum Performance
6. Redo Archival process LGWR LGWR LGWR or ARCH
7. Network Transmission Mode SYNC SYNC ASYNC when using LGWR process. SYNC when using ARCH process
8. Disk write option AFFIRM AFFIRM AFFIRM or NOAFFIRM
9. Standby Redo log required YES YES NO, but its recommended
