Q: odd entries in user_dependencies
Malcolm Dew-Jones
I'm looking at USER_DEPENDENCIES and I see some odd entries. There are
lots of these entries, I copied just a few to show.
NAME TYPE REFERENCED REFERENCED_NAME REFERENCED_TYPE
_OWNER
------------ ------------- ---------- ------------------ ----------------
UTILITY_PKG PACKAGE BODY DGEN DBMS_OUTPUT NON-EXISTENT
UTILITY_PKG PACKAGE BODY DGEN USER_TAB_COLUMNS NON-EXISTENT
UTILITY_PKG PACKAGE BODY DGEN USER_CONS_COLUMNS NON-EXISTENT
UTILITY_PKG PACKAGE BODY DGEN USER_CONSTRAINTS NON-EXISTENT
Obviously I don't expect anyone to know exactly what someone did on my
system to get these entries, but I would like to understand in the general
sense "what's up".
The UTILITY_PKG package and body compiles fine, and is in use by the
application. I would expect the above to at least disappear after the
package is recompiled but that doesn't clean them out.
Anyway, if anyone could shed light on these odd entires I would appreciate
it.
Thanks.
DA Morgan
TTBOMK ... there was a dependency and it is no longer valid.
--
Daniel A. Morgan
University of Washington
damo...@x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
Andy Hassall
wrote:
>Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
>
>I'm looking at USER_DEPENDENCIES and I see some odd entries. There are
>lots of these entries, I copied just a few to show.
>
>NAME TYPE REFERENCED REFERENCED_NAME REFERENCED_TYPE
> _OWNER
>------------ ------------- ---------- ------------------ ----------------
>
>UTILITY_PKG PACKAGE BODY DGEN DBMS_OUTPUT NON-EXISTENT
>UTILITY_PKG PACKAGE BODY DGEN USER_TAB_COLUMNS NON-EXISTENT
>
>UTILITY_PKG PACKAGE BODY DGEN USER_CONS_COLUMNS NON-EXISTENT
>UTILITY_PKG PACKAGE BODY DGEN USER_CONSTRAINTS NON-EXISTENT
>
>
>Obviously I don't expect anyone to know exactly what someone did on my
>system to get these entries, but I would like to understand in the general
>sense "what's up".
NON-EXISTENT type indicates a "negative dependency", which generally shows up
when an object depends on a another object via a public synonym.
If the referenced object is being resolved via a public synonym, then that
requires that there is no object (or private synonym) in the local naming scope
of the same name, because these take precedence over public synonyms - so
Oracle registers a dependency on the named object being non-existent in the
local schema.
e.g. if you created an object named DBMS_OUTPUT in the DGEN schema, then
UTILITY_PKG would become invalid.
--
Andy Hassall :: an...@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Malcolm Dew-Jones
: On 19 Jun 2006 13:33:08 -0800, yf...@vtn1.victoria.tc.ca (Malcolm Dew-Jones)
: wrote:
I would never have thought of that, but it makes a lot of sense now I hear
it. Thanks greatly.