Data Warehouse

Amazon Redshift Connector

OvalEdge enables connectivity to Amazon Redshift using the JDBC driver, allowing for tasks such as crawling database objects, profiling sample data, building relationships, and lineage.

Overview 

Connector Details

Connector Category

RDBMS System

OvalEdge Release Current Connector Version

6.3.4

Connectivity

[How OvalEdge connects to Redshift Server ]

JDBC

Amazon Redshift Version Supported

redshift-jdbc42-2.1.0.4 or above

OvalEdge Releases Supported

(Available from)

Release4.3 onwards

Connector Features

Crawling of Metadata Objects 

Supported

Profiling

Supported

Profiling Methodologies

Full Profiling

Sample Profiling

**Data Types Not Supported**

"array", "xid", "anyarray", "oidvector" ,"int2vector" ,"bytea", "tid"

Query Sheet

Supported

Data Preview

Supported

Lineage 

Supported

Lineage Levels Supported

Table/View Lineage

Column Lineage

Auto Lineage Sources

Parsing Stored Procedures, Functions, and Views

Authentication via Credential Manager

Supported

Data Quality

Supported

DAM (Data Access Management)

Supported

Bridge

Supported

 

Getting Ready to Establish a Connection 

Prerequisites

The following are the prerequisites required for establishing a connection:  

Whitelisting Ports

Ensure the inbound port “5439” is whitelisted for OvalEdge to connect to the Redshift database.

Service Account User Permissions

Important: We recommend having a separate service account to establish a connection from OvalEdge to the data source with minimal permissions.

Operation 

Minimum Access Permission 

Connection Validation

Read

Schema

USAGE

Tables, Table Columns

SELECT

Relationships

SELECT

Views, Triggers, Procedures & Functions

SELECT

Setup a Connection

