Skip to Main Content

Package Dependencies 2

OwnerNameTypeReferenced OwnerReferenced NameReferenced TypeReferenced Link NameReferenced ColumnDependency TypeColumn Name In Source
TEDSTRUIKTED_MAILPACKAGE BODYTEDSTRUIKTED_MAIL_TEST_PARTSTABLE - DISPOSITIONHARDYES
TEDSTRUIKTED_MAIL_OLDPACKAGE BODYTEDSTRUIKTED_MAIL_TEST_PARTSTABLE - DISPOSITIONHARDYES

Info

Packages and the tables & columns they reference, take 2. Click here for take 1.

A second method to find out which packages reference which columns. This one uses the elegant "dba_dependency_columns" method presented by Rob van Wijk.
The view ted_dependency_columns_v I use is identical to Rob's dba_dependency_columns view, except for the formatting.

I have noticed that dependecies of packages on synonyms (for tables/views) are not always included in the results. I suspect that these dependencies are not included in the sys.dependency$ view,but that is something to be investigated.

In the report above I have added an outer join with dba_source, to check if the column is actually mentioned in the source text. That way you avoid finding matches that reference the entire row, in constructions like table%rowtype or select * from table, but that never actually use the columns you're looking for.
Note that the source of (materialized) views is not checked; for that you'd need a select on dba_(m)views and some way to convert the longs to clobs.

In this example, we're looking for packages that reference column 'disposition' in table 'ted_mail_test_parts'. You'll want to adjust the where clauses to your needs.

Either run this as sys/system, or give the user these privileges:

Code

Region

Identification
Sequence
Title
Type
Source
Source Type
Region Source

View

View
Name
DDL