Db2 Resource Configuration

db2.subdialect

Type of Db2 server used; the supported values are "ZOS" for Db2 for z/OS and "DB2" for all other Db2 servers

DB2

db2.username

Name of user with the specified privileges needed for extraction

manta_user

db2.extractedSchemas

List of schemas to extract, separated by commas; each part is evaluated as a regular expression

Schema1,Schema2,Schema3,test_.*

db2.extraction.method

Set to Agent:default when the desired extraction method is the default Manta Extractor Agent, set to Agent:{remote_agent_name} when a remote Agent is the desired extraction method, set to Git:{git.dictionary.id} when the Git ingest method is the desired extraction method. For more information on setting up a remote extractor Agent please refer to the Manta Flow Agent Configuration for Extraction documentation. For additional details on configuring a Git ingest method, please refer to the Manta Flow Agent Configuration for Extraction:Git Source documentation.

default

Git

agent

db2.script.encoding

Encoding of manually provided PL/SQL scripts performed on this Db2 database instance. See Encodings for applicable values.

utf8

db2.excludedEntities

Specify the entities to exclude from extraction. The filter input is divided into two parts by a semicolon character ; . Each filter follows the same format of (Entity Types;)?Name Pattern.

1. Entity types (optional): The first part lists the types of entities to exclude. These can include table, view, type, procedure, function, trigger, sequence, synonym, or database_link. Multiple entity types should be separated by a | character .

2. Name pattern: The second part of the field is a name pattern that matches the entity names to be excluded. This pattern can be either a single name (for any database and any schema), a schema and a name separated by a / (for any database) or a database, schema and name separated by / (see examples).

Both parts of the filter expression are case-insensitive.

You can specify multiple filters by separating them with a comma ,.

If a non-filtered entity (e.g., a view) points to a filtered entity (e.g., a table), the filtered entity will still appear as a deduced item (available as of Manta R42.6).

• temp_.*: Excludes all objects whose name starts with temp_, regardless of their type, database or schema

• function;abc.*: Excludes functions whose name starts with abc, regardless of their database or schema

• table|view;dw.*/.*,function|procedure;abc.*/def.*/ghi.*: Excludes every table and every view from schemas that start with 'dw' of all databases and every function and procedure whose name starts with 'ghi' from schemas that start with 'def' of databases that start with 'abc'

filepath.lowercase

Whether paths to files should be lowercase (false for case-sensitive file systems, true otherwise)

false
true

db2.ddl.input

Directory with automatically extracted Db2 DDL scripts (for the analysis phase)

${db2.dll.output}

db2.script.replace

Path to the CSV file with the replacements to be applied to the provided PL/SQL scripts; see Placeholder Replacement in Input Scripts for details about the replacement file format

${manta.dir.input}/db2/
${db2.dictionary.id}/replace.csv

db2.analyze.parallelCount

Number of parallel threads which will analyze DDL and PL/SQL

4

db2.dictionary.mappingManualFile

Path to mappings provided manually for Db2 databases

${manta.dir.scenario}/conf/

db2DictionaryMantaMappingManual.csv

db2.analyze.retainUnusedResultSetColumns

Flag specifying whether the data lineage should include sub-query resultset columns that do not have any downstream lineage

By default, set to false

false
true

Host name

Name of the host where the database is running

localhost
127.0.0.1

Database name

Name of the database

SAMPLE

Include schemas

List of schemas to extract, separated by commas; each part is evaluated as a regular expression

Schema1,Schema2,Schema3,test_.*