Oracle

Data QualityData LineageData CatalogER DiagramsData ProfilingCatalogAI AutodocumentationReference dataCustom fieldsSchema change tracking

Catalog and documentation

Data catalog

Dataedo documents metadata of the following objects:

• Tables
• Views
• Materialized views
• Procedures
• Packages
• Functions
• Sequences
• Jobs
• Database links

useful tip

For more details, see the Connector specification section below.

Catalog options summary

• Document and enrich metadata: edit descriptions, aliases, custom fields, and glossary links.
• Use source comments: import table/view/column comments from Oracle.
• Model relationships visually: import PK/FK/unique keys and build ER diagrams in subject areas.
• Apply governance features: use profiling, quality checks, lookups, and classification.
• Track and share changes: sync description updates and publish documentation to Portal/exports.

Database links

The Oracle Connector imports Database Links as Linked Sources, capturing the connection details and assigned names.

association of linked sources

The import process does not automatically associate linked sources with specific objects. Users must manually assign the linked source to the desired objects.

If a view is created using a Database Link connection object, the linked server must be assigned, and the script parsed to establish data lineage.

How to connect

Use the step-by-step connection guide for full Portal and Desktop instructions, prerequisites, and import options:

• Connecting to Oracle database

Connector specification

Supported scope

Area	Supported	Scope	Requirements
Metadata import	✅	Tables, views, materialized views, procedures, packages, functions, sequences, jobs, database links	See Required access level
Descriptions, aliases, and custom fields	✅	Manual enrichment in Dataedo after import	Initial schema import completed
Relationships and diagrams	✅	PK/FK/unique keys imported and used in ER diagrams	Keys must exist in source schema
Automatic lineage	✅	Object-level and column-level (parser dependent) for views, materialized views, procedures, and functions	See Required access level
Data profiling and quality	✅	Profiling, quality checks, and classification workflows	See Required access level
Write-back comments	✅	Selected object types	See Required access level

Imported objects

Object	Imported as
Table	Table
View	View
Materialized view	View
Procedure	Procedure
Package	Package
Function	Function
Sequence	Sequence
Job	Task/Job
Database link	Linked Source

Imported column attributes

Column attribute	Table columns	View columns	Editable
Column name	✅	✅	✅
Data type	✅	✅
Nullability	✅	✅
Column comments/descriptions	✅	✅	✅

Lineage support

Source	Method	Supported
Views	From dependencies	✅
Views	From SQL parsing	✅
Views (column level)	From SQL parsing	✅
Materialized views, procedures, functions	SQL parser dependent	✅

Data profiling

Profile	Support
Table row count	✅
Table sample data	✅
Column distribution (unique, non-unique, null, empty values)	✅
Min, max values	✅
Average	✅
Variance	✅
Standard deviation	✅
Min-max span	✅
Number of distinct values	✅
Top 10/100/1000 values	✅
10 random values	✅

Read more about profiling in the Data Profiling documentation.

Not supported or limited

Not supported / Limited	Workaround
Check constraints	Add manual documentation and vote on feature request
Non-unique indexes	Document important indexes manually
Automatic object mapping for database links	Assign linked source manually before parsing SQL

Supported versions and editions

Supported Versions	Supported Editions
9i R1, 9i R2, 10g R1, 10g R2, 11g R1, 11g R2, 12c R1, 12c R2, 18c, 19c, 21c, 23c	Express, Standard, Enterprise

Required access level

Importing database objects requires Oracle access for the account used in Import objects from database.

Permission / access	Used for	If missing
CONNECT role and CREATE SESSION	Establishing connection and running import	Connection and import cannot start
SELECT_ANY_DICTIONARY (recommended) or equivalent SELECT/EXECUTE grants	Cross-schema metadata and object definitions	Import is limited to accessible objects; metadata will be incomplete
SELECT on profiled/tested objects	Data profiling, quality checks, and classification runs	Profiling and quality results will be partial or fail
Access to SQL definitions (for parser input)	SQL parsing lineage for views/procedures/functions	Object-level or column-level lineage will be incomplete
Access to ALL_DB_LINKS (for link import)	Database links import as linked sources	Database links are not imported

Dataedo does not alter source data during synchronization.

The following objects are accessed during import. If access is missing, the import impact is:

Oracle object/view	What will be missing in import without access
ALL_ARGUMENTS	Procedure/function argument metadata (input/output parameters and signatures)
ALL_CONSTRAINTS	Constraint definitions (PK/FK/unique/check metadata), relationship backbone
ALL_CONS_COLUMNS	Column-level mapping for constraints; PK/FK/unique column assignments
ALL_DB_LINKS	Database links import (Linked Sources)
ALL_INDEXES	Index metadata (index objects, type, properties)
ALL_IND_COLUMNS	Column-level index composition
ALL_OBJECTS	Object discovery baseline; some objects may not be detected at all
ALL_SCHEDULER_JOBS	Job/task metadata
ALL_SEQUENCES	Sequence objects and sequence metadata
ALL_SOURCE	Source code/definitions for procedures, functions, packages, triggers; parser input may be incomplete
ALL_TAB_COLUMNS	Column list and core column metadata (names, data types, nullability)
ALL_TAB_COMMENTS	Table and column comments/descriptions from source
ALL_TRIGGERS	Trigger objects and trigger definitions
DUAL	Basic metadata queries may fail, which can block parts of import

##Er Diagram

Check this tutorial to see how to create an ER diagram for Oracle database.