OpenMetadata/openmetadata-docs/content/v1.1.0/connectors/database/oracle/index.md

title	slug
Oracle	/connectors/database/oracle

Oracle

{% multiTablesWrapper %}

Feature	Status
Stage	PROD
Metadata	{% icon iconName="check" /%}
Query Usage	{% icon iconName="cross" /%}
Data Profiler	{% icon iconName="check" /%}
Data Quality	{% icon iconName="check" /%}
Lineage	{% icon iconName="check" /%}
DBT	{% icon iconName="check" /%}
Supported Versions	12c, 18c, 19c, and 21c

Feature	Status
Lineage	{% icon iconName="check" /%}
Table-level	{% icon iconName="check" /%}
Column-level	{% icon iconName="check" /%}

{% /multiTablesWrapper %}

In this section, we provide guides and references to use the Oracle connector.

Configure and schedule Oracle metadata and profiler workflows from the OpenMetadata UI:

• Requirements
• Metadata Ingestion
• Data Profiler
• Data Quality
• Lineage
• dbt Integration

{% partial file="/v1.1.0/connectors/ingestion-modes-tiles.md" variables={yamlPath: "/connectors/database/oracle/yaml"} /%}

Requirements

Note: To retrieve metadata from an Oracle database, we use the python-oracledb library, which provides support for versions 12c, 18c, 19c, and 21c.

To ingest metadata from oracle user must have CREATE SESSION privilege for the user.

-- CREATE USER
CREATE USER user_name IDENTIFIED BY admin_password;

-- CREATE ROLE
CREATE ROLE new_role;

-- GRANT ROLE TO USER 
GRANT new_role TO user_name;

-- GRANT CREATE SESSION PRIVILEGE TO USER
GRANT CREATE SESSION TO new_role;

Metadata Ingestion

{% partial file="/v1.1.0/connectors/metadata-ingestion-ui.md" variables={ connector: "Oracle", selectServicePath: "/images/v1.1.0/connectors/oracle/select-service.png", addNewServicePath: "/images/v1.1.0/connectors/oracle/add-new-service.png", serviceConnectionPath: "/images/v1.1.0/connectors/oracle/service-connection.png", } /%}

{% stepsContainer %} {% extraContent parentTagName="stepsContainer" %}

Connection Details

• Username: Specify the User to connect to Oracle. It should have enough privileges to read all the metadata.
• Password: Password to connect to Oracle.
• Host and Port: Enter the fully qualified hostname and port number for your Oracle deployment in the Host and Port field.
• Database Name: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name. It is recommended to use the database name same as the SID, This ensures accurate results and proper identification of tables during profiling, data quality checks and dbt workflow.
• Oracle Connection Type : Select the Oracle Connection Type. The type can either be Oracle Service Name or Database Schema
  • Oracle Service Name: The Oracle Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in tnsnames.
  • Database Schema: The name of the database schema available in Oracle that you want to connect with.
• Oracle instant client directory: The directory pointing to where the instantclient binaries for Oracle are located. In the ingestion Docker image we provide them by default at /instantclient. If this parameter is informed (it is by default), we will run the thick oracle client. We are shipping the binaries for ARM and AMD architectures from here and here for the instant client version 19.

{% partial file="/v1.1.0/connectors/database/advanced-configuration.md" /%}

{% /extraContent %}

{% partial file="/v1.1.0/connectors/test-connection.md" /%}

{% partial file="/v1.1.0/connectors/database/configure-ingestion.md" /%}

{% partial file="/v1.1.0/connectors/ingestion-schedule-and-deploy.md" /%}

{% /stepsContainer %}

{% partial file="/v1.1.0/connectors/troubleshooting.md" /%}

{% partial file="/v1.1.0/connectors/database/related.md" /%}