Integrations · Databases · Available now
IBM Db2 test data, inside your network
Db2 for Linux, UNIX and Windows connector using IBM's driver installed by the customer: SYSCAT catalog discovery, primary and foreign keys, statistics-based row estimates, bounded profiles and streaming reads into the local engine, over TLS by default.
Available now Databases
Shipped in the standard agent and backed by recorded conformance evidence.
Customer-installed driver. The IBM Db2 driver (ibm_db 3.3.0) is licensed by its vendor under the IBM License Information L-WNKS-F8PR3U for IBM Data Server Driver for ODBC and CLI 12.1.4 (ibm_db itself: Apache-2.0), which does not allow DataNivra to redistribute it, so the standard agent image does not include it. You install it by building the agent extension image; building it means you accept that licence.
What works today
Db2 for Linux, UNIX and Windows connector using IBM's driver installed by the customer: SYSCAT catalog discovery, primary and foreign keys, statistics-based row estimates, bounded profiles and streaming reads into the local engine, over TLS by default.
Customer-installed driver: IBM's driver includes components IBM does not allow DataNivra to redistribute, so you build DataNivra's extension image, which installs IBM's pinned ibm_db wheel (with IBM's CLI driver and its licence files) on top of a released agent image under IBM's terms that you accept. No Db2 Connect licence is included. Password as a secret reference; SECURITY=SSL by default.
Authentication: user and password (secret reference).
Known limitations
- Customer-installed driver: the standard agent image does not include ibm_db. Build the DataNivra agent extension image (agent/runtime/extensions/ibm-db2), which installs ibm_db and IBM's CLI driver under IBM's licence terms that you accept; without it the agent reports CONNECTOR_NOT_AVAILABLE.
- Linux/amd64 agents only: IBM publishes no Linux arm64 CLI driver, so an arm64 agent reports CONNECTOR_PLATFORM_UNSUPPORTED.
- User and password authentication only (no Kerberos, LDAP plug-ins or trusted contexts).
- Db2 for LUW only; Db2 for z/OS and Db2 for i are not supported. Connecting to them through IBM's driver would also need your own Db2 Connect licence, which DataNivra never ships.
- XML columns are read as serialized text; structured and spatial user-defined types are refused with a reason code.
Capability matrix
Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.
| Capability | Level |
|---|---|
| Discovery | Supported |
| Classification | Supported |
| Profiling | Supported |
| Masking | Supported |
| Deterministic masking | Supported |
| Entity-aware subsetting | Supported |
| Relationship preservation | Supported |
| Synthetic workflows | Supported |
| Certification | Supported |
| Provisioning | Supported |
| CI/CD | Supported |
| Evidence generation | Supported |
Read-only proof
Proven from Db2's authorization catalog before reading, across the user, PUBLIC, the user's groups and roles: AUTH_LIST_AUTHORITIES_FOR_AUTHID may show only CONNECT and EXPLAIN; SYSCAT.TABAUTH only SELECT and REFERENCES; SYSCAT.SCHEMAAUTH only SELECTIN; SYSCAT.DBAUTH only CONNECT and EXPLAIN; and the user must own no table.
Conformance evidence
DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.
| Engine or service | Version | Environment | Driver | Authentication | Verified on |
|---|---|---|---|---|---|
| IBM Db2 Community Edition (container) | DB2 v11.5.9.0 | real-engine | ibm_db (IBM CLI driver, customer-installed) 3.3.0 | password | 2026-10-13 |
Connector version 0.1.0, last verified 2026-10-13.
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Setup outline
- Customer-installed driver: build the DataNivra agent extension image for IBM Db2 (agent/runtime/extensions/ibm-db2, guide at /docs/agent-extension-images). It installs IBM’s hash-pinned ibm_db wheel, which carries IBM’s CLI driver and licence files, under IBM’s terms that you accept; DataNivra does not ship it. Without it the agent reports CONNECTOR_NOT_AVAILABLE.
- Run that image on linux/amd64: IBM publishes no Linux arm64 driver, so an arm64 agent reports CONNECTOR_PLATFORM_UNSUPPORTED.
- No Db2 Connect licence is included, and Db2 for z/OS and IBM i are not supported (they would also need your own Db2 Connect licence).
- Grant a dedicated user CONNECT and SELECT (or SELECTIN on the schema) only, and revoke the CREATETAB, BINDADD and IMPLICIT_SCHEMA authorities a non-restrictive database gives PUBLIC.
- Store the connection document with the password as a secret reference. SECURITY=SSL is the default; plain TCP must be chosen explicitly.
- In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
- Before reading, the agent proves the user is read-only from Db2’s authorization catalog (user, PUBLIC, groups and roles) and refuses to continue if it is not.
Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):
{
"kind": "IBM_DB2",
"host": "claims-db2.db.example.internal",
"port": 50001,
"database": "CLAIMS",
"user": "tdmread",
"password_ref": "vault://tdm/claims-db2#password",
"ssl_server_certificate": "/etc/datanivra/db2-ca.pem",
"schemas": ["CLAIMS"]
}Next: install the agent, then follow the getting started guide.
All integrations · Database test data management · Guides · Start free