Oracle to Elasticsearch
real-time replication
TwinCommit replicates Oracle Database to Elasticsearch in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to keep Elasticsearch search indexes current with Oracle, with no triggers or capture tables on the source.
Oracle
log reader
commit-ordered · exactly-once
Elasticsearch
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 Elasticsearch
Changes are sent through the _bulk API with the document ID set to the primary key and external versioning derived from the log position, so late or replayed writes can never overwrite newer data.
Requirements
- ✓An index template or mapping per table
- ✓API key with index and write privileges
- ✓TLS endpoint
Setup
Set up Oracle → Elasticsearch 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 Elasticsearch
Add a target block for Elasticsearch. 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: elasticsearch
url: https://search.internal:9200
api_key: ${ES_API_KEY}
index_template: "{schema}-{table}"
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to Elasticsearch replication FAQ
How does TwinCommit replicate Oracle to Elasticsearch?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to Elasticsearch in commit order. Changes are sent through the _bulk API with the document ID set to the primary key and external versioning derived from the log position, so late or replayed writes can never overwrite newer data.
Does Oracle to Elasticsearch replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to Elasticsearch replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Elasticsearch 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 Elasticsearch today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.