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.
<ghoward_at_isx.com> wrote in message news:r0knauccvshf4pg2e2d6d5d1sl02hgq35o_at_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_at_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.
>
Received on Thu Apr 04 2002 - 04:21:18 CST
