Oracle to Redis
real-time replication
TwinCommit replicates Oracle Database to Redis in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to keep a Redis cache exactly in sync with Oracle, with no triggers or capture tables on the source.
Oracle
log reader
commit-ordered · exactly-once
Redis
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 Redis
Each row is written as a Redis hash (or JSON document) under a key template such as `orders:{ORDER_ID}`, with deletes removing the key. Optionally every change is also appended to a Redis Stream.
Requirements
- ✓A key template per table
- ✓ACL user with write access to the key prefix
- ✓TLS endpoint recommended
Setup
Set up Oracle → Redis 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 Redis
Add a target block for Redis. 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: redis
url: rediss://cache.internal:6380
key_template: "{table}:{pk}"
format: hash
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to Redis replication FAQ
How does TwinCommit replicate Oracle to Redis?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to Redis in commit order. Each row is written as a Redis hash (or JSON document) under a key template such as orders:{ORDER_ID}, with deletes removing the key. Optionally every change is also appended to a Redis Stream.
Does Oracle to Redis replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to Redis replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Redis 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 Redis today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.