Log errors and exceptions
VeronicaAug 27 2012 — edited Aug 27 2012Hi,
I have a procedure that would run as a scheduled job for long hours at the time. I would like to sneak a peak at the procedure error or its unhandled exception if any occurs, but I'm not sure how.
I've taken a look at the alert_SID.log file, but it logges only following:
* All internal errors (ORA-60ORA-1578ORA-600), block corruption errors (), and deadlock errors () that occur
* Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements
* Messages and errors relating to the functions of shared server and dispatcher processes
* Errors occurring during the automatic refresh of a materialized view
* The values of all initialization parameters that had nondefault values at the time the database and instance star
no procedure errors and unhandled exceptions here.
I've enabled trace, and I saw my error number and time when the error occured. But my procedure handles very large volumes of data, and enabling tracing is not going to be accepted.
Is there another way to look at the exception, and be efficiency-friedly? If the error occurs, is it logged anywhere? I'd appreciate any suggestion.