Oracle Connector

This document outlines OvalEdge's integration with Oracle, enabling efficient metadata management through features such as crawling, profiling, query sheet, data preview, and lineage building (both automatic and manual).

Overview

Connector Details

Connector Features

Getting Ready to Establish a Connection

Prerequisites

The following are the prerequisites to establish a connection between Oracle and OvalEdge:

Whitelisting Ports

Ensure the inbound port “1521” is whitelisted for OvalEdge to connect to the Oracle database.

Service Account User Permissions

Setup a Connection

1. Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Oracle, and complete the required parameters.
   
   

   Note: Fields marked with an asterisk (*) are mandatory for establishing a connection.

   
   

   Field Name	Description
   Connector Type	By default, "Oracle" is displayed as the selected connector type.
   Connector Settings
   Credential Manager*	Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection. Supported Credential Managers: OE Credential Manager AWS Secrets Manager HashiCorp Vault Azure Key Vault
   License Add Ons	Auto Lineage Supported Data Quality Supported Data Access Not Supported Select the checkbox for Auto Lineage Add-On to build data lineage automatically. Select the checkbox for Data Quality Add-On to identify data quality issues using data quality rules and anomaly detection.
   Connector Name*	Enter a unique name for the Oracle connection.
   Connector Environment	Select the environment (Example: PROD, STG) configured for the connector.
   Server*	Enter the Oracle database server name or IP address (Example: xxxx-xxxxxxx.xxxx4ijtzasl.xx-south-1.rds.amazonaws.com or 1xx.xxx.1.xx).
   Port*	By default, the port number for Oracle, 1521, is auto-populated. If required, you can change it to a custom port number configured for your Oracle.
   Database*	Enter the database name to which the service account user has access within the Oracle.
   Database Type	Select SID or Service Name from the Database type drop-down. An SID uniquely identifies a specific database within an environment, whereas a Service Name can represent one or more SIDs.
   Driver*	By default, the Oracle driver details are auto-populated.
   Username*	Enter the service account username configured to access the Oracle database (example: "oesauser").
   Password*	Enter the password associated with the service account user.
   Connection String	Configure the connection string for the Oracle database: Automatic mode: The system generates a connection string based on the provided credentials. Manual mode: Enter a valid connection string manually. Replace placeholders with actual database details. {sid} refers to the database name.

   
   

   Default Governance Roles
   Default Governance Roles*	Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are available for selection.
   Admin Roles
   Admin Roles*	Select one or more users from the drop-down list for Integration Admin and Security & Governance Admin. All users configured in OvalEdge Security are available for selection.
   No of Archive Objects
   No Of Archive Objects*	This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive. Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.
   Bridge
   Select Bridge*	If applicable, select the bridge from the drop-down list. The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without modifying firewall rules.

2. After entering all connection details, you can perform the following actions:
   1. Click Validate to verify the connection.
   2. Click Save to store the connection for future use.
   3. Click Save & Configure to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are correct to resolve these issues. If issues persist, contact your assigned OvalEdge support team.

Manage Connector Operations

Crawl/Profile

The Crawl/Profile button allows you to select one or more schemas for crawling and profiling.

1. Navigate to the Connectors page and click Crawl/Profile.
2. Select the schemas you want to crawl.
3. The Crawl option is selected by default. Click the Crawl & Profile radio button if you want both operations.
4. Click Run to collect metadata from the connected source and load it into the OvalEdge Data Catalog.
5. After a successful crawl, the information appears in the Data Catalog > Databases tab.

The Schedule checkbox allows automated crawling and profiling for a selected timeframe, from a minute to a year.

1. Click the Schedule checkbox to enable the Select Period drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click Schedule to initiate metadata collection from the connected source.
4. The system will automatically execute the selected operation (Crawl or Crawl & Profile) at the scheduled time.

Other Operations

The Connectors page in OvalEdge provides a centralized view of all configured connectors and their health status.

Managing connectors includes:

• Connector Health: Displays performance using a green icon for active connections and a red icon for inactive connections, helping to monitor the connection between OvalEdge and data sources.
• Viewing: Click the Eye icon next to the connector name to view connector details, including databases, tables, columns, and codes.

Nine Dots Menu Options:

You can view, edit, validate, build lineage, modify connector settings and delete connectors using the Nine Dots menu.

• Edit Connector: Update and revalidate the data source.
• Validate Connector: Check the connection's integrity.
• Settings: Modify connector settings.
  • Crawler: Configure data extraction.
  • Profiler: Customize data profiling rules and methods.
  • Query Policies: Define query execution rules based on roles.
  • Access Instructions: Add notes on how data can be accessed.
  • Business Glossary Settings: Manage term associations at the connector level.
  • Anomaly Detection Settings: Configure anomaly detection preferences at the connector level.
  • Others: Configure notification recipients for metadata changes.
• Build Lineage: Automatically build data lineage using source code parsing.
• Delete Connector: Remove a connector with confirmation.

Metadata Mapping

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA