Skip to content
Data warehouse ⇄ Database

Databricks to OCI Database (Oracle Cloud) integration — real-time, two-way sync

Keep Databricks and OCI Database (Oracle Cloud) in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Databricks and OCI Database (Oracle Cloud)

Connect OCI Database (Oracle Cloud) and Databricks with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want OCI Database (Oracle Cloud)'s rows in Databricks, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in OCI Database (Oracle Cloud) where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in OCI Database (Oracle Cloud) sync into Databricks in real time, and result tables in Databricks sync back into OCI Database (Oracle Cloud), with schema and type mapping between the two systems handled for you.

Common use cases

  • 01 Serve ML feature outputs computed in Databricks to production apps through a synced operational store.
  • 02 Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
  • 03 Run on-prem Oracle and OCI side by side during a cloud migration while keeping both ends writable.
  • 04 Expose ERP or billing data held in OCI to internal tools by syncing selected schemas to a managed Postgres.

Common sync patterns

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

Offload heavy reads

Point analytical queries at the synced copy in Databricks and keep OCI Database (Oracle Cloud) focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from OCI Database (Oracle Cloud) land in Databricks as they change, replacing hand-built CDC and batch extract jobs.

What you can sync between Databricks and OCI Database (Oracle Cloud)

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Databricks objects OCI Database (Oracle Cloud) objects How this pairing syncs
Schemas Group tables and views; syncs typically target a dedicated schema per source system. Schemas Namespace boundaries that scope which objects a sync connection can access Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Curated read-only projections used as sync sources for downstream tools. Views Read-only projections used to expose curated subsets to downstream systems Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. Materialized views Precomputed result sets sometimes used as stable read sources for replication Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
SQL Warehouses The compute endpoint a sync connects to for query execution. Sequences Key generators that matter when writing new rows from external systems SQL Warehouses is specific to Databricks and Sequences to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.
Change Data Feed Row-level change records on Delta tables that drive incremental reads. PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place Change Data Feed is specific to Databricks and PL/SQL procedures and packages to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.
Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. JSON collections Document-style storage in the converged engine, synced alongside relational tables Catalogs is specific to Databricks and JSON collections to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.

How changes propagate between Databricks and OCI Database (Oracle Cloud)

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Databricks OCI Database (Oracle Cloud) Sub-second propagation

DetectionChanges in Databricks are captured at the source via change data capture — no polling loop against its API. Delta Lake Change Data Feed for row-level changes.

DeliveryEach detected change is applied to OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.

OCI Database (Oracle Cloud) Databricks Sub-second propagation

DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.

DeliveryEach detected change is applied to Databricks as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Databricks: Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits.
  • OCI Database (Oracle Cloud): Throughput bounded by instance sizing rather than API quotas.
What ships with Databricks ⇄ OCI Database (Oracle Cloud)

Connect Databricks and OCI Database (Oracle Cloud) for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–OCI Database (Oracle Cloud) connection.

Real-time

Two-way sync

Changes in Databricks or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Databricks or OCI Database (Oracle Cloud) data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Databricks or OCI Database (Oracle Cloud) record.

Observability

Monitoring

Track your Databricks ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Databricks and OCI Database (Oracle Cloud).

How the Databricks and OCI Database (Oracle Cloud) connectors work

Databricks

Integration surface
SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution
Authentication
Personal access tokens or OAuth machine-to-machine credentials for service principals
Change detection
Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns
Capabilities
read · write · CDC
Rate limits
Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits

OCI Database (Oracle Cloud)

Integration surface
SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP
Authentication
database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available
Change detection
log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling
Capabilities
read · write · CDC
Rate limits
throughput bounded by instance sizing rather than API quotas
How it works

How to connect Databricks to OCI Database (Oracle Cloud) — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Databricks and OCI Database (Oracle Cloud) with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Databricks connected
    OCI Database (Oracle Cloud) connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Databricks and OCI Database (Oracle Cloud) objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Databricks ⇄ OCI Database (Oracle Cloud)
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Databricks OCI Database (Oracle Cloud)
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Databricks and OCI Database (Oracle Cloud) integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 478 integrations available for Databricks and OCI Database (Oracle Cloud).

Popular · 5 of 478
All Databricks integrations All OCI Database (Oracle Cloud) integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own