Path: news.easynews.com!easynews!priapus.visi.com!news-out.visi.com!hermes.visi.com!news.maxwell.syr.edu!newsfeed.sovam.com!news2!not-for-mail From: "Vladimir M. Zakharychev" Newsgroups: comp.databases.oracle.server Subject: Re: Oracle Trigger Problem Date: Thu, 4 Apr 2002 14:21:18 +0400 Organization: N-Networks Lines: 35 Message-ID: References: <20020403214909.01936.00001676@mb-df.aol.com> NNTP-Posting-Host: 212.233.81.44 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: babylon.agtel.net 1017915591 20253 212.233.81.44 (4 Apr 2002 10:19:51 GMT) X-Complaints-To: usenet@babylon.agtel.net NNTP-Posting-Date: 4 Apr 2002 10:19:51 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Xref: easynews comp.databases.oracle.server:142006 X-Received-Date: Thu, 04 Apr 2002 03:19:15 MST (news.easynews.com) select object_name, object_type, status from user_objects where status != 'VALID' / this will show you all invalid objects and their types. If you see any invalid JAVA CLASS/JAVA SOURCE/JAVA RESOURCE here - recompile them (actually, recompile/rebuild everything that's invalid). If you are getting errors while recompiling - resolve them according to the error type (for example, add proper RESOLVER to ALTER JAVA ... RESOLVE). The import *may* have recreated your Java with old resolver/owner. -- Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications. All opinions are mine and do not necessarily go in line with those of my employer. wrote in message news:r0knauccvshf4pg2e2d6d5d1sl02hgq35o@4ax.com... > No, the import itself doesnt have any errors. The error occurs when I > do an Insert into the table with the trigger. When the trigger is > supposed to fire it says that it cannot resolve the trigger name. The > schema name is test_context and the trigger name is TriggerClient. The > error I get says that TEST_CONTEXT.TriggerClient cannot be resolved. > > > > On 04 Apr 2002 02:49:09 GMT, sanjaykunal@aol.com (Sanjaykunal) wrote: > > >Does it occur when you are importing the data ? If so, then please check the > >order in which you imported objects from the export dump file. > > > >If you import the table definitions and triggers first and then in the second > >run import the data you may have problems with triggers that go/verify against > >data in other tables. >