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! Paul Baumgartel paul.baumgartel@xxxxxxxxxxxxxxxxx 212.538.1143 -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Ethan Post Sent: Thursday, March 02, 2006 11:35 AM To: Mercadante, Thomas F (LABOR) Cc: oracle-l@xxxxxxxxxxxxx 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. MESSAGE TTL ------------------------------ ------ ORA-1 95 ORA-1017 1 ORA-1427 65 ORA-1722 1 ORA-3113 1 ORA-4043 ###### ORA-4068 5 ORA-54 5 ORA-900 2 ORA-903 5 ORA-904 5 ORA-918 2 ORA-920 1 ORA-933 2 ORA-936 1 ORA-937 1 ORA-942 84 On 3/2/06, Mercadante, Thomas F (LABOR) <Thomas.Mercadante@xxxxxxxxxxxxxxxxx> wrote: > Ethan > > According to the docs, -- //www.freelists.org/webpage/oracle-l ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== -- //www.freelists.org/webpage/oracle-l