Post process is slow.
Some large transactions or sequence messages cause post to go slow. This delays the processing of other smaller transactions in the post queue.
RESOLUTION:
With named post queues, data can be isolated into separate post queues, each queue generating its own post process. The concurrent post processes facilitate smaller, more efficient operations to be posted separately. However all related tables need to be grouped into the same post queue to avoid referential integrity problems.
Here are the detailed steps.
On Target
1) Stop post.
On source
2) Shutdown shareplex
3) export SP_OCF_SKIP_ANALYZE=1 (This will ensure that the tables is not locked when activating configuration)
4) Start shareplex.
5) Activate the configuration with named post queue.
On target
6) You should see existing post queue and the new post queue are stopped.
7) Start existing post queue first
sp_ctrl> start post queue <old queuename>
sp_ctrl> show post detail queue <old queuename>
8) Check and see if you see the new actid, once you see the new actid or once the existing post queue drains, then you can start the new post queue
sp_ctrl> start post queue <new post queue name>
