When one wants to make a routing change, such as sending table to a different queue or target, the procedure is to make a copy of the currently active config file, make the change in the route for the table(s) in the copy, and then activate the copy. This is supposed to lock the source tables very briefly and does not require exclusive lock as may be required when the table is activated first time, since only routing changes in this activation called continuing activation. When doing a continuing activation involving routing change, it sometimes fails as following event log entries show:
08/01/07 17:11 Process exited sp_tconf (for o.M2PRD) [pid = 1598922] - exit(1)
08/01/07 17:11 Bad config file: file - config_multi_queue.20070801; Unable to lock "CN"."CN_COMMISSION_LINES_ALL", it is currently involved in a transaction.
08/01/07 17:11 Config compilation completed: datasrc - o.M2PRD; file - config_multi_queue.20070801
08/01/07 17:11 Notice: Object "CN"."CN_COMMISSION_LINES_ALL" locked by user "APPS",session(422),process id(18778),mode=ROW EXCLUSIVE(3),OS user applinx [sp_tconf(osp)/1598922]
08/01/07 17:11 Notice: Object "CN"."CN_COMMISSION_LINES_ALL" locked by user "APPS",session(373),process id(23989),mode=ROW EXCLUSIVE(3),OS user applinx [sp_tconf(osp)/1598922]
You need to be signed in and under a current maintenance contract to view premium knowledge articles.