Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!feed.news.tiscali.de!newsfeed01.chello.at!newsfeed02.chello.at!news.chello.at.POSTED!53ab2750!not-for-mail From: "Can" Newsgroups: comp.databases.oracle.misc References: Subject: Re: enabled trigger doesn't fire Lines: 30 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Message-ID: Date: Thu, 09 Sep 2004 11:20:19 GMT NNTP-Posting-Host: 80.110.189.168 X-Complaints-To: abuse@news.chello.at X-Trace: news.chello.at 1094728819 80.110.189.168 (Thu, 09 Sep 2004 13:20:19 MEST) NNTP-Posting-Date: Thu, 09 Sep 2004 13:20:19 MEST Organization: Customers chello Austria Xref: dp-news.maxwell.syr.edu comp.databases.oracle.misc:112539 "Richard Gjerde" schrieb im Newsbeitrag news:wWV%c.8600$g%5.89938@news2.e.nsc.no... > Thanks for the response Can. But there is nothing wrong with the trigger. It > is working fine on the production database, and since the database I am > working on is an exact copy, the trigger is the same. However, it doesn't > fire even though it (look like) it is activated. Hmm, if you think the trigger is disabled, you need to execute: ALTER TABLE tablename ENABLE TRIGGER triggername; Possible solution: If I recall correctly, statements need to be commited before the trigger fires. So - did you execute a commit upon the insert statement? I know you're saying that db is a 100% exact copy, but if it were, the trigger should fire. Maybe you don't have permissions to write into that table. If there's an exception in the trigger code, and this exception is caught/handled, then your insert on the first table will still work, whilst the second table will stay unaffected. So even, if the row is inserted in the first table, this need not mean your trigger is disabled - it still can be enabled, but just be throwing an unhandled exception. Can Oezdemir