In this article, we will see parameters that we can set while setting different protection modes and its impact on primary database and standby database.
We have already seen Protection Modes in Data Guard Protection modes in Oracle Dataguard
Now let us see Redo Transport Attributes required for setting different protection mode.
1. Maximum Availability
- AFFIRM OR NOAFFIRM
We can set AFFIRM and NOAFFIRM with Maximum Availability.
AFFIRM: When we set AFFIRM in redo transport parameter, redo transport destination acknowledges received redo data after it completes writing that redo to standby redo log file.
NOAFFIRM : When we specify NOAFFIRM redo transport destination acknowledges once it is received to standby database but it is yet no written to standby redo log file
- SYNC
We can set SYNC parameter while setting maximum availability protection mode.
SYNC: Specifies that redo data generated by a transaction must have been received at a destination that has this attribute before the transaction can commit; otherwise, the destination is deemed to have failed. In a configuration with multiple SYNC destinations, the redo must be processed as described here for every SYNC destination.
- DB_UNIQUE_NAME
2. Maximum Performance
- NOAFFIRM
- ASYNC
ASYNC: Specifies that redo data generated by a transaction need not have been received at a destination that has this attribute before the transaction can commit.
- DB_UNIQUE_NAME
3. Maximum Protection
To set Protection mode as Maximum Protection, we need to specify following attribute to redo transport service.
- AFFIRM
- SYNC
- DB_UNIQUE_NAME
Stay tuned for More articles on Oracle DataGuard
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Telegram Channel: https://t.me/helporacle
Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/
Joel Perez’s LinkedIn: Joel Perez’s Profile
LinkedIn Group: Oracle Cloud DBAAS
Facebook Page: OracleHelp
