The “activate config” command results in “Not all tables activated successfully”. The following is a sample screen shot:
sp_ctrl (alvsupu07:5439)> activate config config1
Not all tables activated successfully
The following are the sample event log entries:
Warning 2011-06-28 12:32:25.201724 23223 1 Activation: Failed to lock table "SHA76"."TABLE1": timeout awaiting lock. (activating sid syam) [module ocf]
The source table(s) are involved in transactions or are locked in exclusive mode by users.
This behavior is observed in Shareplex 7.6 or up. Check to see if the source table(s) are involved in transactions or are locked in exclusive mode by users. If the source table(s) are involved in transactions or are locked in exclusive mode by users, then activation process will wait for the transactions to finish or locks to be released and will keep processing other tables that do not fall in these categories and will keep revisiting problem table(s). The wait is determined by the parameter SP_OCF_LOCK_WAIT_TIME.
Check to see if the source table(s) are involved in transactions or are locked in exclusive mode by users. Wait for the transactions to finish or locks to be released. Once that occurs, make a copy of the currently active config file and activate the copy. This will result in the remaining tables brought into replication. The tables may need to be sync’d since the source table would have changed by the time it was brought into replication all the while when the target table did not receive such changes.
Related solution: See SOL75667
