Skip to content
Database ⇄ Analytics

OCI Database (Oracle Cloud) to Tableau integration — real-time data sync

Keep OCI Database (Oracle Cloud) and Tableau 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 OCI Database (Oracle Cloud) and Tableau

Give Tableau the users, events, and records that live in OCI Database (Oracle Cloud) in real time, and sync the cohorts and scores Tableau computes back into OCI Database (Oracle Cloud) where your applications read them.

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into OCI Database (Oracle Cloud), so OCI Database (Oracle Cloud) always reflects the current state of Tableau — without exports, scripts, or schedulers.

A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Tableau is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from OCI Database (Oracle Cloud) into Tableau usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.

Common use cases

  • 01 Track Extract Refresh Tasks and DatasourceRefreshFailed webhook events to raise alerts in a database or ticketing system when refreshes fail.
  • 02 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 03 Write changes from SaaS applications back into OCI so PL/SQL-based processes operate on current data.
  • 04 Replicate operational tables from OCI to an analytics warehouse with log-based CDC instead of nightly batch dumps.

Common sync patterns

Where Tableau tracks product events: behavior onto stored records

Signup, usage, and lifecycle events captured in Tableau sync into OCI Database (Oracle Cloud) as rows, so applications and internal tools can read behavioral data next to the records they already keep.

Where Tableau builds cohorts or scores: results your services can read

Segments, cohorts, or scores computed in Tableau sync back into OCI Database (Oracle Cloud), where the services that read from the database act on them at query speed without calling the analytics API.

Analytics on live operational data, minus the pipeline

The users, events, orders, and records stored in OCI Database (Oracle Cloud) land in Tableau as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

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

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.

OCI Database (Oracle Cloud) objects Tableau objects How this pairing syncs
Views Read-only projections used to expose curated subsets to downstream systems Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Same entity on both sides — records pair one-to-one and field-level changes reconcile in the writable direction.
Partitions Physical table subdivisions relevant when replicating large fact tables Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Partitions is specific to OCI Database (Oracle Cloud) and Fields and Columns to Tableau — each maps to any object or custom field on the other side.
Tables The primary sync surface; rows are read and written directly over SQL Published Data Sources Published data sources (.tdsx); their underlying rows are read via the VizQL Data Service, and refresh state is tracked through content webhooks. Tables is specific to OCI Database (Oracle Cloud) and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
Materialized views Precomputed result sets sometimes used as stable read sources for replication Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Materialized views is specific to OCI Database (Oracle Cloud) and Workbooks to Tableau — each maps to any object or custom field on the other side.
Schemas Namespace boundaries that scope which objects a sync connection can access Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Schemas is specific to OCI Database (Oracle Cloud) and Projects to Tableau — each maps to any object or custom field on the other side.
Sequences Key generators that matter when writing new rows from external systems Users Site users with site roles and group membership; read via REST for access reviews and to reconcile identities against an HR or IdP source. Sequences is specific to OCI Database (Oracle Cloud) and Users to Tableau — each maps to any object or custom field on the other side.

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

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.

OCI Database (Oracle Cloud) Tableau 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.

DeliveryTableau does not accept inbound record writes, so this direction carries requests rather than records: Tableau's output flows back as field updates on the originating OCI Database (Oracle Cloud) records.

Tableau OCI Database (Oracle Cloud) Sub-second propagation

DetectionTableau notifies Stacksync of record changes through webhook events. Webhooks fire on workbook and data source create/update/delete and extract refresh events.

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

Rate-limit considerations

  • OCI Database (Oracle Cloud): Throughput bounded by instance sizing rather than API quotas.
  • Tableau: Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
What ships with OCI Database (Oracle Cloud) ⇄ Tableau

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever OCI Database (Oracle Cloud) or Tableau 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 OCI Database (Oracle Cloud) or Tableau record.

Observability

Monitoring

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

Trading partners

EDI

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

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

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

Tableau

Integration surface
REST API, Metadata API (GraphQL), and VizQL Data Service
Authentication
Sign-in via Personal Access Token (PAT) or username/password returns a credentials token sent as the X-Tableau-Auth header; Connected Apps issue JWTs for OAuth-style access. One active session per PAT.
Change detection
Webhooks fire on workbook and data source create/update/delete and extract refresh events; otherwise content and metadata are polled via REST list endpoints (updatedAt) and the Metadata API.
Capabilities
read · webhooks
Rate limits
Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
How it works

How to connect OCI Database (Oracle Cloud) to Tableau — 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 OCI Database (Oracle Cloud) and Tableau 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
    OCI Database (Oracle Cloud) connected
    Tableau connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the OCI Database (Oracle Cloud) and Tableau 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 · OCI Database (Oracle Cloud) ⇄ Tableau
    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
    OCI Database (Oracle Cloud) Tableau
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

OCI Database (Oracle Cloud) and Tableau 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
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 366 integrations available for OCI Database (Oracle Cloud) and Tableau.

Popular · 7 of 366
All OCI Database (Oracle Cloud) integrations All Tableau 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