Oracle

IBM Automatic Data Lineage provides a powerful scanner to the Oracle database. Automatic Data Lineage can connect to the Oracle database via its own connection and automate the scanning of metadata within the selected catalog, including but not limited to tables, views, indexes, PL/SQL procedures, synonyms, sequels, and triggers. Then, Automatic Data Lineage can read all the SQL programming code and logic stored within. This allows Automatic Data Lineage to generate lineage at the lowest granularity while showing all data transformations throughout the pipeline.

Automatic Data Lineage currently scans:

• PL/SQL scripts

• Database dictionaries

• Stored procedures

• Functions

• Packages

• Triggers

• Objects

• Views

• DB links

• Exadata links

Check out the guides below for more details on setting up this scanner.

• Oracle Scanner Guide
• Oracle Integration Requirements
• Oracle PL/SQL Manual Inputs
• Oracle Resource Configuration

Extraction and Analysis Phase Scenarios

Extraction Phase

For the extraction phase for Oracle databases, there are two scenarios.

1. Oracle dictionary mapping scenario — connects to each configured Oracle database and stores the mapping between these values: global database name, instance name, host name, port, dictionary ID, connection ID, list of schemas

2. Oracle extractor scenario — connects to each configured Oracle database and extracts the database dictionary and DDL scripts from the configured schemas

3. IBM Automatic Data Lineage supports Git Ingest connections from version 42.4, for the download of files from a Git repository to the Oracle workflow. For more information, see Manta Flow Agent Configuration for Extraction:Git Source

Analysis Phase

At the beginning of the analysis phase, a new revision scenario is called, which creates a new revision in the internal metadata repository so it is ready to accept new metadata.

For the analysis phase for Oracle databases, there are three scenarios.

1. Oracle dictionary dataflow scenario — analyzes metadata from the extracted Oracle database dictionaries and and saves it in your Automatic Data Lineage metadata repository

2. Oracle DDL dataflow scenario — harvests metadata and lineage from the extracted Oracle DDL scripts and and saves it in your Automatic Data Lineage metadata repository

3. Oracle PL/SQL dataflow scenario — harvests metadata and lineage from the provided PL/SQL scripts and and saves it in your Automatic Data Lineage metadata repository

Related Articles

• Explanation of Oracle Connector Log Errors

• Lineage Missing for Tables Created by CTAS Statement

• Dictionary Dataflow Scenario Fails with java.langOutOfMemory: Java heap space

• Connection Refused/Reset during the Oracle Extraction Phase

• How to Configure a Manual Dictionary Mapping for an Oracle RAC Database

• How Manta Handles Database Temporary Tables

• How to Pre-Process Oracle and SQL*Plus Scripts

• Oracle Database Links

• How to Handle Dynamic SQL Scripts