At times when activating with "live" option, activation log (*rmp* log) may contain the following messages:
.
.
04/11 04:47:50 "OWNER"."TABLE1": CONTINUED,
04/11 04:47:50 LockTablesLive: NOT locking "OWNER"."TABLE1"
04/11 04:47:50 "OWNER"."TABLE2": CONTINUED,
04/11 04:47:50 LockTablesLive: NOT locking "OWNER"."TABLE2"
.
.
What do these message mean?
The "live" activation may not have been able to lock certain tables at a given point in time and as a result logged these messages in the rmp log.
The "live" option of activation is typically used in conjunction with hotbackup and reconcile for first time activation and sync. When activating with "live" option, Shareplex will attempt to lock a table for the purpose of analyzing it. If it cannot acquire the lock, it will move on to the next table and re-visit the table in question.
When the activation is complete, issue "show config" to determine if there are any tables that failed to be brought into replication for any reason and then review the event_log and *rmp* log to see if locking was an issue that caused the table to fail to replicate.
For example, the following output of "show config" shows that one table failed to activate:
sp_ctrl (server_name:2100)> show config
This may take a moment.
Config : config_name
Datasource : o.SID
Activated : 19-Feb-08 20:48:10
Actid : 11
Total Objects : 1050
Total Objects Replicating : 1049
Total Objects Not Replicating : 1
One should investigate why the object failed to activate.
There is a parameter SP_OCF_LOCK_WAIT_TIME that has a default value of 5 and it lets Shareplex wait for 5 minutes to acquire a lock on the table and move on if it is not able to acquire the lock but re-visit the table for a retry, up to 5 times. If the locking is still an issue, the parameter can be increased to say, 10. In that event Shareplex will try to acquire the lock for 10 minutes and will do it to a maximum of 10 attempts. One can use trial and error to set the optimum value for this parameter if running into locking issues during "live" activation.</p><p>Another workaround is to skip the analyze altogether. See SOL2003 and SOL35877 for further details and implications of doing so.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center