The Inspiration: Legacy Metadata Lineage
In enterprise data modeling, knowing the "Lineage" or "Impact" of a change is foundational. This proposal seeks to bring a robust dependency inspector to the FDI/OAC front-end, allowing administrators to audit the entire ecosystem before performing cleanup activities.
Problem Statement
As user adoption grows, the Connections and Datasets tabs become cluttered with redundant or incorrectly configured objects. This "Data Sprawl" creates several critical issues:
- Traceability Gaps: Administrators cannot easily identify which Workbooks, Data Flows, or Dashboards are consuming a specific Connection or Dataset.
- The Cleanup Blocker: Currently, the system prevents the deletion of a connection or dataset if it is tied to another object. However, it does not explicitly show which object is holding the lock. This leaves administrators in a "guessing game," unable to clean up the environment because they cannot trace the specific dependency that needs to be unlinked first.
- Security Blind Spots: When users create datasets without administrator privileges, these objects remain "hidden" from global oversight, yet they consume system resources and prevent connection cleanup.
- Maintenance Overhead: Identifying the "Source of Truth" becomes impossible when dozens of similarly named connections exist with no visibility into their dependencies.
Proposed Solution: The "Dependency Inspector" Feature
Oracle should introduce a centralised Impact Analysis utility within the Console:
- "Used By" Visualizer as we have in ODI 12c: Add a right-click option for any Connection or Dataset called "View Dependencies." This would generate a tree view or list of every object (Workbook, Data Flow, Scheduled Job) utilising that specific item.
- Unlock & Trace Logic: When a deletion is blocked, the system should provide an interactive list of the "blocking" objects. This allows the admin to navigate directly to the dependent item and re-map or delete it.
- Cross-User Visibility: Allow Administrators to see dependencies even if the dependent object is in a user’s "My Folders" area, ensuring no "hidden" content prevents environment hygiene.
- Global Connection Auditing: A dashboard for Admins that identifies "Orphaned Connections" (those with zero dependencies) to facilitate rapid cleanup.
Business Value
- System Hygiene: Enables administrators to confidently decommission redundant connections, resolving the deadlock of "tied" objects.
- Reduced Downtime: Eliminates the trial-and-error approach to environment maintenance.
- Robust Governance: Provides a clear audit trail ensuring the organisations governance model
