The cascade standby database concept was introduced from Oracle 9i Release 2 onwards. In the latest versions and releases there are many changes in the cascade standby databases. The cascade standby database concept was introduced to reduce the load on your primary database and to transmit redo data from the primary to all standby databases, and the network bandwidth needs to be large enough to handle the load. If it is a huge OLTP then it will be more problematic to handle. The cascade standby databases are shown in the following diagram:
The limitations with a cascade standby database are as follows:
- Data cannot be transmitted to other standby databases from a logical standby or a snapshot standby database.
- Data Guard broker is not supported in a cascade standby database environment.
- Cascading is not supported in RAC on versions prior to 11.2.0.2.
- If you are using synchronous redo transport, they cannot cascade redo data in a Maximum Protection mode.
- If the primary database is transmitting redo to the standby redo logfiles and writing into standby redo logfiles once SRL is full and archived, then the respective archive sequence will be transmitted and applied to the cascade standby database(s). This will delay redo to the cascade database.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.