how to disable one object in shareplex replication ?

I’ll  try in rubytw first. Please review my steps. thanks.

Only on target.

1. set param SP_OPO_DISABLE_OBJECT_NUM 45663

start post queue QWIP

2. check post queue if normal

3. stop post queue QWIP

4. set param SP_OPO_DISABLE_OBJECT_NUM 0

5. start post queue QWIP

6. repair that table

reset param SP_OPO_DEBUG_FLAG queue QOE

===

      RUBYTW post queue down(fixing)

    Riley, please provide the action plan which was done by Quest Support Anu, thanks

what quest did:

1. remove some problematic message using qview

   (command like: oseek, seekback, oread, rrls...etc)

2. enter ./sp_ctrl, set param eterto disable issued table

   sp_ctrl> set param SP_OPO_DISABLE_OBJECT_NUM 45663(this is object id from source)

  

3. start post and see if backlog is decreasing.

Becasue we did not really understand the meaning of those qview's commands. So maybe we should ask quest's help if issue happens again.

But as quest said that is horizontal partition bug, and has already provided one-off patch to us.

We will try to apply it on source shareplex to prevent this issue.  Thanks.

====

The procedure for disabling a single object is as follows:

SQL>select owner,object_id from dba_objects where object_name='RPT03_RESULT'

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

sp_ctrl> stop post

sp_ctrl> start post

To set this back to normal:

sp_ctrl> set param SP_OPO_DISABLE_OBJECT_NUM 0

sp_ctrl> stop post

sp_ctrl> start post