Source connector

Oracle Database connector

Oracle Database integration for databases, warehouses and BI tools

Oracle Database for enterprise transactional workloads. Datrise captures Oracle Database entities such as tables, rows, schemas, indexes, sequences and redo log changes, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Oracle Database SQL/PL-SQL (LogMiner, Flashback Query, ORA_ROWSCN) authenticates with username / password, mTLS, incremental runs key on ORA_ROWSCN (or a dedicated last-modified column), or an SCN/timestamp range for LogMiner-based log mining.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `oracle_db_tables`) with a schema derived from the Oracle Database API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Oracle Database pipeline page, and join the waitlist to get the Oracle Database connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Oracle Database data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
tables	oracle_db_tables	Upsert by primary key, incremental on updated-at
rows	oracle_db_rows	Upsert by primary key, incremental on updated-at
schemas	oracle_db_schemas	Upsert by primary key, incremental on updated-at
indexes	oracle_db_indexes	Upsert by primary key, incremental on updated-at
sequences	oracle_db_sequences	Upsert by primary key, incremental on updated-at
redo log changes	oracle_db_redo_log_changes	Append-only, incremental by timestamp

Oracle Database API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Oracle Database SQL/PL-SQL (LogMiner, Flashback Query, ORA_ROWSCN)
Authentication	username / password, mTLS — Database-user authentication (password, or Oracle Net native/TCPS with client certificates for mTLS); Oracle Database Vault or OS/Kerberos authentication are also supported for the connecting account.
Pagination	keyset — There is no REST-style page token; extraction jobs page manually with `ROWID`/primary-key ranges or bound a LogMiner session to an SCN or timestamp range via `DBMS_LOGMNR.START_LOGMNR`.
Rate limit	Not published
Incremental cursor	ORA_ROWSCN (or a dedicated last-modified column), or an SCN/timestamp range for LogMiner-based log mining — `ORA_ROWSCN` reflects the system change number of a row's last change but is block-level (coarse) by default, not row-level, unless the table was created with `ROWDEPENDENCIES`.
Webhooks	No
Bulk export	Yes — Oracle Data Pump (expdp/impdp)
Deletes detectable	Yes — LogMiner surfaces `DELETE` operations from redo logs via `V$LOGMNR_CONTENTS.OPERATION`; `ORA_ROWSCN` alone cannot detect deletes since the row no longer exists to query

Official API reference

What bites when replicating Oracle Database

`ORA_ROWSCN` is block-level (coarse) by default and only becomes row-level after creating or rebuilding the table with `ROWDEPENDENCIES`, so a naive high-water-mark sync on an existing table over-fetches unrelated rows in the same block.
`ORA_ROWSCN` is explicitly unsupported for use in Flashback Query (`AS OF SCN`), and it tracks only inserts/updates, not deletes, since a deleted row can no longer be selected to read the pseudocolumn.
LogMiner requires `ALTER DATABASE ADD SUPPLEMENTAL LOG DATA` enabled database-wide before it can reconstruct full `SQL_REDO`/`SQL_UNDO`, and it cannot mine `LONG`, `LONG RAW`, `CLOB`, `BLOB`, `NCLOB`, ADT, or COLLECTION column values via `MINE_VALUE`/`COLUMN_PRESENT`.
Flashback Query depth is bounded by the `UNDO_RETENTION` parameter, which is only a target, not a guarantee — Oracle can overwrite unexpired undo under space pressure, throwing `ORA-01555: snapshot too old` on a long-running or delayed extract.

Compare this against every other documented API

Popular destinations for Oracle Database

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Oracle Database connector FAQ

What Oracle Database data does the connector extract?: 6 objects: tables, rows, schemas, indexes, sequences and redo log changes. Each lands in its own table with types preserved; history-style objects (1: redo log changes) load as append-only streams.
Is the Oracle Database integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Oracle Database data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Oracle Database → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Oracle Database pipeline with guided onboarding

Join the waitlist to get priority access for Oracle Database integrations with guided setup, schema-aware mapping, and production-grade incremental sync.