-
Title
Post error 119128 - Can't rewind queue to sequence -1 -
Description
Post errors out as below:
sp_ctrl > show
Â
Process Source Target State PID
---------- ------------------------ ------------ -------------------- ------
MTPost o.SID-NNN_qu o.SID Stopped - due to error
The following messages appear in the target event_log:
Info 2010-03-24 17:55:51.420236 8746 1 Command server launched, pid = 8746 (connecting from servername)
Info 2010-03-24 17:54:17.400552 23824 1 Poster exited with code=1, pid = 7750 (posting from name, queue Queue_name, to name)
Error 2010-03-24 17:54:17.394521 7750 1 Poster stopped: Internal error encountered; cannot continue (posting from name, queue Queue_name, to name)
Error 2010-03-24 17:54:17.391438 7750 1 Poster: 119128 - Can't rewind queue to sequence -1; que error: 20 (posting from name, queue Queue_name, to name) [module opo]
Notice 2010-03-24 17:54:17.390582 7750 1 Poster: Transaction history for mismatch logged in /<path>/name_fb_7750_3.log. (posting from vraedb, queue Queue_name, to fraedb) [module opo]
Info 2010-03-24 17:54:15.169075 7753 1 Command server launched, pid = 7753 (connecting from name)
-
Cause
A partial rollback in the Post queue is causing it to error.
-
Resolution
Workaround:
A simple way to get around the error is to configure the parameter SP_OPO_CONTINUE_ON_MISMATCH to 1 and then restart Post:
sp_ctrl> set param SP_OPO_CONTINUE_ON_MISMATCH 1
sp_ctrl>start post
Once the Post is running fine as evident from â€show post detaillâ€, qstatus, status, etc, then the parameter can be disabled by:
sp_ctrl> reset param SP_OPO_CONTINUE_ON_MISMATCH
If the error still occurs despite the parameter enabled, then Support can be contacted to remove the rollbacks manually from the queue.
-
Additional Information
It will not do any harm in leaving the parameter turned on but for the small overhead that may be associated when running Post with the parameter enabled.