Oracle to S3
real-time replication
TwinCommit replicates Oracle Database to Amazon S3 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 S3 as open Delta Lake or Iceberg tables, with no triggers or capture tables on the source.
Oracle
log reader
commit-ordered · exactly-once
S3
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 S3
Changes land as Apache Iceberg, Delta Lake or Parquet tables, one atomic commit per micro-batch with the checkpoint in the snapshot metadata. Iceberg tables register in AWS Glue or Amazon S3 Tables automatically.
Requirements
- ✓IAM role with s3:GetObject, PutObject, DeleteObject and ListBucket on the prefix
- ✓Glue catalog permissions for table registration
- ✓Same-region placement recommended
Setup
Set up Oracle → S3 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 S3
Add a target block for S3. 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: s3
bucket: acme-lake
path: replica/{schema}/{table}
format: iceberg
catalog: { type: glue, database: replica }
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to S3 replication FAQ
How does TwinCommit replicate Oracle to S3?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to S3 in commit order. Changes land as Apache Iceberg, Delta Lake or Parquet tables, one atomic commit per micro-batch with the checkpoint in the snapshot metadata. Iceberg tables register in AWS Glue or Amazon S3 Tables automatically.
Does Oracle to S3 replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to S3 replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same S3 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 S3 today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.