IBM Db2 LUW Triggers-based Agent for Gluesync: Key Features
Core principles
This agent establishes a connection to the IBM Db2 for LUW via a built-in JDBC driver and it provides Change Data Capture capabilities through a robust auditing structure based on database triggers. This approach offers a reliable way to track changes across your DB2 LUW database tables without requiring complex transaction log configurations.
Key Features
-
Trigger-based auditing system
-
Atomic sequence tracking for row-level changes
-
Minimal setup requirements
-
Compatible with any DB2 LUW version starting from 11.5, community edition included
-
Built-in JDBC driver connection
How It Works
The Triggers agent tracks record changes using:
-
Database triggers that monitor INSERT, UPDATE, and DELETE operations after commit, in transaction with in-memory buffered rows;
-
A dedicated CDC table within the GLUESYNC schema (user-configurable)that stores:
-
Unique row identifiers for changed records;
-
CRUD action types;
-
Minimal metadata thanks to the change tracking technique.
-
Tecnology under the hood
The triggers business logic that powers the DB2 LUW Triggers agent is based on a per-transaction logic, and only tracks changed row IDs, storing data on a table called CDC where all changed row IDs are stored and their data type is maintained unaltered.
The CDC table is populated by the triggers and managed by the agent.
Supported version
With this agent, you can target any version of IBM Db2 for LUW starting from 11.5.
Q&A
I have got DB2 on an i series system, is it supported? IBM Power (AS/400) is supported and requires the usage of a specific Gluesync source connector for IBM Power that makes use of the AS400 built-in journal. To read more about this specific source connector you can follow this link.
I have got DB2 running on z/OS (aka mainframe) is it supported? This specific version has not yet been tested. If you would like to consider helping us with testing in this system please reach out to us by writing at hello@molo17.com.