Oracle - Automatic Data Lineage

Oracle Database—Automatic Data Lineage

Dataedo captures Data Lineage at four levels:

Object-level

Mapping tables to specific data sets in your system

Column-level

Providing detailed insights into how columns relate and transform data

Source-level

Tracking data relationships for individual sources

System-level

Offering a comprehensive view of connections across all databases

This document outlines how lineage is generated and provides troubleshooting steps for some common issues.

Lineage support by object type

Views

Dataedo analyzes SQL in database views using its built-in SQL Parser and generates column-level lineage by tracking dependencies between queried tables/views and the resulting view object.

useful tip

Check PL/SQL parser documentation to learn more.

note

Dataedo will generate lineage only for SQL statements supported by the SQL Parser. Check the SQL Parser documentation for more information.

troubleshoot lineage from views

In case of any issues with view lineage, follow these steps:

• Make sure you selected PL/SQL as the SQL Dialect in the Data Source configuration
• Rerun the import process to update the schema if you're using an older version or incorrect settings

Stored procedures

Dataedo extracts column-level data lineage from stored procedure scripts. Each script is divided into steps, represented as separate processes.

• Supported steps generate lineage automatically.
• Unsupported steps are marked with the first word of the process script followed by three dots (...). These appear in the Data Lineage Configuration tab in Desktop.

Known Limitations

1. Check the limitations for views lineage from SQL parser

2. Check the limitations for stored procedures lineage from SQL parser

Dataedo generates lineage only for supported SQL syntax (in this case PL/SQL). Check the SQL parser documentation for more information.

Troubleshooting

Missing data lineage for views

1. Make sure you have selected the right SQL dialect - in this case, PL/SQL (SQL Dialect field at the Data Source level).

2. Rerun the import of the source - maybe the schema was imported in an older version, or the configuration was incorrect.

Missing data lineage for stored procedures

1. Make sure Dataedo supports the SQL syntax of the procedure. Check Known Limitations above.

2. Rerun the import of the source - maybe the schema was imported in an older version, or the configuration was incorrect.

Missing cross-database lineage

1. Make sure the source object has a Linked Source with a correctly assigned database.

2. Rerun the import of the source - maybe the schema was imported in an older version, or the configuration was incorrect.

If you encounter any issues with stored procedure lineage, follow these steps:

• Verify that Dataedo supports the SQL syntax used in the procedure
• Rerun the import process to refresh schema changes

Need help?

If you run into any problems or have questions, reach out to Dataedo support.