Published 19 Apr 2021
Last change Oct 2025
In our newsletter, we defined schema dependencies this way:
Two database schemas depend on each other if at least one object in Schema A depends on an object in Schema B (or vice versa).
Such dependencies can arise via:
Foreign key constraints between tables in different schemas
Object dependencies (e.g. procedures, views, triggers) across schemas
You can discover these relationships using Oracle’s ALL_DEPENDENCIES or DBA_DEPENDENCIES views. KeepTool
Even a single matching dependency is sufficient to establish a dependency between the schemas.
On the Schema → Schema dependencies tab in Hora, you’ll find a visual diagram showing schema-level dependencies:
To the left of the current schema box: the “master” schemas on which the current schema depends (via foreign keys or object references)
To the right: the “detail” schemas dependent on the current schema
Below is a screenshot showing dependencies for the sample user MDSYS (we unlocked MDSYS and granted CREATE SESSION to demo).
This gives you a high-level, intuitive view of how schemas relate in your database.
There is a drill-down data grid beside the diagram:
Click any schema on the diagram, and the grid shows all objects in that schema which have cross-schema dependencies
Selecting an object displays a lower grid with dependent objects in the neighboring schema
Two checkboxes indicate foreign key dependencies, object dependencies, or both
Now in Hora, you can trace schema-level relationships down to individual object-level dependencies.
This offers powerful insight into where cross-schema coupling occurs.
Ready to explore your schema dependencies? Try Hora’s dependency visualization tools in your environment.
➡️ Try for free
KeepTool’s Oracle tools serve developers, DBAs, and support engineers. Based on 20+ years of customer feedback, we continue enhancing the UI and features with each release.