Oracle to BigQuery
real-time replication
TwinCommit replicates Oracle Database to Google BigQuery in real time by reading the Oracle transaction log and applying every committed change exactly once and in commit order. Use it to feed BigQuery 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
BigQuery
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 BigQuery
Changes stream through the BigQuery Storage Write API into staging tables and are applied with MERGE on a configurable interval, so deletes and updates are reflected exactly.
Requirements
- ✓A service account with BigQuery Data Editor and Job User
- ✓A dataset for staging tables
- ✓Primary keys declared on target tables (recommended)
Setup
Set up Oracle → BigQuery 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 BigQuery
Add a target block for BigQuery. 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: bigquery
project: acme-analytics
dataset: replica
credentials_file: /secrets/bq.json
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]Oracle to BigQuery replication FAQ
How does TwinCommit replicate Oracle to BigQuery?
+
TwinCommit reads changes from the Oracle transaction log, buffers them per transaction, and applies each committed transaction to BigQuery in commit order. Changes stream through the BigQuery Storage Write API into staging tables and are applied with MERGE on a configurable interval, so deletes and updates are reflected exactly.
Does Oracle to BigQuery replication need triggers or capture tables?
+
No. TwinCommit reads the Oracle log directly and creates no objects in the source database.
Is Oracle to BigQuery replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same BigQuery 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 BigQuery today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.