Add support for collecting lineage when an Oracle database connects to a Teradata database via a database link

Summary

Please add support for collecting lineage when an Oracle database link connects to Teradata. Today, Manta supports Oracle database links when the target is another Oracle database, but it does not support Oracle database links that point to a different technology such as Teradata.

Problem

In our environment, Oracle database links are used to access Teradata objects from Oracle-based workloads. Because this cross-technology database link pattern is not currently supported, the lineage breaks at the Oracle database link boundary. This creates incomplete end-to-end lineage and leaves downstream assets unresolved or disconnected.

Requested enhancement

Extend Oracle database link lineage support so the Oracle scanner can recognize and resolve database links whose target is Teradata.

At a minimum, the enhancement should allow Manta to:

• Detect Oracle database links that point to Teradata
• Capture the connectivity details needed to resolve the remote system
• Map the Oracle-side reference to the correct Teradata source or object
• Continue lineage across the Oracle-to-Teradata boundary

Suggested approach

A useful model already exists in other cross-technology scanning patterns, such as Informatica. In that case, the scanner collects and stores connectivity metadata needed to resolve cross-technology lineage, including items such as:

• Host
• Database name
• Connection ID

A similar pattern for Oracle database links could make cross-technology resolution possible for Oracle-to-Teradata use cases.

Business value

This enhancement would:

• Improve end-to-end lineage completeness
• Reduce unknown or unresolved assets
• Better reflect real enterprise integration patterns
• Increase the value of lineage for impact analysis, governance, and troubleshooting

Use case

An Oracle workload references data through a database link that connects to Teradata. The Oracle scanner identifies the database link, captures the connection details, and resolves the lineage to the corresponding Teradata system and objects instead of stopping at the Oracle boundary.

Why this matters

Cross-technology connectivity is common in enterprise environments. Supporting Oracle database links only when they point to Oracle leaves an important gap in lineage coverage. Oracle-to-Teradata support would address a real-world integration pattern and materially improve lineage accuracy.