Oracle database - Automatic Data Lineage

Ever wonder about the source of data of some view and what tables are used to define it? Using Dataedo, you can easily make sense of the data flow between objects in the Oracle database by visualizing it using Data lineage functionality.

What to expect

Views

Dataedo analyzes SQL scripts defining database views with a built-in SQL Parser and builds column-level lineage from tables/views to views (both materialized and not) queried by them. To learn more about parsing the PL/SQL dialect, visit: PL/SQL Parsing.

Stored Procedures and Functions

Dataedo will create column-level data lineage for stored procedures based on the script. The script will be divided into steps represented as separate processes. Data lineage will be created only for supported steps; the unsupported steps will be named after the first word from the process script and end with three dots. This is seen on 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

Troubleshooting

I don't see data lineage for views

I don't see 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.

I don't see 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.

Cross-database lineage is not built

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.