RedoRoutes
The RedoRoutes property lets you override the default behavior by which 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.
Note:
A member whoseMaxFailure property is set to zero cannot be part
of a RedoRoutes group.
| Category | Description |
|---|---|
|
Datatype |
String |
|
Valid values |
A character string that contains one or more redo routing rules, each contained within a pair of parentheses: (redo_routing_rule_1) [(redo_routing_rule_n)] See "Redo Routing Rules" for more information about redo routing rules. |
|
Broker default |
Null |
|
Imported? |
No |
|
Parameter class |
Not applicable |
|
Role |
Primary, standby, far sync instance |
|
Standby type |
Physical standby and far sync instance |
|
Corresponds to |
|
|
Scope |
Database, far sync instance |
|
Cloud Control Name |
RedoRoutes |