Db2 to Hive
real-time replication
TwinCommit replicates IBM Db2 to Apache Hive in real time by reading the Db2 transaction log and applying every committed change exactly once and in commit order. Use it to feed Hive 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
Hive
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 Hive
Changes are written as ORC delta files and committed with Hive ACID MERGE, or as Iceberg snapshots through the Hive Metastore, depending on table format.
Requirements
- ✓Transactional (ACID) tables or Iceberg tables
- ✓HiveServer2 JDBC endpoint
- ✓Write access to the warehouse location
Setup
Set up Db2 → Hive 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 Hive
Add a target block for Hive. 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: hive
jdbc_url: jdbc:hive2://hs2.internal:10000/default
table_format: iceberg
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Db2 to Hive replication FAQ
How does TwinCommit replicate Db2 to Hive?
+
TwinCommit reads changes from the Db2 transaction log, buffers them per transaction, and applies each committed transaction to Hive in commit order. Changes are written as ORC delta files and committed with Hive ACID MERGE, or as Iceberg snapshots through the Hive Metastore, depending on table format.
Does Db2 to Hive replication need triggers or capture tables?
+
No. TwinCommit reads the Db2 log directly and creates no objects in the source database.
Is Db2 to Hive replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Hive 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 Hive today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.