Oracle to Hive
real-time replication
TwinCommit replicates Oracle Database to Apache Hive in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to feed Hive with live Oracle data for analytics, AI and reporting, with no triggers or capture tables on the source.
Oracle
log reader
commit-ordered · exactly-once
Hive
native writer
How capture works on Oracle
TwinCommit parses online redo and archived logs directly, including RAC threads, and reassembles transactions in SCN order before they leave the host.
Prerequisites
- ✓ARCHIVELOG mode
- ✓Minimal plus primary-key supplemental logging
- ✓Read access to V$ views and the archive destination
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 Oracle → Hive in four steps
- 1
Prepare Oracle
Run twincommit check. It verifies archivelog mode 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: oracle
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]Oracle to Hive replication FAQ
How does TwinCommit replicate Oracle to Hive?
+
TwinCommit reads changes from the Oracle 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 Oracle to Hive replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle 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 Oracle versions are supported?
+
Oracle 19c, 21c, 23ai · RAC, Data Guard standby, CDB/PDB · Autonomous Database (target).
Use cases for this route
Related replication routes
Stream Oracle to Hive today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.