I'd argue that it's reasonable for Oracle to exclude NO_DATA_FOUND, as every query will eventually encounter it. It's not really a "server error". Some of the other exclusions seem reasonable, too, but "out of process memory"? Maybe that error precludes the firing of the trigger!
Sent: Thursday, March 02, 2006 11:35 AM
To: Mercadante, Thomas F (LABOR)
Subject: Re: Why does a job loose its context?
Argggg! Burned by those dang docs again!
All sorts of errors will fire, syntax and otherwise. Now one has to
ask why the heck won't those errors fire the trigger. Here are the
results from the log since yesterday.
Thanks for finding that, never occurred to me that a few errors would
be excluded from the trigger. Makes finding this problem more
difficult. The code is not "properly" instrumented. I will definatley
hit Tom Kytes session at Hotsos on this.
On 3/2/06, Mercadante, Thomas F (LABOR)
> According to the docs,
Please access the attached hyperlink for an important electronic communications disclaimer: