OpenMetadata/openmetadata-docs/content/v1.7.x-SNAPSHOT/connectors/database/oracle/index.md

title	slug
Oracle	/connectors/database/oracle

{% connectorDetailsHeader name="Oracle" stage="PROD" platform="OpenMetadata" availableFeatures=["Metadata", "Query Usage", "Data Profiler", "Data Quality", "dbt", "Lineage", "Column-level Lineage", "Stored Procedures", "Sample Data", "Reverse Metadata Ingestion"] unavailableFeatures=["Owners", "Tags"] / %}

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
• Reverse Metadata
• Troubleshooting

{% partial file="/v1.7/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.
--   This allows the role to connect.
GRANT CREATE SESSION TO new_role;

-- Grant SELECT_CATALOG_ROLE Privilege.
--   This allows the role ReadOnly Access to Data Dictionaries
GRANT SELECT_CATALOG_ROLE TO new_role;

If you don't want to create a role, and directly give permissions to the user, you can take a look at an example given below.

-- Create a New User
CREATE USER my_user IDENTIFIED by my_password;

-- Grant CREATE SESSION Privilege.
--   This allows the user to connect.
GRANT CREATE SESSION TO my_user;

-- Grant SELECT_CATALOG_ROLE Privilege.
--   This allows the user ReadOnly Access to Data Dictionaries
GRANT SELECT_CATALOG_ROLE to my_user;

Note: With just these permissions, your user should be able to ingest the metadata, but not the Profiler & Data Quality, you should grant SELECT permissions to the tables you are interested in for the Profiler & Data Quality features to work.

-- If you are using a role and do not want to specify a specific table, but any
GRANT SELECT ANY TABLE TO new_role;

-- If you are not using a role, but directly giving permission to the user and do not want to specify a specific table, but any
GRANT SELECT ANY TABLE TO my_user;

-- if you are using role
GRANT SELECT ON ADMIN.EXAMPLE_TABLE TO new_role;

-- if you are not using role, but directly giving permission to the user
GRANT SELECT ON ADMIN.EXAMPLE_TABLE TO my_user;

-- if you are using role
GRANT SELECT ON {schema}.{table} TO new_role;

-- if you are not using role, but directly giving permission to the user
GRANT SELECT ON {schema}.{table} TO my_user;

You can find further information here. Note that there is no routine out of the box in Oracle to grant SELECT to a full schema.

Metadata Ingestion

{% partial file="/v1.7/connectors/metadata-ingestion-ui.md" variables={ connector: "Oracle", selectServicePath: "/images/v1.7/connectors/oracle/select-service.png", addNewServicePath: "/images/v1.7/connectors/oracle/add-new-service.png", serviceConnectionPath: "/images/v1.7/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.7/connectors/database/advanced-configuration.md" /%}

{% /extraContent %}

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

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

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

{% /stepsContainer %}

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

Reverse Metadata

{% note %} This feature is specific to Collate and requires the Collate Enterprise License. {% /note %}

Description Management

Oracle supports description updates at the following levels:

• Table level
• Column level

Owner Management

❌ Owner management is not supported for Oracle.

Tag Management

❌ Tag management is not supported for Oracle.

Custom SQL Template

Oracle supports custom SQL templates for metadata changes. The template is interpreted using python f-strings.

Examples will be provided in a future update.

For more details about reverse metadata ingestion, visit our Reverse Metadata Documentation.