Post errors out with "ORA-01843: not a valid month" (4216036)

You see the following error in the event log:

sp_ctrl>show log reverse

11/01/07 22:34 Process exited sp_opst  (for o.SID1-o.SID2 queue queuename) [pid = 14957] - exit(1)
11/01/07 22:34 Error: sp_opst (for o.SID1-o.SID2 queue queuename) Unexpected Oracle error: ORA-01843: not a valid month. (object name: "owner"."tablename")
11/01/07 22:34 Notice: sp_opst(osp) (for o.SID1-o.SID2 queue queuename) ORA-01843: not a valid month.

There could be issues with source data in that it may have invalid date values.

You can query the source row on the basis of the primary key taken from the failed sql which appears in the opo log. The source row would have invalid date data for the post to return ORA-01843 error. When that is determined, one can ignore this Oracle error by configuring the file oramsglist located in /vardir/data directory and setting the parameter SP_OPO_CONT_ON_ERR (see Shareplex Admin Guide for details). Since the out of sync has been introduced and moreover the underlying issue still exists on the source database, one may want to correct the source data and then run compare with rowid option (or other compare option) to take care of this out of sync row.