Oracle lineage configuration

Connect to Oracle databases to scan metadata and display it on lineage. To import lineage metadata, create data source definition, a connection, and metadata import job.

Import process overview

To import lineage metadata for Oracle, complete these steps:

  1. Create a data source definition.
  2. Create a connection to the data source in a project.
  3. Create a metadata import.

Creating a data source definition

Create a data source definition. Select Oracle as the data source type. The Database (SID) or Service name field is required.

Creating a connection to Oracle

Connection details

Create a connection to the data source in a project.
For connection details, see Oracle connection.

Creating a metadata import

Create a metadata import. Learn more about options that are specific to Oracle data source:

Include and exclude lists

You can include or exclude assets up to the schema level. Each value is evaluated as a regular expression. Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists. Example values:

  • mySchema: mySchema schema.
  • mySchema[1-5]: any schema with a name that starts with mySchema and ends with a digit between 1 and 5.

External inputs

If you use external Oracle PL/SQL scripts, you can add them in a .zip file as an external input. You can organize the structure of a .zip file as subfolders that represent schemas. Schemas are optional. If schemas are defined, the scripts are added under respective schemas in the selected catalog or project. The .zip file can have the following structure:

<schema_name>
   <script_name.sql>
<script_name.sql>
replace.csv

The replace.csv file contains placeholder replacements for the scripts that are added in the .zip file. For more information about the format, see Placeholder replacements.

Advanced import options

Extract extended attributes
You can extract extended attributes like primary key, unique and referential integrity constraints of columns. By default these attributes are extracted.
Extract invalid objects
Include invalid objects in extraction.
Extraction mode
You can decide which extraction mode to run for the imported metadata. You have the following options:
  • Prefetch: use it for relational databases.
  • Parallel bulk: use it for analytical processing engines.
  • Single-thread: use it to avoid parallelism and large queries during extraction. When you select this mode, performance might be low.
Transformation logic extraction
You can enable building transformation logic descriptions from SQL code in SQL scripts.
Dynamic SQL
Enable dynamic SQL processing in DDL scripts.

Learn more