Important: You must have the Connector Creator role to set up a connection in OvalEdge.

  1. Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Redshift, and complete the specific parameters.
    Note: Fields marked with an asterisk (*) are mandatory for establishing a connection.

    Field Name

    Description

    Connector Type

    By default, "Redshift" is displayed as the selected connector type.

    Connector Settings

    Credential Manager*

    Select the desired credentials manager from the dropdown 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

    OvalEdge connectors have a default license add-on for data crawling and profiling.

    • 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.
    • Select the checkbox for Data Access Add-On, which will enforce connector access via OvalEdge with the Data Access Management (DAM) feature enabled.

    Connector Name*

    Enter a unique name for the Redshift connection              

    (Example: "Redshift_Prod").

    Connector Environment

    Select the environment (Example: PROD, STG) configured for the connector. 

    Server*

    Enter the Redshift database Server name or IP address (Example: https://abc1.cpgvvwcxxxes.us-xxxt-2.redshift.amazonaws.com/ or 192.168.1.10).

    Port*

    By default, the port number for the Redshift database "5439" is auto-populated. If necessary, you can change this to a different port number.

    Database*

    Enter the database name to which the service account user has access within the Redshift.

    Driver*

    By default, the Redshift driver details (Example: com.amazon.redshift.jdbc.Driver) are auto-populated. OvalEdge artifacts include the required drivers for supported databases.

    Username*

    Enter the service account username set up to access the Redshift database (Example: "oesauser").

    Password*

    Enter the password associated with the service account user (Example: "password").

    Connection String

    Configure the connection string for the Redshift database:

    • Automatic Mode: The system generates a connection string based on the provided credentials.
      • Example (Redshift): 

    jdbc:redshift://{server}:5439/{sid}

    • Manual Mode: Manually enter a valid connection string.
      • Example (Redshift): jdbc:redshift://{server}:{port}/{sid}

    Replace placeholders with actual database details.

    {sid} refers to Database Name


    Default Governance Roles

    Default Governance Roles*

    Select the appropriate users or teams for each governance role from the dropdown list. All users and teams configured in OvalEdge Security are displayed for selection. 

    Admin Roles

    Admin Roles*

    Select one or more users from the dropdown list for Integration Admin and Security and Governance Admin. All users configured in OvalEdge Security are available for selection.

    No Of Archive Objects*

    It indicates the number of recent metadata changes to a dataset at the source. By default, it is off. You can enable it by toggling the Archive button and specifying the number of objects to archive.

    Example: Setting it to 4 retrieves the last 4 changes, shown 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 altering 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 provided, you may encounter error messages. To resolve these issues, ensure all input is correct. If problems persist, contact your assigned OvalEdge support team.

S.No.

Error Message(s)

Error Description / Resolution

1

Error while validating connection: Error while validating Redshift Connection: Failed to obtain JDBC Connection; nested exception is java.sql.SQLException: [Amazon](100021) Error setting default driver property values.

Error Description: 

It indicates an issue with your JDBC connection, particularly when interacting with an Amazon service, possibly Amazon RDS or Redshift.


Resolution: 

We need to check the server to see if it is up and then start it.

2

Error while saving Database Connection: Prepared StatementCallback; Data truncation: Data too long for column 'ipaddress' at row 1; nested exception is com.mysql.cj.jdbc.exceptions.MysqlDataTruncation: Data truncation: Data too long for column 'ipaddress' at row 1

Error Description: 

The error indicates that the data you're trying to insert into the ‘ipaddress’ column in your database is too large for the column's defined size.

Resolution: 

Look for the size of the ‘ipaddress’ column (e.g., VARCHAR(15)).

3

Error while validating connection: Error while validating Redshift Connection: Failed to obtain JDBC Connection; nested exception is java.sql.SQLException: [Amazon](500310) Invalid operation: database ":5439/ovaledgedb" does not exist;   database name wrong

Error Description: 

The error indicates an issue with the database connection string for Amazon Redshift.

Resolution:

Make sure to enter the correct database name.

4

Error while validating connection: Error while validating Redshift Connection: Failed to obtain JDBC Connection; nested exception is java.sql.SQLException: [Amazon](500310) Invalid operation: password authentication failed for user "ovaledge1";  wrong user name

Error Description: 

The error message indicates a failure to authenticate to your Amazon Redshift cluster.

Resolution:

Make sure to enter the correct username.

5

Error while validating connection: Error while validating Redshift Connection: Failed to obtain JDBC Connection; nested exception is java.sql.SQLException: [Amazon](500310) Invalid operation: password authentication failed for user "ovaledge1";  wrong password provided

Error Description: 

The error message indicates a failed attempt to connect to an Amazon Redshift database due to incorrect credentials.

Resolution:

Make sure to enter the correct password.

6

Error while validating connection: Error while validating Redshift Connection: Failed to obtain JDBC Connection; nested exception is java.sql.SQLException: [Amazon](500150) Error setting/closing connection: UnknownHostException. wrong servername

Error Description:

The error indicates a JDBC connection failure to Amazon Redshift due to an UnknownHostException, likely caused by an incorrect or unreachable hostname.

Resolution:

  • Verify that the server name (hostname) of your JDBC URL is correct.
  • Ensure that the hostname matches the format given in your Redshift cluster's endpoint.

Manage Connector Operations

Configure Settings for Connector Operations

The Redshift connector offers various settings to customize data crawling, profiling, and access. These include:

  • Crawler: Configure data that needs to be extracted.
  • Profiler: Customize data profiling rules and methods.
  • Query Policies: Define rules for executing queries based on roles. 
  • Access Instructions: Specify how data can be accessed as a note.
  • 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.

Crawl/Profile

Important: You must have the Integration Admin role in OvalEdge for crawl/profile operations.

Crawl and Profile operations enable you to select one or more schemas from a list of all available schemas within a specific database. This allows you to customize the crawling and profiling operations selection according to your requirements. Furthermore, it provides the option to schedule crawling and profiling and enable anomaly detection to identify any irregularities in the data objects.

Other Operations

The Connectors page in OvalEdge provides a centralized view of all configured connectors, including their health status. You can view, edit, validate, build lineage, and delete connector/Schema using the Nine Dots menu.

Managing connectors includes:

  • Connectors Health: Displays performance with a green (active) or red (inactive) icon, helping monitor data flow and address issues early.
  • Viewing: Shows connector details (e.g., Databases, Tables, Table Columns, and Codes) via the View icon.

Nine Dots Menu Options:

  • Edit Connector: Update and revalidate the data source.
  • Validate Connector: Check the connection's integrity.
  • Settings: Modify connector settings.
  • Build Lineage: Automatically build data lineage using SQL logs and source code parsing.
  • Delete Connector: Remove connectors or schemas with confirmation.

Limitations

S.No.

Description

The connection will not get validated without an external jar


Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA