Starting with SharePlex 9 and up, parameter SP_DEQ_PARTIAL_REPAIR_CLR_OOS was introduced to deal with repair of a part of the table using “where” clause. The article delves on the working of this parameter including pros and cons.
When a table is repaired using a “where” clause, SharePlex works on the premise that the table can still have out of sync in other rows that are not accessed by the repair. So repair does not remove the out of sync entry for that table in the statusdb. This needs to be done manually using the command “clear status <statusid>”.
If it is known that the out of sync was only confined to some rows and a repair issued with “where” clause to fix those subset of rows.
In order to remove the out of sync entry in statusdb entry for such repair with where clause, SharePlex 9 and up offers the parameter SP_DEQ_PARTIAL_REPAIR_CLR_OOS. When “show sync” is subsequently issued, the table will not show up as out of sync.
The SP_DEQ_PARTIAL_REPAIR_CLR_OOS needs to be configured to a value of 1 on target sp_ctrl prior to running another repair with “where” clause:
sp_ctrl>set param SP_DEQ_PARTIAL_REPAIR_CLR_OOS 1
The parameter will remain in effect for all subsequent Repair till it is changed back to its default of 0.
Reset the parameter back to its default value of 0 once you have completed that repair for a subset of rows. The reason is, not every repair done with a “where” clause can be guaranteed to have synchronized the whole target table. To reset it back to its default, issue the following command on target prior to running another repair:
sp_ctrl>reset param SP_DEQ_PARTIAL_REPAIR_CLR_OOS
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center