The solution suggested is for a Unix environment only.
If you want to continue posting but not having Shareplex writing to event_log and SID_errlog.sql, link the event_log and SID_errlog.sql to /dev/null as follows:
1. Shutdown Shareplex on target.
2. Create soft link for the files as below:
$ ln -s /dev/null event_log
$ ln -s /dev/null SID_errlog.sql (substitute appropriate value for SID)
3. Start Shareplex on target
This will cause entries not to be written to event log nor SID_errlog.sql, but will help speed up Post.
You should remove the soft links after you resync the tables.
Starting with SharePlex 8.6.x, number of out of sync messages logged per table, into the event_log and *errlog.sql can be controlled by the parameter SP_OPO_SYNC_LOG_FREQUENCY.
sp_ctrl>set param SP_OPO_SYNC_LOG_FREQUENCY <integer> (where integer is any positive integer)
For example, to log first out of sync message in event log and *errlog.sql and skip the next 9 out of sync messages, set the parameter as below:
sp_ctrl>set param SP_OPO_SYNC_LOG_FREQUENCY 10
Reset the parameter as below.
sp_ctrl>reset param SP_OPO_SYNC_LOG_FREQUENCY