Does Post only stop on Oracle errors encountered due to its actions or can it also stop on errors that are not caused by its actions.
General information.
Excluding certain Oracle errors associated with the out of sync encountered by Post, the Post will stop on any Oracle error caused by its action. For the most part it is not concerned with Oracle errors caused by sessions other than its own (Shareplex) sessions. But there may be exceptions. Certain Oracle errors though not caused by its actions can also cause Post to stop due to error. The following errors are such notable exceptions, and there may be many others like these:
ORA-00257
11/07/07 22:37 Notice: ORA-00257: archiver error. Connect internal only, until freed.. [sp_opst(osp)/4857912]
11/07/07 22:37 Error: Unexpected Oracle error: ORA-00257: archiver error. Connect internal only, until freed.. in opo_access7.c:298 [sp_opst(osp)/4857912]
ORA-00600
10/12/06 00:03 Warning: 15022 - Error posting ODR_INSERT1 to table "owner"."tablename". [sp_opst (for o.SID1-o.SID2 queue queue_name)/12833]
10/12/06 00:03 Notice: Oracle error: ORA-00600: internal error code, arguments: [6002], [6], [0], [2], [0], [], [], []. rowid:AABxmpAKQAABMQMAAY [sp_opst (for o.SID1-o.SID2 queue queue_name)/12833]
ORA-01683
Notice 2009-01-28 03:46:17.628436 16809 2931817376 Poster: ORA-01683: unable to extend index owner.index_name partition name by 8192 in tablespace tablespace_name. (posting from SID1, queue queue_name, to SID2) [module osp]
In these situations the resolution lies in correcting the underlying Oracle error regardless of the fact that it was not caused by Post. Once the error is corrected/addressed, then Post can restart.
