Oracle Data Guard - Step-by-Step - Broadcast Cascade and Far Sync Standby Architectures

Hello viewers, welcome to the Step-by-Step Oracle Data Guard series and in this Part-9, we are going to discuss about Broadcast, Cascade and Far Sync Standby architecture.
BROADCAST: This is the simplest configuration of the standby that is implemented by default when the primary sends the redo data to one or multiple standby destinations based on the parameter log_archive_dest_n settings in the primary. In this architecture, the redo data is paralelly sent to different destinations, so it increases the load on the primary database as well as the network traffic. This configuration minimizes the risk of data loss and ensure the fastest possible role transition. So far in this series we have implemented the broadcast architecture only.
CASCADE: In this configuration, a standby database receives its redo data from another standby database, instead of receiving it directly from the primary database. This is mostly implemented when the standbys are configured over a WAN. This configuration reduces the overhead associated with performing redo transport from a primary database and reduce the traffic in the network. However, this may increase the role transition time with a risk of data loss.
FAR SYNC: Data Guard far sync instance is a remote Oracle Data Guard destination that accepts redo from the primary database and then ships that redo to other standby DBs of the Data Guard configuration. It manages a control file, receives redo into standby redo logs (SRLs), and archives those SRLs to local archived destination and sends the redo to the other standbys but other than that it is not similar with a physical standbys.
Oracle data guard is an indispensable part of oracle's high availability solutions. In a real world scenario the Primary and Physical standby databases reside on geographically different locations or different data centers to make sure that even if one region goes completely down, your database is still available and intact. In this tutorial and the series I am covering various topics on oracle Data Guard, like architecture, implementation, administration, management, monitoring etc. Each of these topics may need one or more tutorials to cover it completely. I assume you are already an oracle dba or familiar with at least the basics of oracle database architecture. I will keep everything simple so there won't be any difficulty in understanding the concepts even if you are a beginner.
I am using a virtual environment for demonstration purpose.
Commands and SQLs used:
docs.google.com/document/d/1Y...
Previous Parts in this Series:
Part-1: Create a Physical Standby using OEM
• Oracle DataGuard - Ste...
Part-2: DG Architecture, Configuration, Broker, Switchover, Failover
• Oracle DataGuard - Ste...
Part-3: Administration, Management, Monitoring using OEM
• Oracle DataGuard - Ste...
Part-4: Standby Log Gap, Detect, Alert and Resolve
• Oracle Data Guard - St...
Part-5: Primary Database Protection Modes
• Oracle Data Guard - St...
Part-6: Different Standby Database Modes
• Oracle Data Guard - St...
Part-7: Configuring RMAN Backups in Standby
• Oracle Data Guard - St...
Part-8: Configuring Data Guard Observer and Auto-Failover
• Oracle Data Guard - St...
My other series on RUclips:
===========================
Mastering OEM 13c (Full Series):
• Mastering OEM 13c
Setting up OEM Notification, Monitoring and Alerting:
• OEM Monitoring and Ale...
Oracle VirtualBox Virtual Machines:
• VBox Virtual Machines