RE: source of package invalidation

From: Chandra Pabba <>
Date: Sat, 14 Mar 2009 11:03:02 -0600
Message-id: <015501c9a4c6$bc5b7500$35125f00$_at_net>

Opps, sorry wrong thread.

-----Original Message-----
From: Chandra Pabba [] Sent: Saturday, March 14, 2009 11:02 AM
To: ''; '' Cc: ''
Subject: RE: source of package invalidation


Did you check to make sure that you can successfully SSH between the nodes (using both the Public and private interfaces) - without being prompted for password or seeing the banner.


-----Original Message-----
From: [] On Behalf Of Yong Huang
Sent: Friday, March 13, 2009 10:34 AM
Subject: Re: source of package invalidation

> We are seeing packages invalidated in our production database
> and I don't have a clue how to track down the actual cause.
> I've taken a look at dba_dependencies and know the potential
> candidates for causing the invalidation but I'm looking to
> actually identify the chain of events that is causing this.


Why not check latest last_ddl_time's?

select owner, object_name, object_type, last_ddl_time from dba_objects where last_ddl_time > sysdate - 1/12 order by 4;

Not all DDL's update the objects' last_ddl_time. See But then if they don't, they probably don't invalidate the dependent objects either.

Auditing helps too. I always turn on audit_trail when I build a new database. As far as I know, if you don't actually audit anything (type command audit <something>), there's really no overhead. But when you do need to audit something even temporarily, you don't need to schedule downtime to change that parameter. So in this case, you would just (I think) audit table, audit view,..., and wait for the PL/SQL error to appear one more time and noaudit ...

Yong Huang       


Received on Sat Mar 14 2009 - 12:03:02 CDT

Original text of this message