Oracle 12c Feature - Data Guard - Real-Time Cascade Standby Database!
Oracle 12c Feature - RedoRoutes:
Oracle Database 12c has brought over 500 new features, and many of them are related to Data Guard enhancements. Along with general optimization, now Data Guard Broker supports cascading standby databases. What's more, cascading destinations now receive redo logs in real time, without waiting for the archivelog switch.
The standby cascade works just like the standby database, but receives the redo logs from another standby database and not directly from the primary database. Therefore, the use of bandwidth in the primary database is improved.
Before 12c when the primary database redo was applied to the cascade standby database only after it was archived. This is why there is always a delay between the primary database and the cascade standby database.
To configure different variations of pending destinations, a new parameter called RedoRoutes was implemented. It defines the forwarding rules that return the transfer based on the status of the databases in the Data Guard.
RedoRoutes:
By default, a primary database sends the redo that it generates to every other redo transport destination in the configuration. You can use the RedoRoutes property to create a more complex redo transport topology, such as one in which a physical standby database or a far sync instance forwards redo received from the primary database to one or more destinations, or one in which the redo transport mode used for a given destination is dependent on which database is in the primary role.
The RedoRoutes property is set to a character string that contains one or more redo routing rules. Each rule contains one or more redo sources and one or more redo destinations. A redo routing rule becomes active when one of the redo sources in the rule is in the primary role. This results in redo from the primary database being sent to every redo destination in that rule.
More demonstrates will follow.......
Source: Oracle Documentation
Post a Comment: