Enterprise Data Catalog Scanner Configuration Guide > Configuring Database Management Resources > IBM DB2
  

IBM DB2

You can configure an IBM DB2 resource type to extract metadata from IBM DB2 databases.

Objects Extracted

Enterprise Data Catalog extracts metadata of the following schema objects from an IBM DB2 resource:

Permissions to Configure the Resource

The following table lists the schema objects and system tables on which you must configure SELECT permissions for the IBM DB2 database user account:
Schema Objects
System Tables
  • - Tables
  • - Views
  • - Indexes
  • - Packages
  • - Procedures
  • - Functions
  • - Sequences
  • - Triggers
  • - Synonyms
  • - SYSCAT.SCHEMATA
  • - SYSCAT.TRIGGERS
  • - SYSCAT.INDEXES
  • - SYSCAT.INDEXCOLUSE
  • - SYSCAT.REFERENCES
  • - SYSCAT.TABCONST
  • - SYSCAT.KEYCOLUSE
  • - SYSCAT.COLCHECKS
  • - SYSCAT.DATATYPES
  • - SYSCAT.COLUMNS
  • - SYSCAT.TABLES
  • - SYSCAT.FUNCTIONS
  • - SYSCAT.PROCEDURES
  • - SYSCAT.PACKAGES
  • - SYSCAT.TRIGGERS
  • - SYSCAT.SEQUENCES
  • - SYSCAT.INDEXES
  • - SYSCAT.CHECKS
  • - SYSCAT.VIEWS
  • - SYSCAT.PACKAGES
  • - SYSCAT.FUNCDEP
  • - SYSCAT.TRIGDEP
  • - SYSCAT.VIEWDEP

Resource Connection Properties

The following table describes the connection properties for the IBM DB2 resource type:
Property
Description
User
Name of the user account that connects to IBM DB2 database.
Password
Password for the user account that connects to IBM DB2 database.
Host
Fully qualified host name of the machine where IBM DB2 database is hosted.
Port
Port number for the IBM DB2 database.
Database
The DB2 connection URL used to access metadata from the database.
The following table describes the Additional and Advanced properties for source metadata settings on the Metadata Load Settings tab:
Property
Description
Enable Source Metadata
Select to extract metadata from the data source.
Import system objects
Specifies the system objects to import.
Schema
Specifies a list of database schema.
Source Metadata Filter
You can include or exclude tables and views from the resource run. Use semicolons (;) to separate the table names and view names.
For more information about the filter field, see Source Metadata and Data Profile Filter.
Import stored procedures
Specifies the stored procedures to import.
Case Sensitive
Specifies that the resource is configured for case insensitivity. Select one of the following values:
  • - True. Select this check box to specify that the resource is configured as case sensitive.
  • - False. Clear this check box to specify that the resource is configured as case insensitive.
The default value is False.
Memory
Specify the memory value required to run a scanner job.
Specify one of the following memory values:
  • - Low
  • - Medium
  • - High
Note: For more information about the memory values, see the Tuning Enterprise Data Catalog Performance article on How To-Library Articles tab in the Informatica Doc Portal
JVM Options
JVM parameters that you can set to configure scanner container. Use the following arguments to configure the parameters:
  • - -Dscannerloglevel=<DEBUG/INFO/ERROR>. Changes the log level of scanner to values, such as DEBUG, ERROR, or INFO. Default value is INFO.
  • - -Dscanner.container.core=<No. of core>. Increases the core for the scanner container. The value should be a number.
  • - -Dscanner.yarn.app.environment=<key=value>. Key pair value that you need to set in the Yarn environment. Use a comma to separate the key pair value.
  • - -Dscanner.pmem.enabled.container.memory.jvm.memory.ratio=<1.0/2.0>. Increases the scanner container memory when pmem is enabled. Default value is 1.
  • - -DskipExternalDatabaseObjects=true. Excludes all external objects such as schema, table, database and view.
Track Data Source Changes
View metadata source change notifications in Enterprise Data Catalog.
You can enable data discovery for an IBM DB2 resource. For more information about enabling data discovery, see the Enable Data Discovery topic.
You can enable composite data domain discovery for an IBM DB2 resource. For more information about enabling composite data domain discovery, see the Composite Data Domain Discovery topic.