Shareplex version 6.x or lower only allows one object per queue to be disabled for posting by configuring the parameter SP_OPO_DISABLE_OBJECT_NUM whereas version 7.x or up does not have this restriction. The resolution section describes how to achieve the disabling of posting of multiple objects in pre Shareplex 7.x and up.
A. For Shareplex versions 6.x or lower:
Since poster only allows skipping one object per queue in Shareplex 6.x or lower; the only way to disable multiple objects is if they are in separate queues.
The procedure for disabling a single object is as follows:
Obtain the Oracle object_id of the object from the SOURCE system, then on the target configure SP_OPO_DISABLE_OBJECT_NUM as:
sp_ctrl> set param SP_OPO_DISABLE_OBJECT_NUM <object_id>
sp_ctrl> stop post
sp_ctrl> start post
To resume posting to this object:
sp_ctrl> reset param SP_OPO_DISABLE_OBJECT_NUM
sp_ctrl> stop post
sp_ctrl> start post
This procedure can be extended to disable posting on more than one table at any given time, so long as the tables are configured to travel through different named Post queues.
The syntax to be used is:
sp_ctrl> set param SP_OPO_DISABLE_OBJECT_NUM queue <post_queue_name> <object_id_from_source>
To resume posting to this object:
sp_ctrl> reset param SP_OPO_DISABLE_OBJECT_NUM queue <post_queue_name>
The only constraint is that only one object per named Post queue can be disabled for posting at any given time.
B. For Shareplex versions 7.x or up:
Starting with Shareplex 7.0.2 and up, it is possible to disable posting on multiple objects using the following syntax (also described in Release Notes for 7.0.2 and in Reference Guide for all Shareplex versions starting with 7.0.2)
If not using quotes, there must be no spaces in between the object ids, e.g.:
sp_ctrl>set param SP_OPO_DISABLE_OBJECT_NUM object_id1, object_id2, object_id2
sp_ctrl>stop post
sp_ctrl>start post
If using quotes, spaces must be used e.g.:
set param SP_OPO_DISABLE_OBJECT_NUM "object_id1, object_id2, object_id2"
sp_ctrl>stop post
sp_ctrl>start post
For option B, it is only possible to disable objects at global level and not at the individual Post queue level. So, regardless of these objects routing through the same named Post queue or different ones, only the parameter must be specified without specifying the named Post queue (in effect setting it at global level).
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center