Database connector

The Oracle data catalog your whole team can trust.

The Dawiso Oracle connector turns your database into a searchable data catalog: every schema, table, view, procedure and constraint, with lineage to BI downstream.

Read the docs

Live connector Stable connector

Oracle

Dawiso

Metadata-only · your data never leaves the source

Type: Enterprise relational database
Auth: User + password (read-only)
Sync: Scheduled, incremental
Direction: Read-only · metadata

First things first

What is a data connector?

Metadata-only Read-only access Incremental sync Cross-system lineage

A data connector is the bridge between a tool in your stack and the catalog that gives you a unified view of it. Once a connector is configured, it reaches into the source system on a schedule, reads out the metadata - schemas, tables, dashboards, jobs, ownership, lineage - and represents it inside the catalog. Your actual rows and values stay where they are.

Connectors are the reason a data catalog can answer questions like "which Power BI dashboard depends on this Snowflake table?" or "who owns the orders topic in Kafka?" - automatically, without anyone keeping a spreadsheet up to date.

Three properties separate a good connector from a brittle one: it should be read-only and safe, it should be incremental so a full re-scan isn't required for every refresh, and it should resolve lineage across system boundaries, not just inside one tool.

About the platform

What is Oracle Database?

Oracle Database is the long-running enterprise relational database from Oracle Corporation, first released in 1979. Banks, insurers, telcos and the public sector use it for core systems of record: general ledger, policy, billing, claims. It runs on-premises, in Oracle Cloud, and as Cloud at Customer.

Oracle's own catalog views (ALL_TABLES, ALL_TAB_COLS, ALL_VIEWS) cover what's inside the database. What they don't cover is the Power BI report consuming the table, the data product the business owns, and the GDPR policy security signed off on. That's where the Dawiso Oracle data catalog joins the picture: read-only, metadata-only, and cross-platform.

Architecture

How Dawiso connects to Oracle

A small read-only role on the Oracle side. The Dawiso scanner pulls metadata on a schedule. Everything ends up in your catalog, business-readable.

Source

Oracle database

Schemas & users
Tables & views
Procedures & functions
Indexes & constraints

REST · JDBC

Dawiso scanner

Read-only metadata

Schema & object discovery
Dependency resolution
SQL flow parsing (optional)
Sampling on opt-in

Internal

Catalog

Dawiso platform

Searchable metadata
Lineage & ownership
Business glossary
Policy & classifications

Connection details

Protocol: Oracle JDBC + ALL_* and SYS catalog views
Authentication: Oracle user + password · read-only grants
Lineage: Object dependencies resolved from ALL_DEPENDENCIES; object-level lineage built from parsed view and stored-procedure SQL via Data Flow parsing on enterprise plans

Setup

Connect Oracle in 4 steps

01

Create a Dawiso user

CREATE USER dawiso IDENTIFIED BY <password>, then GRANT CREATE SESSION TO dawiso so the integration can connect to the database.
02

Grant metadata access

Choose object-level GRANT SELECT for each table, schema-level GRANT SELECT ANY TABLE (Oracle 23c+), or system role with SELECT on sys.all_tables, all_tab_cols, all_views, all_procedures.
03

Connect in Dawiso

Add the host (DNS, IP or Oracle URL), port 1521, the SID or Service Name, plus user and password. Choose Shared or Private connection.
04

Run ingestion

Provide a comma-separated list of schemas to ingest. Scheduled incremental sync keeps the catalog current. Flow parsing resolves object-level lineage on enterprise plans.

Capabilities

What you get with the Oracle connector

Schema & table catalog

Every Oracle schema, table, view, procedure and function is searchable, with column descriptions, data types, owners and the constraints behind them.
Object-level lineage

Cross-platform lineage from a Power BI report through Oracle views and stored procedures down to the source table that feeds them, via Data Flow parsing on enterprise plans.
PII classification

Classify a column once. Dawiso flags every Oracle column carrying birth number, IBAN or government IDs across all schemas in scope.
Ownership & certification

Mark Oracle tables as certified, deprecated or under review. Owner, steward and SLA are visible directly in the catalog.
Procedure & function metadata

Stored procedures and functions are catalogued with their arguments and parsed bodies, so the business logic in PL/SQL is searchable too.
GDPR & DORA evidence

Sensitive columns are tagged and the policy follows them through views and into downstream BI, with a full audit trail for regulators.

Business value

Why teams turn on the Oracle connector

-65%
Fewer 'which table?' pings

Analysts find the certified Oracle table in Dawiso instead of pinging the DBA to ask which view the finance report actually reads from.
10x
Faster impact analysis

Before altering an Oracle view or procedure, see exactly which BI reports and downstream tables depend on it. Seconds, not days.
Read-only
Zero risk to production

Dawiso uses a dedicated user with SELECT on catalog views only. Your Oracle data, your transactions and your write paths are untouched.

Ready to catalog your Oracle?

Set up the connector in an afternoon. See your first lineage graph the same day.

Read the docs

Frequently asked questions

Still curious? Talk to our team ->

What is catalog in Oracle database?

Oracle's data dictionary (catalog) stores metadata about schemas, tables and objects in views like ALL_TABLES and ALL_TAB_COLUMNS. Dawiso reads these read-only and builds a business-readable catalog with lineage, ownership and classification.

Is the OCI data catalog free?

Oracle's OCI Data Catalog covers Oracle Cloud sources. Dawiso is cross-platform: it reads Oracle metadata read-only and connects it to BI and the rest of your stack, with lineage and a business glossary that span beyond OCI.

What is a data catalog used for?

A data catalog makes every Oracle table discoverable, documented and trustworthy. Dawiso turns dictionary metadata into one searchable catalog the whole business can use, with lineage to source.

What permissions does Dawiso need in Oracle?

A dedicated user (e.g. dawiso) with CREATE SESSION and either object-level GRANT SELECT per table, schema-level GRANT SELECT ANY TABLE on Oracle 23c+, or a system role with SELECT on sys.all_users, all_tables, all_tab_cols, all_views, all_procedures, all_constraints, all_indexes. Read-only end to end.

Which Oracle versions are supported?

Oracle 19c is the officially supported baseline, all editions. Newer versions (21c, 23ai) work with the same catalog views; for 23ai, schema-level GRANT SELECT ANY TABLE ON SCHEMA simplifies onboarding.

Does Dawiso copy our Oracle data?

No. Dawiso queries ALL_* and SYS catalog views for metadata only. Row-level data stays inside Oracle. Column profiling and sampling are opt-in per data source and never run automatically.

How is lineage built?

Object dependencies come from ALL_DEPENDENCIES. For object-level resolution, Dawiso parses SQL from view and PL/SQL procedure definitions via Data Flow parsing. Oracle is one of the supported targets for this enterprise feature.