Oracle to ADLS
real-time replication
TwinCommit replicates Oracle Database to Azure Data Lake Storage in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to land live Oracle data in ADLS as open Delta Lake or Iceberg tables, with no triggers or capture tables on the source.
Oracle
log reader
commit-ordered · exactly-once
ADLS
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 ADLS
Each micro-batch becomes one atomic Delta Lake or Apache Iceberg commit (or Parquet files) with the checkpoint stored in the commit itself. Use merge mode to mirror current state, or append mode for a full change history.
Requirements
- ✓Storage Blob Data Contributor on the container
- ✓Hierarchical namespace enabled
- ✓Optional Iceberg catalog (REST or Hive Metastore)
Setup
Set up Oracle → ADLS 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 ADLS
Add a target block for ADLS. 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: adls
account: acmelake
container: lake
path: replica/{schema}/{table}
format: delta
mode: merge
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to ADLS replication FAQ
How does TwinCommit replicate Oracle to ADLS?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to ADLS in commit order. Each micro-batch becomes one atomic Delta Lake or Apache Iceberg commit (or Parquet files) with the checkpoint stored in the commit itself. Use merge mode to mirror current state, or append mode for a full change history.
Does Oracle to ADLS replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to ADLS replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same ADLS 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 ADLS today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.