← All Adapters
Oracle logo

ORACLE

type: oracle
FREE FOR INDIVIDUALS✓ VERIFIED IN DVT TEST SUITE

Enterprise-grade relational database. Industry standard for mission-critical financial, ERP, and healthcare systems.

DVT SUPPORT

FEDERATION SOURCE

read in federation models

FEDERATION TARGET

materialize federation results

DEFAULT TARGET

run full dbt projects against it

SEED TARGET

dvt seed --target loads here

DVT supports Oraclebecause both dbt and Sling do: dbt drives standard materializations when it's your default target, Sling moves data in and out during federation. Connectivity for both layers is checked with dvt debug --all.

PREREQUISITES

Driver: oracledb — installed automatically by:

dvt sync

CONFIGURATION FIELDS

FIELDTYPEREQUIREDDEFAULTDESCRIPTION
typestringyesMust be `oracle`
hoststringyesOracle server hostname
portintegerno1521Listener port
userstringyesOracle username
passwordstringyesOracle password
servicestringyesOracle service name
threadsintegerno4Number of parallel threads

PROFILES.YML EXAMPLE

my_project:
  target: oracle_dev
  outputs:
    oracle_dev:
      type: oracle
      host: oracle.internal.com
      port: 1521
      user: ANALYTICS
      password: "{{ env_var('ORA_PASSWORD') }}"
      service: ORCL

SOURCES.YML EXAMPLE

sources:
  - name: erp_system
    meta:
      connection: oracle_dev
    schema: FINANCE
    tables:
      - name: GL_JOURNAL
      - name: AP_PAYMENTS

DBT ADAPTER FEATURES

When Oracle is your default target, every standard dbt model runs through the official dbt adapter — all of its documented capabilities apply unchanged:

MATERIALIZATIONS

tableviewincrementalephemeralmaterialized_viewf_tablef_incremental

INCREMENTAL STRATEGIES

appendmergedelete+insert

NOTABLE CONFIGS

  • parallel degree
  • compression clauses
  • service_name connections
Official dbt Oracle adapter docs ↗

FEDERATION INCREMENTAL STRATEGIES

Strategies available when this engine is the target of a f_incremental model:

Append Delete+Insert Merge

KNOWN LIMITATIONS

  • DROP uses PL/SQL blocks with CASCADE CONSTRAINTS PURGE