Oracle to Snowflake
real-time replication
TwinCommit replicates Oracle Database to Snowflake in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to feed Snowflake 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
Snowflake
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 Snowflake
Rows land through Snowpipe Streaming into a change table and are merged into the target on a short, configurable interval.
Requirements
- ✓Key-pair authentication for a service user
- ✓A warehouse for the MERGE step
- ✓OWNERSHIP or INSERT/UPDATE/DELETE on the target schema
Setup
Set up Oracle → Snowflake 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 Snowflake
Add a target block for Snowflake. 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: snowflake
account: myorg-myaccount
warehouse: REPLICATION_WH
database: RAW
private_key_file: /secrets/sf.p8
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to Snowflake replication FAQ
How does TwinCommit replicate Oracle to Snowflake?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to Snowflake in commit order. Rows land through Snowpipe Streaming into a change table and are merged into the target on a short, configurable interval.
Does Oracle to Snowflake replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to Snowflake replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Snowflake 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).
Stream Oracle to Snowflake today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.