Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Why does a job loose its context?
Speaking of triggers not firing, anyone seen an example of where a
SERVERERROR trigger does not fire?
I was looking an an issue this week where a log file in an app is reporting a ORA- error (no data found), so we added some logging to the code and turned on SERVERERROR trigger. I was hoping to get something like this in my log file.
..entering proc foo...
..ORA- error
...
However, I never got the ORA- error in my log (the application log still reports it, but it is possible some developer has hard coded this particular error string someplace where the error is not really occurring, strange but possible).
The only other option is that the trigger is not firing, I see errors for plenty of other sessions in the database. At first I thought it was because I had the EVENT level elevated for this error and the dump of a trace file was causing this, but we removed that and still getting nothing.
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Mar 02 2006 - 10:14:07 CST
![]() |
![]() |