metadata-ingestion/docs/sources/db2/db2_post.md
Use the Important Capabilities table above as the source of truth for supported features and whether additional configuration is required.
This source can connect to Db2 for IBM i (AS/400) directly using the IBM i Access ODBC Driver rather than using the default CLI driver that requires Db2 Connect.
This requires you to install the IBM i Access ODBC Driver along with an ODBC driver manager such as unixodbc.
To use the IBM i Access ODBC Driver rather than the default driver, specify the db2+pyodbc400 scheme in your ingestion configuration:
scheme: "db2+pyodbc400"
If you're using DataHub Cloud's Remote Executor, you can either build a custom image with the ODBC driver included, or sideload the driver. For instance, to sideload the driver and when using the Remote Executor Helm chart, you might use the following Helm values file:
extraInitContainers:
- name: init-db2-as400-driver
image: debian:stable-slim
command:
- bash
- -c
- |
set -euxo pipefail
apt-get update
apt-get install -y wget
wget -P /etc/apt/sources.list.d/ https://public.dhe.ibm.com/software/ibmi/products/odbc/debs/dists/1.1.0/ibmi-acs-1.1.0.list
apt-get update
apt-get install -y ibm-iaccess
cp /etc/odbcinst.ini /opt/ibm
volumeMounts:
- name: ibmdriver
mountPath: "/opt/ibm"
extraVolumes:
- name: ibmdriver
emptyDir: {}
extraVolumeMounts:
- name: ibmdriver
mountPath: "/opt/ibm"
readOnly: true
nodeSelector:
kubernetes.io/arch: amd64
Then configure your source to set the following environment variables:
LD_LIBRARY_PATH="/opt/ibm/iaccess/lib64/"
ODBCSYSINI="/opt/ibm"
Module behavior is constrained by source APIs, permissions, and metadata exposed by the platform. Refer to capability notes for unsupported or conditional features.
The Db2 source is available on Linux x86_64, macOS x86_64, and macOS ARM. It is not available on Linux ARM, and attempting to execute the source will result in an error.
This source has been tested against:
acryl-datahub[db2] package)This source also includes nominal support for:
If ingestion fails, validate credentials, permissions, connectivity, and scope filters first. Then review ingestion logs for source-specific errors and adjust configuration accordingly.