IBM DB2
This connector support IBM DB2 for i-series (as400) and IBM DB2 for z/OS databases. IBM DB2 for LUW is partially supported. The default import query that Katalogue uses has been tested on IBM DB2 for i-series version 11 and z/OS. A custom import query is required to make this connector work with IBM DB2 for LUW databases.
Installation
Section titled “Installation”The IBM DB2 connector need some attention to install correctly. See the api/Dockerfile for more information. It might also require a IBM DB2 license file to work if the IBM DB2 server is not configured with server side licensing. More info: https://www.npmjs.com/package/ibm_db
Configuration
Section titled “Configuration”Code page and special characters encoding
Section titled “Code page and special characters encoding”On some occasions, special characters like “åäö” get wrong encoding when importing data to Katalogue. If this happens, the code page of the connector must be configured to match the source database.
The code page is configured in the GUI, in the Settings -> Connectors -> IBM DB2 section. See https://www.ibm.com/docs/en/db2/11.5?topic=support-supported-territory-codes-code-pages for available code pages
Note that this setting applies globally to all IBM DB2 connections in Katalogue, i.e. setting a specific code page configuration for each IBM DB2 connection is currently not supported.
Required Permissions
Section titled “Required Permissions”By default, Katalogue requires read access to the following resources.
Note that other permissions might be required if custom import queries are used.
SYSIBM.SYSCOLUMNSSYSIBM.SYSTABLESSYSIBM.SYSVIEWSSYSIBM.SYSDATABASESYSIBM.SYSTABLESPACESYSIBM.SYSTABLESPACESTATSSYSIBM.SYSFOREIGNKEYSSYSIBM.SYSRELS
i-series (as400)
Section titled “i-series (as400)”INFORMATION_SCHEMA.CATALOG_NAMEINFORMATION_SCHEMA.COLUMNSINFORMATION_SCHEMA.SCHEMATAINFORMATION_SCHEMA.VIEWSQSYS2.SYSCOLUMNSQSYS2.SYSTABLESQSYS2.SYSSCHEMASQSYS2.SYSCATALOGSQSYS2.SYSTABLESTATQSYS2.SYSCSTQSYS2.SYSCSTCOLQSYS2.SYSKEYCSTQSYS2.SYSREFCST
Unknown
Usage Notes
Section titled “Usage Notes”DB2 z/OS max column length is set to 30. This means that we cannot use e.g. the Katalogue column name “dataset_technical_definition_raw” (32 characters) for z/OS connections. References: https://www.ibm.com/docs/en/db2-for-zos/13.0.0?topic=db2-catalog-tables
Limitations
Section titled “Limitations”Max column length
Section titled “Max column length”DB2 z/OS max column length is set to 30. This means that we cannot use e.g. the Katalogue column name “dataset_technical_definition_raw” (32 characters) for z/OS connections. References: https://www.ibm.com/docs/en/db2-for-zos/13.0.0?topic=db2-catalog-tables
Lineage
Section titled “Lineage”This connector does not provide dataset/table lineage out of the box as this is missing in the information schema tables.
i-series (as400)
Section titled “i-series (as400)”Source Ids
Section titled “Source Ids”The source ids for views, tables etc is not synced. This means that the connector cannot handle table renames optimally (i.e. with an update). Instead, a renamed table causes a delete/insert, which means that any references to the table will be lost in the sync. The source ids are missing since they are not made available in the DB2 information schema tables.
Lineage
Section titled “Lineage”This connector does not provide dataset/table lineage out of the box as this is missing in the information schema tables.