Oracle Database Connector

Extract Oracle Database tables with full refresh or cursor-based incremental sync. Connect by service name with optional lookback for late-arriving rows.

SourceCommunity

Start for Free View Documentation

Evaluating against Fivetran? See how Supaflow handles Oracle Database pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Full Refresh and Incremental Sync

Use full refresh for smaller or static tables, or cursor-based incremental sync for tables with reliable date or timestamp-style columns. The connector does not use Oracle CDC, redo logs, LogMiner, GoldenGate, XStream, or Flashback.

Oracle Service-Name Connection

Configure Host, Port, User, Password, and Service Name. Each source connects to one Oracle service, with port 1521 as the default.

Source-Load-Aware Reads

Initial syncs and full refreshes run SQL reads against selected Oracle tables. Use incremental sync, focused table selection, and off-peak schedules to manage production database load.

Incremental Lookback Window

Configure a lookback period up to 24 hours so incremental syncs re-read a short window before the previous cursor position when writes can arrive out of order.

Supported Objects

Database Objects

Tables

Tables in the Oracle schema associated with the connecting user that the user has permission to read.

How It Works

Prepare Oracle access

Connect as the Oracle schema/user whose tables you want to sync. The user needs CREATE SESSION and read access to selected tables. If your database restricts inbound access, allow Supaflow IP 18.214.240.61 or use your approved private network path.

Enter connection details

Provide the Oracle host, port (default 1521), user, password, and Service Name. Use an Oracle service name, not a SID, TNS alias, wallet name, or full connection string.

Choose sync behavior

Select tables in your pipeline and use full refresh or cursor-based incremental sync. For incremental sync, choose a cursor column that advances when rows are inserted or updated.

Test and save

Click Test & Save to verify the connection. Supaflow discovers accessible tables in the connected Oracle schema and refreshes metadata according to the schema refresh interval.

Use Cases

Oracle analytics replication

Sync operational Oracle tables into your warehouse for analytics without running heavy reporting queries against production.

Database workload offloading

Move recurring reporting reads out of Oracle by loading selected tables into an analytics environment.

Incremental warehouse updates

Use cursor-based incremental sync for large tables that have reliable updated-at style columns.

Frequently Asked Questions

How do I connect Supaflow to an on-premises Oracle database?

For production, deploy a self-hosted Docker Agent on a stable host inside the same private network as Oracle. The agent connects to the Oracle listener over the private network and polls Supaflow over outbound HTTPS, so the database port stays private. For a quick proof-of-concept connectivity test, a temporary TCP tunnel can work; the linked SQL Server walkthrough demonstrates the network pattern, but you must use the Oracle listener port and follow your Oracle authentication and network-security requirements.

Deploy a self-hosted Docker Agent See the temporary TCP tunnel pattern

Does the Oracle connector support CDC or redo-log based replication?

No. The Oracle connector supports full refresh and cursor-based incremental sync. It does not read redo logs and does not use Oracle CDC, LogMiner, GoldenGate, XStream, or Flashback. It does not detect hard deletes from the source.

Can one source sync multiple Oracle services or schemas?

Each source connects to one Oracle service. Current schema discovery is based on the Oracle schema associated with the connecting user, so use the appropriate user/service for the tables you want to sync.

Can I sync Oracle views, materialized views, or synonyms?

The current connector discovers tables in the connected Oracle schema. Views, materialized views, and synonyms are not exposed as supported objects on this source page.

Which cursor columns can I use for incremental sync?

Use a reliable date or timestamp-style column that advances when rows are inserted or updated. Tables without a reliable cursor column should use full refresh.

Do I need to whitelist an IP address?

If your Oracle database restricts inbound connections, allow Supaflow IP 18.214.240.61 or connect through your approved private network path.

Can I configure Oracle Wallet, TCPS, or client certificates?

The current Oracle source configuration does not expose Oracle Wallet, TCPS, client certificate, TNS descriptor, or SSL-mode fields. Use an approved private network path or contact support if your database requires those settings.

What happens with late-arriving updates?

Use the optional lookback period to re-read a short window before the previous cursor position. This can capture rows written slightly out of order, but the cursor column still needs to be reliable.