Db2 to Redshift
real-time replication
TwinCommit replicates IBM Db2 to Amazon Redshift in real time by reading the Db2 transaction log and applying every committed change exactly once and in commit order. Use it to feed Redshift with live Db2 data for analytics, AI and reporting, with no triggers or capture tables on the source.
Db2
log reader
commit-ordered · exactly-once
Redshift
native writer
How capture works on 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.
Prerequisites
- ✓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
How apply works on Redshift
Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Requirements
- ✓An S3 staging bucket and IAM role for COPY
- ✓A database user with CREATE on the target schema
- ✓Network path to the cluster or workgroup endpoint
Setup
Set up Db2 → Redshift in four steps
- 1
Prepare Db2
Run twincommit check. It verifies archive logging enabled (logarchmeth1) and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Redshift
Add a target block for Redshift. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: db2
database: PRODDB
user: ${SRC_USER}
password: ${SRC_PASSWORD}
target:
type: redshift
host: analytics.123456789.us-east-1.redshift-serverless.amazonaws.com
database: dev
staging_bucket: s3://acme-twincommit-staging
iam_role: arn:aws:iam::123456789012:role/twincommit-copy
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Db2 to Redshift replication FAQ
How does TwinCommit replicate Db2 to Redshift?
+
TwinCommit reads changes from the Db2 transaction log, buffers them per transaction, and applies each committed transaction to Redshift in commit order. Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Does Db2 to Redshift replication need triggers or capture tables?
+
No. TwinCommit reads the Db2 log directly and creates no objects in the source database.
Is Db2 to Redshift replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Redshift transaction as the data, so a crash or restart never loses or duplicates a transaction.
What Db2 versions are supported?
+
Db2 LUW 11.1, 11.5, 12.1 · Db2 for z/OS 12 and 13 · Db2 on Cloud (target).
Stream Db2 to Redshift today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.