Oracle Resource Configuration

oracle.dictionary.id

Name of a resource representing this Oracle database known as the dictionary ID, used as an output subdirectory name for extracted DDL files and the database dictionary

OracleODS

oracle.username

Name of the user for connection to the Oracle database

manta_user

oracle.extractedSchemas

List of schemas to extract, separated by commas, or leave blank to extract all schemas; supports regular expressions; the matching is case-sensitive

Schema1,Schema2,Schema3,Schema_.*

oracle.excludedEntities

Specify the entities to exclude from extraction. The filter input is divided into two parts by a semicolon ( ; ). 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, materialized_view, package, package_body, type, type_body, procedure, function, trigger, sequence, synonym, or database_link. Multiple entity types should be separated by a | .

Note: Specifying package or type, etc. will automatically exclude also package_body or type_body, respectively. The reverse is also true, specifying package_body will automatically exclude package, etc.

2. Name pattern: is evaluated as a regular expression to match object name (regardless of schema that the object is in) or schema/objectname to limit the schema as well.

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.

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

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

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

oracle.ddl.encoding

Encoding of automatically extracted Oracle DDL scripts. See Encodings for applicable values.

utf8

oracle.dictionary.dir

Directory with data dictionaries extracted from Oracle

${manta.dir.temp}/oracle

oracle.dll.output

Directory for automatically extracted Oracle DDL scripts (for the extraction phase)

${manta.dir.temp}/oracle/

${oracle.dictionary.id}/ddl

oracle.script.input

Directory with manually provided PL/SQL scripts which are performed on this Oracle database instance (for the analysis phase)

${manta.dir.input}/oracle/

${oracle.dictionary.id}/

oracle.script.replace.regex

Flag specifying whether replacements for PL/SQL scripts in the provided CSV file specified in oracle.script.replace should be interpreted as regular expressions (true) or simple text (false)

false
true

oracle.synonymProcessing

Toggles synonym visibility; set to READ_ONLY to show synonyms or TRANSPARENT to connect the lineage directly to the synonyms' targets

READ_ONLY
TRANSPARENT

oracle.dictionary.mappingManualFile

Path to mappings provided manually for Oracle databases

${manta.dir.scenario}/conf/

oracleDictionaryMantaMappingManual.csv

oracle.dynamicSql.enabled.plsql

Enables or disables dynamic SQL processing in PL/SQL scripts

false
true

oracle.expressionDescriptions.enabled.plsql

Enables or disables building transformation logic descriptions from SQL code in PL/SQL scripts

false
true

oracle.includeSchemaDependencies

Enables or disables the extraction of dependencies from non-included schemas (non-transitive)

Synonyms pointing into non-extracted schemas are only extracted if this flag is set to true

false
true

oracle.instanceNameQuery

Query to get the name of the database that affects what is displayed in Manta and used in exports

select sys_context('userenv', 'instance_name') from dual

select name from v$database

custom

oracle.extractorScenario.inputReader

Set the extraction mode to scenarioReaderPrefetch (default) to use the prefetch extractor, to scenarioReader to use the legacy single thread extractor, or to scenarioReaderParallelBulk to use the bulk extractor

scenarioReaderPrefetch
scenarioReader
scenarioReaderParallelBulk

oracle.prefetchExtractor.bufferSize

Size of the prefetch buffer used by the prefetch extractor

The bufferSize is the number of prefetched scripts, and the occupied RAM depends on the content of the scripts; for example, if the bufferSize is 100 and the average script size is 10KB, the total occupied RAM is 1 MB

• Impact: higher values allow a bigger buffer, consuming more RAM in CLI

• Minimum: 1

• Maximum: depends on the available RAM

• Recommended setting is 100–1000

100

oracle.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