At times there may be a problematic object in replication on SOURCE database causing issues either on source and/or target.Is there is a way to force Shareplex processes (Capture and/or Read) to ignore this object for a limited time while stillprocessing transactions on other objects.
Currently there is no such capability in Shareplex to achieve this on source. The only workarounds that can be tried are:
Take the object out of replication. This will ensure that no future transactions pertaining to this object are gathered in Capture and other queues downstream. The current messages in the Shareplex queues for this object will still need to be processed.
On target ignore posting on this object. This is done by configuring the Shareplex Post parameter SP_OPO_DISABLE_OBJECT_NUM. This may require the object to be resyncd at a later time. See Solution # SOL16835 for more information about SP_OPO_DISABLE_OBJECT_NUM.
It is possible to let Capture ignore a particular transaction on source by running the procedure SHAREPLEX_IGNORE_TRANS prior to executing the transaction. See Shareplex Administrators Guide Chapter titled Shareplex Utilities section titled Preventing DML transactions from replicating with create_ignore.sql. However, the limitation here is that the ignoring is done on a transaction specific basis and not table wise.
Also refer to Solution # SOL55971 that delves on a new feature whereby Capture can be directed to ignore activities conducted by a certain user in the source database. This is done by configuring the Capture parameter SP_OCT_DENIED_USERID on source Shareplex. The new feature has its pros and cons that the solution describes. This feature is only available from Shareplex 7.0 and up.