Resolving The Problem

For all Oracle errors, the system uses only one WMS error code: WH2352. You cannot have different severity settings for different Oracle errors through Error Code Setup.

For Oracle errors, the system automatically raises a "130" level alert based on entries in a file (db_errfile.dat). Any Oracle error for which there is an entry, causes the application to abort instantly. I am reproducing the file for your quick reference.

For non-Oracle errors, in non-interface programs, changing "Error Severity" is not going to have any impact on the behavior of the application.

#!/bin/ksh
########################################################## ##############
### File : dberrfile.dat #
### Description : List of Oracle Errors #
### #
### Copyright (C) by Yantra Corporation, USA #
########################################################################<br >#errno err-desc
-1012 NOT LOGGED IN
-3114 NOT CONNECTED
-1547 FAILED TO EXTENT
-1013 USER CANCEL
-1578 DATA CORRUPT
-1017 LOGON ERROR
-1631 MAX EXT ON TABLE EXCEEDED
-1632 MAX EXT ON INDEX EXCEEDED
-1653 UNABLE TO EXTEND TABLE IN TABLESPACE
-1654 UNABLE TO EXTEND INDEX IN TABLESPACE
-1562 UNABLE TO EXTEND ROLLBACK SEGMENT
-600 ORACLE INTERNAL ERROR
-50 OPERATING SYSTEM ERROR WHILE OBTAINING AN ORACLE ENQUEUE
-60 DEADLOCK
-942 TABLE OR VIEW DOES NOT EXIST
-1116 ORACLE SYSTEM ERROR CANNOT OPEN DATAFILE
-1458 INVALID LENGTH INSIDE VARIABLE CHARACTER STRING
-4068 INVALID PACKAGE
-6550 PL/SQL COMPILATION ERROR
-376 FILE CANNOT BE READ AT THIS TIME ( VARIED OFF )
# END OF FILE