Post does not move forward in terms of “operations posted” or “transactions posted” in the “show post detail” output (both of which remain static) and the # of messages/backlog keeps increasing. The following messages keep showing up in the event log when that happens:
Notice 2010-11-04 21:15:05.486816 11072 4137130192 Poster: removed compare client as queue reader after 100 seconds (processDataEquatorMsg,L914) (posting from name1, queue queue_name, to name2) [module opo]
Error 2010-11-04 21:13:24.776381 11072 4028169104 s:2 Table "OWNER"."TABLE_NAME" out of sync for queue queue_name at source rowid AAAGLzAAFAAPmKwAAF: Row Not Found (posting from name1, queue queue_name, to name2)
Info 2010-11-04 21:13:19.602102 11072 4136773312 Poster launched, pid = 11072 (posting from name1, queue queue_name, to name2)
The compare marker(s) in the Post queue did not get removed when the compare was/were cancelled on the source.
Try one of the following measures to have Post running again:
1. Shutdown and restart Shareplex a couple of times.
2. Stop Post cleanly and then restart it. Upon every restart the Post will process some data till it encounters yet another compare marker. The # of such markers encountered will depend on how many compare were cancelled on the source. This may need to be done a number of times to get rid of all such markers in the Post queue. Once the Post queue is free of these markers, it will resume normal processing and will not get stuck.
When a compare is launched from the source, it takes a read consistent view of the source table and sends a compare marker message, a kind of token message that is used to take a read consistent view of the target table at the right time. Normally a “compare cancel <id>” command will get rid of the compare processes on source and target (sp_desvr process on source and sp_declt process on target), and will also clean up the compare marker from Shareplex queues as well as get rid of the *sp_declt* reader to the Post queue. At times the compare markers are not removed from the Post queues and they interfere with the functioning of Post till they are removed by one of the methods described above.
