How to read release full rollback transactions on the source so that it does not go to the target
Rollbacks create a lot of latency in the post queues.
Resolution:
On source
sp_ctrl>stop capture
sp_ctrl>set param SP_OCT_TARGET_COMPATIBILITY 6.1
sp_ctrl>start capture
SP_OCT_TARGET_COMPATIBILITY
This parameter enables the use of two (2) enhancements in 6.1 that are not backwards
compatible. To take advantage of more efficient handling of large rollback operations
and support for the dbms_lob.erase operation, this setting must be set to 6.1 on
SharePlex Parameters both source system.
(The source and target systems must both have SharePlex 6.1
installed prior to setting this parameter.)
To maintain compatibility with previous releases and allow for smoother migrations and
upgrades this parameter should be left atas isdefault value, 6.0.
User configurable
Default: 6.0
Range of valid values: 6.0 or 6.1
Takes effect: when Capture is restarted