Oracle
This document outlines the integration with Oracle, enabling streamlined metadata management through features such as crawling, profiling, querying, data preview, and lineage building (both automatic and manual). Additionally, it ensures secure authentication via Credential Manager.

Overview
Connector Details
Connector Category
RDBMS
Connector Version
Release7.1
Releases Supported (Available from)
Legacy Connector
Connectivity
[How the connection is established with RDBMS System]
JDBC driver
Verified Oracle Version
21c
Connector Features
Crawling
✅
Delta Crawling
❌
Profiling
✅
Query Sheet
✅
Data Preview
✅
Auto Lineage
✅
Manual Lineage
✅
Secure Authentication via Credential Manager
✅
Data Quality
✅
DAM (Data Access Management)
❌
Bridge
✅
Metadata Mapping
The following objects are crawled from Oracle and mapped to the corresponding UI assets.
Table
tablename
Table
Tables
table
Table
table_type
Table Type
Tables
table
Table
tablecomment
Source Description
Descriptions
Source Description
Columns
COLUMN_NAME
Column
Table Columns
-
Columns
DATA_TYPE
Column Type
Table Columns
-
Columns
COMMENTS
Source Description
Table Columns
-
Columns
DATA_LENGTH
Data Type Size
Table Columns
-
View
View Name
View
Tables
View
View
text
View Query
Views
View
Procedures
name
Name
Procedures
-
Procedures
Text
Procedure Query
-
-
Synonyms
SYNONYM_NAME
Synonym
Synonyms
-
Set up a Connection
Prerequisites
The following are the prerequisites to establish a connection:
External Supporting Files
ojdbc8-19.3.0.0.jar
Use this file when connecting to Oracle databases using the ojdbc8 driver. Place the file in the Third Party Jars folder.
Whitelisting Ports
Make sure that inbound port “1521” is whitelisted to enable successful connectivity with the Oracle database.
The default port number for Oracle data source is 1521. If a different port is used, ensure that the updated port number is specified during connection setup, the port is whitelisted, and communication between the system and Oracle data source is properly established.
Service Account User Permissions
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
Schemas
sys.dba_users
SELECT
Schemas
all_users
SELECT
Tables
all_tab_comments
SELECT
Tables
SYS.ALL_MVIEWS
SELECT
Tables
dba_tab_comments
SELECT
Table Columns
ALL_TAB_COLUMNS, ALL_COL_COMMENTS
SELECT
Table Columns
all_constraints, all_cons_columns
SELECT
Views
ALL_VIEWS
SELECT
Functions
DBA_SOURCE, ALL_SOURCE
SELECT
Stored Procedures
DBA_SOURCE, ALL_SOURCE
SELECT
Synonyms
all_synonyms
SELECT
Indexes
ALL_INDEXES, ALL_IND_COLUMNS
SELECT
Relationships
all_cons_columns, all_constraints
SELECT
Connection Configuration Steps
Users are required to have the Connector Creator role in order to configure a new connection.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Oracle, and complete the required parameters.
Connector Type
By default, "Oracle" is displayed as the selected connector type.
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.
Connector Description
Enter a brief description of the connector.
Server*
Enter the Oracle database server name or IP address (Example: xxxx-xxxxxxx.xxxx4ijtzasl.xx-south-1.rds.xxxxxx.com or 1xx.xxx.1.xx).
Port*
By default, the port number for Oracle, 1521, is auto-populated. If required, the port number can be modified as per custom port number that is configured for the Oracle database.
Database*
Enter the database name to which the service account user has access within the Oracle database.
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.
Plugin Server
Enter the server’s name when running as a plugin server.
Plugin Port
Enter the port number on which the plugin is running.
Default Governance Roles
Default Governance Roles*
Select the appropriate users or teams for each governance role from the drop-down list. All users configured in the security settings 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 the security settings 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 that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.
After entering all connection details, the following actions can be performed:
Click Validate to verify the connection.
Click Save to store the connection for future use.
Click Save & Configure to apply additional settings before saving.
The saved connection will appear on the Connectors home page.
Manage Connector Operations
Crawl/Profile
To perform crawl and profile operations, users must be assigned the Integration Admin role.
The Crawl/Profile button allows users to select one or more schemas for crawling and profiling.
Navigate to the Connectors page and click Crawl/Profile.
Select the schemas to crawl.
The Crawl option is selected by default. To perform both operations, select the Crawl & Profile radio button.
Click Run to collect metadata from the connected source and load it into the Data Catalog.
After a successful crawl, the information appears in the Data Catalog > Databases tab.
The Schedule checkbox allows automated crawling and profiling at defined intervals, from a minute to a year.
Click the Schedule checkbox to enable the Select Period drop-down.
Select a time period for the operation from the drop-down menu.
Click Schedule to initiate metadata collection from the connected source.
The system will automatically execute the selected operation (Crawl or Crawl & Profile) at the scheduled time.
Other Operations
The Connectors page provides a centralized view of all configured connectors, along with their health status.
Managing connectors includes:
Connector Health: Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with 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:
To view, edit, validate, build lineage, configure, or delete connectors, click on 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.
Connectivity Troubleshooting
If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.
1
Error while validating connection: Error while validating Oracle Connection: Failed to obtain JDBC Connection; nested exception is xxx.sql.SQLxxxxx: ORA-xxxxx: invalid username/password; logon denied
Description:
Either username and password might be wrong.
Resolution:
The username or password entered in the setup form is incorrect.
The authorizing user has the necessary permissions to establish a connection with the database.
2
Error while validating connection: Error while validating Oracle Connection: Failed to obtain JDBC Connection; nested exception is xxxx.sql.SQLxxxx: Listener refused the connection with the following error: ORA-xxxxx, TNS:listener does not currently know of SID given in connect descriptor.
Description:
The database name provided is invalid.
Resolution:
The database name entered in the setup form's Database Name field is incorrect.
Ensure that the database name is correctly spelled and exists in the target system.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?

