Post is not moving beyond a certain log offset and the following messages appear in target event log over and over:
Warning 2010-07-14 15:24:27.090515 520404 515 s:241 Poster: ../src/opst_mt/sql.cpp:6274: Table "OWNER"."TABLE_NAME" is out of sync with source rowid: AAArgmAAIAABWBbAHX due to data integrity error. MID: 36230711 is discarded. (posting from NAME1, queue QUEUE_NAME, to NAME2) [module opo]
Error 2010-07-14 15:24:27.088363 520404 515 s:241 Poster: Invalid length in column data, check poster logfile for details (posting from NAME1, queue QUEUE_NAME, to NAME2) [module opo]
Error 2010-07-14 15:24:27.086215 520404 515 s:241 Poster: Incorrect length in message (posting from NAME1, queue QUEUE_NAME, to NAME2) [module osp]
The following type of message appears in the *opo* log (log of Post process):
opo 2010-07-14 15:49:27.207163 3260540 515 s:241 ***** Invalid length in column data *****
Batch processing is enabled on source (applicable in Shareplex 7.0 and up).
If batch processing is enabled on source, post may end up with a corrupted message.
Verify that the parameter SP_ORD_BATCH_ENABLE is set to 1 on source. Issue "list param all read" on source sp_ctrl to check this. If it is enabled, disable it by running the following command in sp_ctrl on source:
sp_ctrl>set param SP_ORD_BATCH_ENABLE 0 (the parameter is live and will take effect immediately).
From now on there will not be any corrupt messages sent from source. Do not enable the parameter.
To remove the corrupted message in Post queue, contact Shareplex Support.
