Re: Invalid objects in new database

It seems that package or package bodies where created but have an INVALID status because some error has occured.
Can you please run the following query :

select owner,object_name, object_type, status from dba_objects where object_type in ('PACKAGE','PACKAGE BODY') order by 1,2,3;

and then post the result to this newsgroup so that I can help you further ?

Jim Smith <jim_at_jimsmith.demon.co.uk> a écrit dans l'article <rSRiuVAbNkf4EwEw_at_jimsmith.demon.co.uk>...
> I have the following invalid objects after creating a new database.
> After numerous attempts to clear them, including recreating the database
> from scratch I am still at a loss.
>
> DBMS_SUMADV PACKAGE BODY
>
> This seems to depend on a non-existent DBMS_SUMADV_LIB. Both DBMS_SUMADV
> and DBMS_SUMADV_LIB are packages created (wrapped) in prvtsma.plb, and
> DBMS_SUMADV also seems to be in prvtsum.plb. Thesea are both run from
> catproc.sql Attempting to recompile complains 'object DBMS_SUMADV_LIB
> must be declared. I don't even know what it does.
>
> MDDICT PACKAGE BODY
> MDEXEC PACKAGE BODY
> MDEXEX PACKAGE BODY
> MDTRIG PACKAGE BODY
> MDVERIFY PACKAGE BODY
> MD_DDL PACKAGE BODY
> MD_DML PACKAGE BODY
> MD_PART PACKAGE
> MD_PART PACKAGE BODY
> SERV_PART PACKAGE BODY
>
> Attempting to recompile these produces the message that the package does
> not exist, rather than a compilation error, despite the objects
> appearing in the dba_objects table. I thought these were part of the
> spatial option so I recreated the database without that option but they
> are still there.
>
> I'm using
> Oracle 8i (8.1.5)
> Redhat Linux 6.0
>
> Is this a Linux only thing or generic 8.1.5. Any ideas?
>
> --
> Jim Smith
>
Received on Fri Jan 14 2000 - 03:19:21 CST