The “activate config” with “nolock” option will not lock the source table. The net effect would be, Shareplex may simply replicate changes to a table from the middle of a transaction. In simple terms, Shareplex activation process brings tables into replication one by one by locking them first to ensure that there are no open transactions. But, when performing nolock activation, it does not lock the source table at all. Due to this one may lose some transactions depending on how busy the table is. This is not true for the regular (default) activation.
In case of “live” activation, Shareplex tries to acquire lock on the source table. If it does not succeed, it moves to the next table till all tables are brought into replication and then revisits all tables that failed to lock. It repeats this till the activation process times out which is 30 minutes by default. For Shareplex 7.6 and up, all activation are “live” and the option “live” need not be specified. For prior versions, the “live” option needs to be specified otherwise the activation terminates if Shareplex is not able to lock a table.
