Is it possible to force Post to stop due to Oracle errors listed in *oramsglist* file it normally (4298760)

Post process will stop on encountering any Oracle errors except those listed in the oramsglist file (located in /vardir/data directory). This solution delves on a workaround that can cause Post to stop due to the errors which are mentioned (listed) in the oramsglist file.

General information.

The following steps can be undertaken to make Post stop when encountering any Oracle error on which it does not stop by default (that is, the ones listed in the oramsglist file):

NOTICE: oramsglist only works when the parameter SP_OPO_CONT_ON_ERR is set to 1.

1. Stop Post.
2. Edit oramsglist file and remove the entry for the Oracle error that Post should no longer ignore. For example, by default Post will not stop when encountering ORA-00902 (listed in oramsglist as 902). Tp automatically stop Post when running into ORA-00902, remove the entry 902 from oramsglist file.
3. Save the oramgslist file.
4. Start Post.

To undo the above changes, reverse the changes made above by:

1. Stop Post.
2. Add the entry corresponding to the Oracle error which was earlier present by default and has since been removed (in our example it is 902).
3. Save the oramsglist file.
4. Start Post.