Oracle to Redshift
real-time replication
TwinCommit replicates Oracle Database to Amazon Redshift in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to feed Redshift 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
Redshift
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 Redshift
Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Requirements
- ✓An S3 staging bucket and IAM role for COPY
- ✓A database user with CREATE on the target schema
- ✓Network path to the cluster or workgroup endpoint
Setup
Set up Oracle → Redshift 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 Redshift
Add a target block for Redshift. 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: redshift
host: analytics.123456789.us-east-1.redshift-serverless.amazonaws.com
database: dev
staging_bucket: s3://acme-twincommit-staging
iam_role: arn:aws:iam::123456789012:role/twincommit-copy
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to Redshift replication FAQ
How does TwinCommit replicate Oracle to Redshift?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to Redshift in commit order. Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Does Oracle to Redshift replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to Redshift replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Redshift 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 Redshift today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.