The activate config works when both the SCN and nolock options are specified together though the SharePlex manuals recommend otherwise stating that these two options are mutually exclusive.
When running “activate config” with SCN and nolock option, the activation works fine as shown:
sp_ctrl (alvsupl14:9111)> status
Brief Status for alvsupl14
Process State PID Running Since
--------------- ------------------------------ -------- --------------------
Cop Running 7213 12-Jun-18 14:57:52
Cmd & Ctrl Running 7223 12-Jun-18 14:58:07
There are no active configuration files
sp_ctrl (alvsupl14:9111)> activate config config1a scn=22100297145 nolock
sp_ctrl (alvsupl14:9111)> list config
File Name State Datasource
-------------------------------------------------- ---------- ---------------
.
.
config1a Active o.ORA11GR2
Last Modified At: 21-May-18 16:05 Size: 117 Internal Name: .conf.50
This is despite the fact that the SharePlex Reference Guide advises against using nolock option in conjunction with SCN or SEQNO option.
When SCN or SEQNO option is used with “activate config”, SharePlex does not lock the source tables which it normally would to ensure that there are no open transactions gathered during activation. Hence directing the activation to use the nolock option is irrelevant and its use will not change the outcome of activation which will be same regardless of the presence or absence of nolock option, given that SCN or SEQNO options of activation behaves as if the activate command is issued with nolock option.
