Post is slow when there are lots of Out of Band (OOB) messages sent to target. The key is the transaction id. The code loops through the entire cache looking for an element that has the same transaction id.number of full rollbacks. See in this part of theopo log:
opo 2009-10-13 11:22:51.644654 2700030 1 RrbResolve: 62
opo 2009-10-13 11:22:51.753773 2700030 1 Transaction 86(46).9660388-3(311051271), full rollback complete, 2 messages skipped
It looks like it is taking about a tenth of a second to do this search (the log message â??full rollback complete)
We did not optimize for large number of full rollback when we implemented the skip full rollback logic. The out-of-band full rollback records are added to a C++ container.The code loops through the entire cache looking for an element that has the same transaction id.number of full rollbacksThe code loops through the entire cache looking for an element that has the same transaction id.number of full rollbacks.
Workaround:
sp_ctrl >set param SP_OCT_TARGET_COMPATIBILITY 6.0
sp_ctrl > stop post
sp_ctrl > start post
Starting with SharePlex 9, the parameter SP_OCT_TARGET_COMPATIBILITY has been deprecated and is replaced by a new parameter SP_SYS_ TARGET_COMPATIBILITY. Here is the description of the new parameter from the SharePlex Reference Guide:
SP_SYS_TARGET_COMPATIBILITY
This parameter enables you to preserve compatibility between different versions of SharePlex to allow for
smoother migrations and upgrades. As SharePlex continues to evolve to satisfy new user requirements,
features or functionality added in a new version are not always compatible with previous versions. This
parameter enables replication from a higher version of SharePlex on the source system to a lower version on a
target system.
By default, this parameter is set to the version of the installed SharePlex software.
l When replicating from a higher version on a source system to a lower version of SharePlex on a target,
set this parameter to a value that most closely matches the version of SharePlex on the target. For
example, if SharePlex is version 8.6.3 on the source and 8.6.2 on the target, set this parameter to 8.6.2.
l When replicating between identical versions, leave this parameter set to the default on both systems.
Default: The version of the installed SharePlex software
Range of valid values: SharePlex release versions from 6.0.0 to the current version, up to three numbers long
(for example 8.6.3).
Takes effect: when Capture is restarted
This issue will be fixed in Shareplex 7.5
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center