Integrations · Databases · Available now
IBM Informix test data, inside your network
Informix connector over DRDA using IBM's driver installed by the customer: system catalog discovery, primary and foreign keys, statistics-based row estimates, bounded profiles and streaming reads into the local engine, over verified TLS by default.
Available now Databases
Shipped in the standard agent and backed by recorded conformance evidence.
Customer-installed driver. The IBM Informix 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
Informix connector over DRDA using IBM's driver installed by the customer: system catalog discovery, primary and foreign keys, statistics-based row estimates, bounded profiles and streaming reads into the local engine, over verified TLS by default.
Customer-installed driver: IBM's driver includes components IBM does not allow DataNivra to redistribute, so you build DataNivra's IBM extension image (the same one as for IBM Db2), which installs IBM's pinned ibm_db wheel on top of a released agent image under IBM's terms that you accept. Connects to the server's DRDA listener; password as a secret reference; TLS with certificate and host-name verification by default.
Authentication: user and password (secret reference).
Known limitations
- Requires agent 0.4.3 or later: agent 0.4.2 and earlier do not contain the Informix connector, so build the IBM extension image FROM that release's digest.
- Customer-installed driver: the standard agent image does not include ibm_db. Build the DataNivra agent extension image (agent/runtime/extensions/ibm-db2, shared with 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.
- Needs a DRDA listener on the server (drsocssl for TLS, drsoctcp without) and a logged database; the SQLI protocol is not used.
- A non-ANSI database gives PUBLIC write privileges on every new table, Select on every new sequence and Execute on every new routine; the read-only proof refuses the source until you revoke them (or create objects with NODEFDAC=yes).
- User and password authentication only (no Kerberos, PAM challenge or single sign-on).
- SET, MULTISET, LIST, ROW and user-defined types are read as their text form.
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 the database's privilege catalog before reading, across the user, PUBLIC and every role granted to them: sysusers may show only Connect (DBA and Resource refuse); systabauth and syscolauth only Select and References; no fragment privileges, no privilege on a sequence and no Execute on a user-defined routine; the user owns no table and has no access to the sysadmin database.
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 Informix Developer Edition (container) | 15.0.1.0.3DE | real-engine | ibm_db (IBM CLI driver over DRDA, 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
- Use agent 0.4.3 or later (agent 0.4.2 and earlier do not contain the Informix connector), and build the extension image FROM that release’s digest.
- Customer-installed driver: build the DataNivra agent extension image for IBM (agent/runtime/extensions/ibm-db2, the same image as for 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.
- The agent connects to the server’s DRDA listener: add a drsocssl entry (TLS) to sqlhosts and DBSERVERALIASES if the server has none. The database must be logged.
- Grant a dedicated operating-system user CONNECT and SELECT only. A non-ANSI database gives PUBLIC write privileges on every new table, Select on every new sequence and Execute on every new routine: revoke them (REVOKE ALL ON <table> FROM PUBLIC AS <owner>), or create objects with NODEFDAC=yes.
- Store the connection document with the password as a secret reference and the server’s CA (or self-signed) certificate as ssl_server_certificate. TLS with host-name verification 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 the database’s privilege catalog (user, PUBLIC and their 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_INFORMIX",
"host": "claims-ifx.db.example.internal",
"port": 9089,
"database": "claims",
"user": "tdmread",
"password_ref": "vault://tdm/claims-informix#password",
"ssl_server_certificate": "/etc/datanivra/informix-ca.arm",
"schemas": ["claims"]
}Next: install the agent, then follow the getting started guide.
All integrations · Database test data management · Guides · Start free