Oracle to Databricks
real-time replication
TwinCommit replicates Oracle Database to Databricks in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to feed Databricks 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
Databricks
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 Databricks
Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Requirements
- ✓A SQL warehouse or all-purpose cluster
- ✓A Unity Catalog volume or external location for staging
- ✓A service principal with MODIFY on the target schema
Setup
Set up Oracle → Databricks 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 Databricks
Add a target block for Databricks. 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: databricks
host: adb-1234567890.12.azuredatabricks.net
warehouse: replication-wh
catalog: main
schema: replica
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to Databricks replication FAQ
How does TwinCommit replicate Oracle to Databricks?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to Databricks in commit order. Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Does Oracle to Databricks replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to Databricks replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Databricks 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 Databricks today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.