IBM Db2
change data capture
TwinCommit captures changes from IBM Db2 by reading its transaction log directly, then delivers each committed transaction exactly once to any supported target. Db2 LUW and Db2 for z/OS, read straight from the recovery log.
IBM Db2
Db2 LUW 11.1, 11.5, 12.1 · Db2 for z/OS 12 and 13 · Db2 on Cloud (target)
- ✓Archive logging enabled (LOGARCHMETH1)
- ✓DATA CAPTURE CHANGES on each replicated table
- ✓A primary key or unique index on each replicated table
- ✓DBADM (or SYSADM) for the capture user
Capture
How TwinCommit reads Db2
TwinCommit reads the Db2 recovery log through the native log read API and decodes row images itself. No SQL Replication, no Q Replication, no CD tables, no triggers and no capture agents are installed on the source.
Db2 source docs →Apply
How TwinCommit writes to Db2
Array MERGE statements committed in the same unit of work as the TwinCommit checkpoint.
Db2 target docs →Replicate Db2 to…
Db2 connector FAQ
Which Db2 versions does TwinCommit support?
+
Db2 LUW 11.1, 11.5, 12.1 · Db2 for z/OS 12 and 13 · Db2 on Cloud (target).
Does TwinCommit install anything in Db2?
+
No. TwinCommit reads the Db2 log and creates no triggers, tables or procedures in the source database.
How does TwinCommit write to Db2?
+
Array MERGE statements committed in the same unit of work as the TwinCommit checkpoint.
Replicate your first table in five minutes.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.