Invalid objects in apex_030200?
557616Jan 7 2010 — edited Jan 7 2010Does anyone else have over 300 invalid objects in their apex_030200 schema?
I've was snooping around in my dev instance apex_030200 schema with sqldeveloper and noticed a lot of red Xs on package bodies. So I ran
select object_name, object_type from dba_objects where owner = 'APEX_030200' and status = 'INVALID' and got 300+ rows.
The objects include functions, procedures, packages, package bodies, views, synonyms and triggers. So then I checked my 4 other apex installs and got similar results.
My databases range from XE to 11.1.0.7 Enterprise and my Apex versions are all 3.2.0.00.27.
Since my apex installs seem to be working fine, I'm perfectly willing to leave well enough alone.
What would have caused these objects to go invalid? Obviously no one is in the database tinkering with this schema. When I run a dbms_utility.compile_schema, all the objects are marked valid, but I don't know for how long... Surely none of the default database jobs (stats etc) would cause things to go invalid.
Has anyone else seen this?