LogShipping
The broker uses the value of the LogShipping property when the primary database is in the TRANSPORT-ON state or when the physical standby or far sync instance forwards redo data to another member.
The other member can be a physical, logical, or snapshot standby, or a far sync instance.
-
If the primary database is in the
TRANSPORT-ONstate and the value of theLogShippingproperty isON, then redo transport services are enabled to send redo data to the particular configuration member. If theLogShippingproperty isOFF, then redo transport services are disabled to that member. -
If a configuration member that forwards redo data has its
LogShippingproperty set toONand the member to which it sends redo data also has itsLogShippingproperty set toON, then redo transport services are enabled from the member sending redo data to the member that is to receive redo data.If a member that forwards redo data has its
LogShippingproperty set toONbut the member to which it sends redo data has itsLogShippingproperty set toOFF, then redo transport services are disabled from the member sending redo data to the member that is to receive redo data.
| Category | Description |
|---|---|
|
Datatype |
String |
|
Valid values |
|
|
Broker default |
|
|
Imported? |
No |
|
Parameter class |
Dynamic |
|
Role |
Standby database, Recovery Appliance, far sync instanceFoot 1 |
|
Standby type |
Physical, logical, or snapshot standby, far sync instance, Recovery Appliance |
|
Corresponds to |
|
|
Scope |
Database, Recovery Appliance |
|
Cloud Control name |
|
Footnote 1
Although this property is set for a standby database or far sync instance, it is indirectly related to the redo transport services for the database or far sync instance that is sending redo data. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the database or far sync instance that is sending redo data.