The following messages are observed in event log but the Post does not stop due to error:
Notice 2015-10-14 23:06:41.932073 110732 229467904 Poster: Error reading oramsglist: expected 23 msgs, read 22 msgs (posting from SID1, queue queue_name, to SID2) [module opo]
The first entry in the oramsglist file (located in /vardir/data directory) that denotes the # of Oracle errors that will be ignored by Post is not correct. The first entry is followed by the detailed list of the Oracle errors that Post will ignore. So, if the first entry is 21, then there should be 21 different Oracle error codes following this entry which Post is expected to ignore. The file can be manipulated to add more Oracle errors to be ignored. For example, if you want an additional Oracle error to be ignored (other than those already ignored), you will change the first entry to 22 and add another Oracle error at the end of the file. If the first entry does not conform to the number of Oracle error list following it, then Post will keep writing those notices in target event_log. This usually happens when a user made changes to the oramsglist but in the process had the first entry wrongly configured.
To correct the problem:
sp_ctrl>stop post (make sure it is “stopped by user” and not “stopping”, and keep issuing “status” till it shows “stopped by user”)