IBM Db2

IBM Automatic Data Lineage boasts a powerful scanner for IBM Db2 technology. Automatic Data Lineage can connect to the IBM Db2 resource for extracting and analyzing the pertinent metadata within the selected databases. This metadata includes but is not limited to tables, views, indexes, SQL procedures, schemas, databases, columns, and triggers. Then, Automatic Data Lineage can parse all the SQL programming code and logic stored within. This allows Automatic Data Lineage to generate lineage down to the column level. Automatic Data Lineage supports the following Db2 flavors: LUW, z/OS, Db2 on Cloud, Db2 Warehouse, and Data Virtualization (Watson Query). Other offerings of Db2 for i (iSeries formerly AS/400) are not supported.

Automatic Data Lineage currently scans:

• Data dictionaries

• Scripts

• Stored procedures

• SQL

• Modules

• Functions

• Triggers

• Views

• Packages

• Aliases / Synonyms

• It also supports Oracle’s compatibility mode

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

• Db2 Integration Requirements
• Db2 Manual Inputs
• Db2 Resource Configuration

Extraction and Analysis Phase Scenarios

Extraction Phase

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

1. Db2 dictionary mapping scenario — connects to each configured Db2 database and stores the mapping between these values: dictionary ID, host name, instance name, database name, included and excluded schemas

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

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

Analysis Phase

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

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

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

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

Related Articles

• Db2 Reports Error "*RATE_DDL;;SQL0551 Reason Code or Token: READER,CREATE TABLE,SYSTOOLSP

• Db2 Extraction Fails with Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x3. ERRORCODE=-4499, SQLSTATE=58009

• Db2 Extraction Fails with Insufficient data. ERRORCODE=-4499, SQLSTATE=08001

• Db2 Extraction Fails with java.io.CharConversionException, ERRORCODE=-4220, SQLSTATE=null

• Lineage Missing for Tables Created by CTAS Statement

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

• How to Handle Dynamic SQL Scripts

• Db2 Reports Error " *RATE_DDL;;SQL0551 Reason code or token: ...,BIND,NULLID.DB2L"