Database Object Dependencies - only goes one level deep

Question

I've run the Database Object Dependencies report and it appears that the report only shows the top level dependencies and not lower level ones. Am I running this report incorrectly or is there something I'm missing.
For example, it displays the tables and views correctly but does not show any triggers that have been created for a specific table. Additionally, I didn't see any references to database links being used.
version: 3.1.1.00.09
thanks
John
Edited by: johurj on Dec 8, 2008 2:49 PM
Edited by: johurj on Dec 8, 2008 2:53 PM
Edited by: johurj on Dec 8, 2008 2:54 PM

Answer 1

John,
The report shows the immediate dependencies for the anonymous blocks and similar code snippets contained within the application components. It's just like if you did this:
create table footab (n1 number)
create trigger footrig before insert on footab for each row begin null; end;
create or replace procedure fooproc
as
begin
for c1 in (select n1 from footab) loop
null;
end loop;
end;
SQL> select referenced_name from all_dependencies where name='FOOPROC'
2 /
REFERENCED_NAME
SYS_STUB_FOR_PURITY_ANALYSIS
STANDARD
FOOTAB
SQL>
The table FOOTAB is the only "real" object that the procedure FOOPROC has a dependency on. No mention of the trigger on the table.
Additionally, I didn't see any references to database links being used.Yes, that would be a possible improvement to the report.
Scott