Oracle Collected Data

This page describes what Sifflet imports from your Oracle database once the Oracle source is connected.

Imported Assets

Sifflet imports the following objects from the schemas selected in the source scope:

• Tables
• Views
• Materialized views (shown as views)
• External tables

Collected Metadata

Sifflet reads metadata from the ALL_* data dictionary views, which only list the objects that the Sifflet user can access. For each table and view, Sifflet collects:

• Name and schema
• Columns: name, data type, nullability, default value, and size
• DDL of tables, views, and materialized views, from DBMS_METADATA.GET_DDL (requires the optional SELECT_CATALOG_ROLE)

The Freshness (Update Time Gap) monitor reads the last change time of a table from ALL_OBJECTS.LAST_DDL_TIME. This is the time of the last DDL statement on the table: inserting or updating rows doesn't change it.

Lineage

Sifflet doesn't extract lineage between tables inside Oracle (from query logs or view definitions).

Oracle tables appear in lineage when other integrations reference them, for example BI tools, dbt, or data pipelines. Sifflet links these assets when the host, port, service name, and schema configured in the other tool match the Oracle source.

Data Freshness

Sifflet refreshes the Oracle metadata on the source schedule. See Integrations Management for the default frequency and scheduling options.

Data Exposure

Sifflet stores metadata and monitor results. Some features read and display row-level data from your tables: data preview and the failing rows of monitors. The DDL that Sifflet collects is stored and displayed in the Data Catalog. See Security for details on the data that Sifflet accesses and stores.