Just thought I would let you all know the solution for this, in case
anyone else does the same thing and needs to fix it.

Oracle Support had me run catpatch.sql and it worked. I can now run
exports and all the packages that were invalid are now valid.

Betsy
On Aug 26, 2006, at 5:53 AM, Betsy Ward wrote:

> Here's a question maybe someone on this list has experienced. I
> just started in this position in July. I was told that a certain
> database was version 9.2.0.6. So when the July Oracle Security
> patch came out I applied it to this database, 2 weekends ago,
> along with all the others here that are 9.2.0.6.
>
> We've since had various problems with this particular database and
> I tracked it down to the patch. The database is really version
> 9.2.0.3. So I tried last night to roll the patch back. It rolled
> back, but there are now 4 INVALID packages. I did run UTLRP, but
> had it blow up on the BEGIN rdbms_registry_sys.validate components.
>
> So I researched on metalink and ran
> SQL> execute DBMS_REGISTRY_SYS.VALIDATE_CATPROC
>
> PL/SQL procedure successfully completed.
>
> But it didn't change anything. In the dba_registry it still lists
> the CATPROC as INVALID. Also 4 objects won't compile either.
>
> SQL> select count(*) from dba_objects where status = 'INVALID';
>
> COUNT(*)
> ----------
> 4
>
> SQL> alter package sys.dbms_export_extension compile;
>
> Warning: Package altered with compilation errors.
>
> SQL> alter package sys.dbms_internal_logstdby compile;
>
> Warning: Package altered with compilation errors.
>
> SQL> alter package sys.dbms_logmnr_session compile;
>
> Warning: Package altered with compilation errors.
>
> SQL> show errors
> No errors.
> SQL> Select text from dba_errors where name
> ='dbms_export_extension' and owner = 'sys';
>
> no rows selected
>
> Does anyone know if there would be bad repercussions if I ran
> catproc.sql and catalog.sql again? What I'm finding on metalink
> suggests to do that, but I don't want to blow anything up any
> further. Although I do feel that I'm close to getting it back.
> And if I do that will it actually fix the packages?
>
> Thanks.
>
>


Oracle LazyDBA home page