> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/connectors/connector-repositories/data-warehouse/amazon-redshift.md).

# Amazon Redshift

This article outlines the integration with Amazon Redshift, enabling streamlined metadata management through features such as crawling, profiling, querying, data preview, and lineage building (both automatic and manual).&#x20;

This connector uses the JDBC driver to establish connectivity with Amazon Redshift databases and supports metadata extraction from schemas, tables, columns, views, and other database objects. Authentication is established using service account credentials for secure access to Amazon Redshift metadata objects.

<figure><img src="https://1121831267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFZv5WsZmBfXjiJfMU2zR%2Fuploads%2F8K3c41lJ8DgT9cs75jqJ%2Fimage.png?alt=media&amp;token=202aebd5-0e2e-4514-9291-0d8f68fd24ad" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                                  | Data Warehouse     |
| ----------------------------------------------------------------------------------- | ------------------ |
| OvalEdge Release Supported                                                          | Release4 and later |
| <p>Connectivity</p><p>\[How the connection is established with Amazon Redshift]</p> | JDBC driver        |
| Verified Amazon Redshift Version                                                    | 1.0.109768         |

{% hint style="info" %}
**Note**: The Amazon Redshift connector has been validated with the mentioned "Verified Amazon Redshift Versions" and is expected to be compatible with other supported Amazon Redshift versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

### Connector Features

| Feature                                      |                                                                                      Availability                                                                                     |
| -------------------------------------------- | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| Crawling                                     |                                                                                           ✅                                                                                           |
| Delta Crawling                               |                                                                                           ❌                                                                                           |
| Profiling                                    |                                                                                           ✅                                                                                           |
| Sample Profiling                             |                                                                                           ✅                                                                                           |
| Query Sheet                                  |                                                                                           ✅                                                                                           |
| Data Preview                                 |                                                                                           ✅                                                                                           |
| Auto Lineage                                 | <p>✅<br>To learn more, <a href="https://docs.ovaledge.com/release8.1/connectors/connector-repositories/data-warehouse/amazon-redshift/amazon-redshift-lineage.md">click here</a>.</p> |
| Manual Lineage                               |                                                                                           ✅                                                                                           |
| Secure Authentication via Credential Manager |                                                                                           ✅                                                                                           |
| Data Quality                                 |                                                                                           ✅                                                                                           |
| DAM (Data Access Management)                 |                                                                                           ✅                                                                                           |
| Bridge                                       |                                                                                           ✅                                                                                           |

### Metadata Mapping

The following objects are crawled from Amazon Redshift and mapped to the corresponding UI assets.

<table><thead><tr><th width="148">Redshift Object</th><th width="176">Redshift Attribute</th><th width="172">OvalEdge Attribute</th><th width="171">OvaEdge Category</th><th width="188">OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>Schema name</td><td>Schema</td><td>Databases</td><td>Schema</td></tr><tr><td>Schema</td><td>Schema comment</td><td>Source Description</td><td>Databases</td><td>Schema</td></tr><tr><td>Table</td><td>Table Name</td><td>Table</td><td>Tables</td><td>Table</td></tr><tr><td>Table</td><td>Table Type</td><td>Type</td><td>Tables</td><td>Table</td></tr><tr><td>Table</td><td>Table Comments</td><td>Source Description</td><td>Descriptions</td><td>Source Description</td></tr><tr><td>Columns</td><td>Column Name</td><td>Column</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Data Type</td><td>Column Type</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Description</td><td>Source Description</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Ordinal Position</td><td>Column Position</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Length</td><td>Data Type Size</td><td>Table Columns</td><td>-</td></tr><tr><td>Views</td><td>View Name</td><td>View</td><td>Tables</td><td>View</td></tr><tr><td>Views</td><td>text</td><td>View Query</td><td>Views</td><td>View</td></tr><tr><td>Procedures</td><td>ROUTINE_NAME</td><td>Name</td><td>Procedures</td><td>-</td></tr><tr><td>Procedures</td><td>DESCRIPTION</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr><tr><td>Procedures</td><td>ROUTINE_DEFINITION</td><td>Procedure</td><td>Procedures</td><td>-</td></tr><tr><td>Functions</td><td>ROUTINE_NAME</td><td>Name</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>ROUTINE_DEFINITION</td><td>Function</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>DESCRIPTION</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The following are the prerequisites to establish a connection:

#### **External Supporting Files**

{% hint style="info" %}
The required external JAR files are included as part of the **OvalEdge installation artifacts**. For driver installation and configuration details, refer to the [**Connector Drivers Setup Guide**](https://docs.ovaledge.com/connectors/additional-requirements/connector-drivers-setup-guide). Please contact the **OvalEdge Team** for assistance related to the driver files and configuration setup.
{% endhint %}

<table><thead><tr><th width="207">File Name</th><th>Description</th></tr></thead><tbody><tr><td>JDBC driver file (RedshiftJDBC42)</td><td>Use this file to enable connectivity with Amazon Redshift without relying on the AWS SDK. Place the file in the <strong>Third Party Jars</strong> folder.</td></tr></tbody></table>

#### **Whitelisting Ports**

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

{% hint style="warning" %}
*The default port number for Amazon Redshift is 5439. 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 Amazon Redshift is properly established.*
{% endhint %}

#### **Service Account User Permissions**

{% hint style="warning" %}
*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.*
{% endhint %}

{% hint style="info" %}
👨‍💻 **Who can provide these permissions?** These permissions are typically granted by the Amazon Redshift administrator, as users may not have the required access to assign them independently.
{% endhint %}

<table><thead><tr><th width="114">Operation</th><th width="131">Objects</th><th width="303">pg_catalog Tables</th><th width="180">Access Permissions</th><th width="553">Comment</th></tr></thead><tbody><tr><td>Crawling</td><td>Schema</td><td>pg_catalog.pg_namespace, SVV_EXTERNAL_SCHEMAS</td><td>USAGE, SELECT</td><td>Requires access to the pg_catalog.pg_namespace to crawl schema and schema comments into OvalEdge. SVV_EXTERNAL_SCHEMAS is to crawl external schemas and tables</td></tr><tr><td>Crawling</td><td>Tables</td><td>INFORMATION_SCHEMA.TABLES, pg_catalog.pg_class, SVV_EXTERNAL_TABLES</td><td>SELECT</td><td>Requires access to catalog tables and table comments into OvalEdge</td></tr><tr><td>Crawling</td><td>Table Columns</td><td>INFORMATION_SCHEMA.COLUMNS, INFORMATION_SCHEMA.TABLE_CONSTRAINTS, SVV_EXTERNAL_COLUMNS, INFORMATION_SCHEMA.KEY_COLUMN_USAGE, pg_catalog.pg_description</td><td>SELECT</td><td>To fetch the column name, type, length, position, constraints, and comments</td></tr><tr><td>Crawling &#x26; Lineage Building</td><td>Views</td><td>pg_catalog.pg_class, pg_get_viewdef(), pg_catalog.pg_namespace</td><td>SELECT</td><td>To fetch views code, metadata, and schema association</td></tr><tr><td>Crawling &#x26; Lineage Building</td><td>Functions/Stored Procedures &#x26; Source Code</td><td>pg_proc, PG_PROC_info, pg_namespace, pg_get_late_binding_view_cols()</td><td>SELECT</td><td>To get procedures, functions, source code from system catalogs and retrieve view column definitions</td></tr><tr><td>Crawling</td><td>Relationships</td><td>INFORMATION_SCHEMA.TABLE_CONSTRAINTS, INFORMATION_SCHEMA.KEY_COLUMN_USAGE, INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS</td><td>SELECT</td><td>To identify the constraint names for reference tables/columns and relationships</td></tr><tr><td>Profiling</td><td>Row Count</td><td>User Data Tables</td><td>SELECT</td><td>To fetch row count of tables for profiling analysis</td></tr><tr><td>Profiling</td><td>Data Profiling &#x26; Sample Data</td><td>User Data Tables</td><td>SELECT</td><td>To fetch sample rows and statistical metrics (MIN, MAX, COUNT, DISTINCT) for data profiling</td></tr><tr><td>Data Access &#x26; Query Execution</td><td>Data Query Execution</td><td>User Data Tables</td><td>SELECT</td><td>To execute user-defined SELECT queries with filtering and governance</td></tr></tbody></table>

### Connection Configuration Steps

{% hint style="warning" %}
*Users are required to have the Connector Creator role in order to configure a new connection.*
{% endhint %}

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

{% hint style="info" %}
***Note:** Fields marked with an asterisk (\*) are mandatory for establishing a connection.*
{% endhint %}

<table><thead><tr><th width="221.25">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "<strong>Redshift</strong>" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp Vault</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add Ons</td><td><ul><li>Select the checkbox for the Auto Lineage Add-On to build data lineage automatically.</li><li>Select the checkbox for Data Quality Add-On to identify data quality issues using data quality rules and anomaly detection.</li><li>Select the checkbox for the Data Access Add-On license that will enforce connector access via OvalEdge with the Data Access Management (DAM) feature enabled.</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Amazon Redshift connection              </p><p>(Example: "Redshift_Prod").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.<br>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</td></tr><tr><td>Connector Description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Server*</td><td>Enter the Amazon Redshift database server name or IP address (Example: xxxx-redshift.xxxx4ijtzasl.xx-south-1.rds.xxxx.com or 192.xxx.1.xx).</td></tr><tr><td>Port*</td><td>By default, the port number for the Amazon Redshift, "5439" is auto-populated. If required, the port number can be modified as per custom port number that is configured for your Redshift.</td></tr><tr><td>Database*</td><td>Enter the database name to which the service account user has access within the Redshift.</td></tr><tr><td>Driver*</td><td>By default, the Redshift driver details are auto-populated. </td></tr><tr><td>Username*</td><td>Enter the service account username set up to access the Amazon Redshift database (Example: "oesauser").</td></tr><tr><td>Password*</td><td>Enter the password associated with the service account user.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Amazon Redshift database:</p><ul><li>Automatic Mode: The system generates a connection string based on the provided credentials.</li><li>Manual Mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to Database Name.</p></td></tr><tr><td>Plugin Server</td><td>Enter the server name when running as a plugin server.</td></tr><tr><td>Plugin Port</td><td>Enter the port number on which the plugin is running.</td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="221.5"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>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.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="221.5"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="221.5"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td>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.</td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="222.75"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td>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.</td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   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.

## Manage Connector Operations

### Crawl/Profile

{% hint style="warning" %}
*To perform crawl and profile operations, users must be assigned the Integration Admin role.*
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for **crawling** and **profiling**.&#x20;

1. Navigate to the **Connectors** page and click **Crawl/Profile**.
2. Select the schemas to be crawled.
3. The **Crawl** option is selected by default. To perform both operations, select the **Crawl & Profile** radio button.
4. Click **Run** to collect metadata from the connected source and load it into the **Data Catalog**.
5. 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.

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 provides a centralized view of all configured connectors, along with their health status.

#### Managing connectors includes:

* **Connectors 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.

#### **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**: Include notes on how to access the data.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Anomaly Detection Settings**: Configure anomaly detection preferences at the connector level.
  * **Connection Pooling:** Configure database connection pool parameters to optimize database connectivity and resource utilization. For more details, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings#connection-pooling).
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

For more details, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

## 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.

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="58.3515625">S. No</th><th width="230.57421875">Error Message</th><th width="613.95703125">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Invalid username or password during connection validation</td><td><p>The credentials entered do not match the Redshift account, and the error message returned is the same one Redshift itself produces.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the username and password are correct for the service account being used.</li><li>Confirm the account has not been locked or had its password changed on the Redshift side.</li><li>Revalidate the connector after correcting the credentials.</li></ul></td></tr><tr><td>2</td><td>Connection cannot be established because the Redshift driver is missing</td><td><p>Redshift requires an external JAR file for connectivity, since it is not bundled internally with the application.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the Redshift external JAR file has been added to the environment.</li><li>Confirm the correct driver is selected in the connector configuration.</li><li>Revalidate the connection once the JAR file is in place.</li></ul></td></tr><tr><td>3</td><td>Connector saved successfully but crawling cannot be triggered</td><td><p>Saving a connector does not require validation, but crawling and data access management both require the connector to be validated first.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the connector has been validated, not just saved.</li><li>Revalidate the connector if any credential or configuration field was changed after the last validation.</li><li>Retry the crawl once validation succeeds.</li></ul></td></tr><tr><td>4</td><td>Connection fails when using a credential manager, with no clear indication why</td><td><p>A key entered for a field may not exist in the configured credential manager, in which case the system falls back to treating the entered value as a raw value rather than reporting that the key was not found.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the secret name and key are entered exactly as they exist in the credential manager.</li><li>Confirm the connector ID for the credential manager connection is correctly referenced in the Redshift connector.</li><li>Recheck each field for typing errors, since a missing key is silently treated as a raw value and will fail to connect without a clear reason.</li></ul></td></tr><tr><td>5</td><td>Certain MySQL-style or server-specific connection parameters are not available as standard fields</td><td><p>Some source configurations require additional connection parameters, such as a public key retrieval setting, that are not exposed as separate connector attributes.</p><p><strong>Resolution</strong>:</p><ul><li>Switch the connection string mode from auto to manual.</li><li>Append the required additional parameter directly to the manual connection string.</li><li>Validate the connection after the parameter is added.</li></ul></td></tr><tr><td>6</td><td>Error while validating Redshift Connection: Failed to obtain JDBC Connection; nested exception is <code>java.sql.SQLException: [Amazon](500150) Error setting/closing connection: UnknownHostException</code></td><td><p>Connection validation fails with an error, <code>UnknownHostException</code>, indicating that the specified hostname or IP address cannot be resolved or the Redshift server is unreachable.</p><p><strong>Resolution</strong>:</p><ul><li>Verify that the hostname or IP address specified in the connection settings is correct.</li><li>Confirm that the Redshift cluster is running and accessible from the application server.</li><li>Verify network connectivity and DNS resolution to ensure that the application server can reach the Redshift endpoint.</li></ul></td></tr><tr><td>7</td><td>Error while validating Redshift Connection: Failed to obtain JDBC Connection; nested exception is <code>java.sql.SQLException: [Amazon](xx) Invalid operation: database "xx" does not exist</code></td><td><p>Connection validation fails because the specified database does not exist in the Amazon Redshift cluster.</p><p><strong>Resolution</strong>:</p><ul><li>Verify that the database name specified in the connector configuration is correct.</li><li>Confirm that the database exists in the target Redshift cluster.</li><li>Update the database name in the connection settings and validate the connection again.</li></ul></td></tr><tr><td>8</td><td><code>ERROR: S3ServiceException: User is not authorized to perform: s3:ListBucket</code></td><td><p>The IAM role associated with the Amazon Redshift cluster or session does not have sufficient permissions to access the target Amazon S3 bucket or prefix.</p><p><strong>Resolution</strong>:</p><ul><li>Update the IAM policy associated with the Redshift role to include the required S3 permissions.</li><li>Grant the <code>s3:ListBucket</code> permission on the target S3 bucket and configure the required resource or prefix restrictions, where applicable.</li><li>Verify that the IAM role is correctly associated with the Redshift cluster or session.</li><li>Retry the operation after updating the permissions.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling/Profiling" %}

<table><thead><tr><th width="58.57421875">S. No</th><th width="162.40234375">Error Message</th><th width="570.20703125">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Crawl fails to read metadata for schemas, tables, views, or other objects</td><td><p>The service account used for the connector does not have the required SELECT or USAGE permissions on the relevant system views.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm that SELECT and SELECT permissions are granted for retrieving schema-level metadata.</li><li>Confirm SELECT permissions are granted for tables, views, procedures, and functions.</li><li>Recrawl after the required permissions are granted.</li></ul></td></tr><tr><td>2</td><td>External views are missing from the catalog even though they exist in Redshift</td><td><p>The Redshift connector crawls external tables, except those whose names contain <code>_csv</code>. External tables with <code>_csv</code> in their names are excluded from cataloging.</p><p><strong>Resolution</strong>:</p><ul><li>Verify whether the external table name contains <code>_csv</code>, as these tables are excluded from cataloging.</li><li>For external tables without <code>_csv</code> in their names, confirm that the service account has the required permissions to access the external schema and tables.</li><li>Confirm the view is a supported external view type before expecting it to be catalogued.</li><li>Run the crawl again and review the crawl job logs to identify any errors preventing the external tables from being cataloged.</li></ul></td></tr><tr><td>3</td><td>Materialized views do not appear in the catalog</td><td><p>Materialized views are not supported by this connector.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the object in question is a materialized view.</li><li>Do not expect materialized views to be catalogued, since this is a known limitation.</li><li>Use a standard view or table as an alternative where possible.</li></ul></td></tr><tr><td>4</td><td>Profiling does not run for a large table even though a row count limit is configured</td><td><p>The behavior depends on the profiling mode selected. In auto mode, if the table exceeds the configured row count limit, the system falls back to sample profiling. In query mode, the system does not fall back and processes only up to the configured row count limit.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm which profiling mode is selected: auto, query, or sample.</li><li>For query mode, confirm the row count limit is appropriate, since it will not expand automatically for larger tables.</li><li>Switch to auto mode if a fallback to sample profiling is the desired behavior for oversized tables.</li></ul></td></tr><tr><td>5</td><td>Profiling jobs take a very long time to complete on large datasets</td><td><p>Profiling runs on a single thread by default, which processes tables sequentially.</p><p><strong>Resolution</strong>:</p><ul><li>Increase the number of threads configured for profiling to run tables in parallel.</li><li>Confirm that no other heavy jobs are running in parallel, since additional threads increase memory usage.</li><li>Schedule profiling within a defined time window if faster performance is needed only during off-hours.</li></ul></td></tr><tr><td>6</td><td>Profiling jobs run outside the expected daily window</td><td><p>A profiling schedule window, such as a start and end time, may not be configured, or the configured window does not match the intended working hours.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm that the start time and end time settings are configured for the profiling job.</li><li>Confirm the configured window matches the intended working hours.</li><li>Adjust the schedule and save the settings using the correct save control.</li></ul></td></tr><tr><td>7</td><td>Changed settings on the connector settings page do not take effect</td><td><p>Clicking the general Save Changes button at the bottom of the page does not apply settings; a separate save icon must also be used.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm that the specific save icon associated with the setting was clicked, not only the Save Changes button.</li><li>Reopen the settings page to confirm the change was actually applied.</li><li>Reapply the setting if it was not saved, since this is a known interface inconvenience.</li></ul></td></tr><tr><td>8</td><td>Include or exclude schema rules do not appear to reduce load on the source system</td><td><p>Regular expression filtering is applied at the application level after all data has already been queried from Redshift, not at the source system query level.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the regular expression pattern is correct for the intended schema, table, or column filtering.</li><li>Understand that filtering happens after data retrieval, so it reduces what is catalogued but not what is queried from the source.</li><li>Review crawl performance expectations accordingly when working with very large sources.</li></ul></td></tr><tr><td>9</td><td>Triggers appear as a supported object in documentation but are not available in the application</td><td><p>Triggers are not actually supported for this connector, and the documentation listing them is outdated.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the object type in question is a trigger.</li><li>Do not expect trigger metadata to be catalogued, regardless of documentation references.</li><li>Refer to supported objects as tables, views, columns, procedures, functions, and relationships.</li></ul></td></tr><tr><td>10</td><td>Unsupported Datatype</td><td><p>Profiling is skipped for columns where the column length exceeds the configured profiling size limit (default: 4000). This behavior is intentional to avoid performance issues during profiling.</p><p><strong>Resolution</strong>:</p><ul><li>Review the warning logs to identify columns skipped during profiling.</li><li>Review the configured profiling size limit and adjust it if required.</li><li>Exclude large columns from profiling where profiling is not required.</li></ul></td></tr><tr><td>11</td><td><code>ERROR: schema "pg_temp_91" does not exist</code></td><td><p>The query references a temporary schema that no longer exists. Temporary schemas in Amazon Redshift are session-based and are automatically removed when the session ends or when temporary objects are dropped.</p><p><strong>Resolution</strong>:</p><ul><li>Verify whether the referenced temporary schema exists in the active Redshift session.</li><li>Ensure that the temporary tables or schemas referenced by the query are available during execution.</li><li>Re-run the operation using valid and active schemas.</li></ul></td></tr><tr><td>12</td><td><code>ERROR: Query (&#x3C;query_id>) cancelled on user's request</code></td><td><p>Query execution is interrupted due to manual cancellation, query timeout settings, resource constraints, or administrative actions in Amazon Redshift.</p><p><strong>Resolution</strong>:</p><ul><li>Execute the failed query directly in Redshift to evaluate its execution time.</li><li>Increase the query timeout value in the connection pooling settings, if required.</li><li>Optimize long-running queries or reduce the profiling scope for large datasets.</li></ul></td></tr><tr><td>13</td><td><code>ERROR: permission denied for schema pg_autocopy</code> and <code>ERROR: permission denied for schema pg_automv</code></td><td><p>The service account does not have sufficient privileges to access Redshift system-managed schemas such as <code>pg_autocopy</code> or <code>pg_automv</code>.</p><p><strong>Resolution</strong>:</p><ul><li>Grant the required USAGE or SELECT permissions on the respective schemas, where access is required.</li><li>Verify that the service account has sufficient privileges to access the system schemas involved in crawling or profiling.</li><li>Retry the operation after updating the required permissions.</li></ul></td></tr><tr><td>14</td><td>Error while retrieving Redshift SQL Profile Results: <code>Amazon Invalid operation: could not identify an equality operator for type "unknown"</code></td><td><p>The profiling operation fails while retrieving SQL profile results because the generated query includes a DISTINCT operation on a column type for which Amazon Redshift cannot identify a valid equality operator. This can occur when profiling unsupported, ambiguous, or incompatible data types.</p><p><strong>Resolution</strong>:</p><ul><li>Verify the data type of the affected column and confirm that it supports comparison and DISTINCT operations in Amazon Redshift.</li><li>Review the table schema to identify columns with unsupported, custom, or ambiguous data types that may be interpreted as <code>unknown</code>.</li><li>Modify the affected column to use a supported Redshift data type, if required.</li><li>Exclude unsupported columns from profiling when DISTINCT-based metrics are not applicable.</li><li>Validate the query directly in Amazon Redshift to identify the column causing the failure.</li><li>Retry the profiling operation after updating the schema or profiling configuration.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="DAM" %}

<table><thead><tr><th width="58.44921875">S. No</th><th width="163">Error Message</th><th width="557.87890625">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>DAM instance does not appear after enabling the DAM checkbox</td><td><p>Data Access Management (DAM) instance creation happens only after the connection has been validated and saved.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the connector has been validated successfully.</li><li>Confirm the connector has been saved after validation.</li><li>Reopen the DAM screen to check whether the instance now appears.</li></ul></td></tr><tr><td>2</td><td>Roles, groups, or users do not appear in the DAM screen after enabling DAM</td><td><p>Role, group, and user information populates only after an instance-level or connector-level crawl has been initiated for DAM.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the DAM crawl checkbox was selected and the crawl was run.</li><li>Confirm the service account has the specific permissions required for DAM crawling, which differ from standard metadata crawling permissions.</li><li>Recrawl and check the Roles, Groups, and Users tabs again.</li></ul></td></tr><tr><td>3</td><td>Not all roles from the source system appear as synced in the application</td><td><p>Only roles that are actively assigned to an object in Redshift are synced into the application; unused roles are not brought over.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the role is assigned to at least one object in the source system.</li><li>Recrawl after assigning the role to an object if it needs to be synced.</li><li>Expect roles with no object assignment to remain absent from the application.</li></ul></td></tr><tr><td>4</td><td>A user does not appear to have their Redshift role reflected in the application</td><td><p>User accounts are not created automatically in the application to protect license counts; only roles are synced, and the role is linked only if a matching user already exists in the application.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm whether the corresponding user already exists in the application, since new users are never created automatically from Redshift.</li><li>Confirm the role itself is assigned to an object in the source system so that it can sync.</li><li>Manually assign the synced role to the existing application user if needed.</li></ul></td></tr><tr><td>5</td><td>Changing data permissions or roles appears to take time to reflect</td><td><p>Permission and role updates run as a background sync operation rather than completing instantly.</p><p><strong>Resolution</strong>:</p><ul><li>Wait for the sync operation shown on screen to complete.</li><li>Confirm the operation continues even if navigating to another screen, since syncing runs in the background.</li><li>Refresh the screen after the sync completes to see the updated permissions.</li></ul></td></tr><tr><td>6</td><td>Bulk removal of a role, group, or user from multiple schemas does not show the expected items</td><td><p>The system can only display and remove roles, groups, or users that are common across all the selected schemas.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the role, group, or user being removed is actually present on every selected schema.</li><li>Select a smaller or more consistent set of schemas if the removal needs to target items not common to all of them.</li><li>Perform individual removals for schemas with unique role, group, or user assignments.</li></ul></td></tr><tr><td>7</td><td>Connection timeout occurs while bringing in roles, groups, and users through DAM</td><td><p>The default timeout of 180 seconds may not be sufficient for queries running in the background for DAM crawling.</p><p><strong>Resolution</strong>:</p><ul><li>Open the connector or instance-level timeout settings.</li><li>Increase the timeout value beyond the default of 180 seconds.</li><li>Re-run the DAM crawl once the timeout has been adjusted.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Masking Policies" %}

<table data-search="true"><thead><tr><th width="58.5546875">S. No</th><th width="163.14453125">Error Message</th><th width="548.76171875">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Assigned users or roles can still see raw data when a masking policy was meant to hide it, or the reverse</td><td><p>Redshift masking behavior is the opposite of what the application assumes by default: assigned roles and users are the ones restricted by the masking policy, rather than the ones permitted to see raw data.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm which direction the masking policy is intended to work for the roles and users selected.</li><li>Create two separate masking policies, one representing the raw unmasked view and one representing the masked view with lower priority.</li><li>Assign these two policies together using priority settings so the correct users see raw data and others see the masked value.</li></ul></td></tr><tr><td>2</td><td>Only a limited number of masking policies appear when assigning one to a column</td><td><p>Available masking policies are filtered based on the column’s data type, so not every masking policy created for the database applies to every column.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the data type of the column being assigned a masking policy.</li><li>Review only the masking policies compatible with that data type.</li><li>Create a new masking policy matching the column’s data type if none of the existing ones fit.</li></ul></td></tr><tr><td>3</td><td>The option to assign a masking policy to a table column does not appear</td><td><p>This has been identified as a display issue in the column security assignment interface.</p><p><strong>Resolution</strong>:</p><ul><li>Refresh the page and attempt the assignment again.</li><li>Confirm whether the masking policy exists and is associated with the correct database.</li><li>Escalate to the support team if the assignment option continues to not appear.</li></ul></td></tr><tr><td>4</td><td>Masking policy created or removed in the application does not match what appears in Redshift</td><td><p>Enabling both the application-to-remote sync and the remote-to-application sync for masking policies at the same time can cause conflicting updates, especially since Redshift allows multiple masking policies on a single column.</p><p><strong>Resolution</strong>:</p><ul><li>Use only one synchronization direction at a time, either application to remote or remote to application, to avoid confusion.</li><li>Confirm which masking policies already exist directly in Redshift before making changes in the application.</li><li>Avoid removing masking policies from within the application, since removal is intentionally restricted due to the risk of deleting the wrong policy when multiple policies exist on one column.</li></ul></td></tr><tr><td>5</td><td>Row level visibility does not change after enabling or disabling a row access policy in the application</td><td><p>Row visibility in the data tab depends on the permissions of the service account used to log in at the source, not on syncing configured within the application.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the row access policy is enabled or disabled using the switch provided, rather than attempting to remove it.</li><li>Confirm the service account’s permissions in Redshift reflect the intended row-level access.</li><li>Understand that row access policy enforcement depends on remote permissions, since there is no syncing mechanism from the application back to Redshift for this policy type.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## FAQs

{% tabs %}
{% tab title="Connectivity" %}

<table><thead><tr><th width="58.82421875">S. No</th><th width="164.41796875">Question</th><th width="571.828125">Answer</th></tr></thead><tbody><tr><td>1</td><td>What is the Amazon Redshift connector used for?</td><td><p>Redshift is an AWS cloud data warehouse. The connector brings its structure into the application as a JDBC-based connector.</p><ul><li>Schemas, tables, views, columns, procedures, functions, and relationships are catalogued.</li><li>Profiling, lineage, and data access management are supported.</li><li>The connector is available from release 4 onward, with the current documented version being 7.1.</li></ul></td></tr><tr><td>2</td><td>What is required to set up the connection?</td><td>A server name, port, database name, driver information, username, and password are required. An external Redshift JAR file must also be available, since it is not bundled internally.</td></tr><tr><td>3</td><td>How does the credential manager option work for this connector?</td><td><p>A credential manager, such as HashiCorp, AWS Secrets Manager, or Azure Key Vault, can be used in place of raw values.</p><ul><li>A separate credential manager connection must be created first, and its connector ID referenced in the Redshift connector.</li><li>Each field, such as database, username, or password, takes a key name rather than a raw value.</li><li>If the key exists in the credential manager, its value is retrieved; if not, the entered text is treated as a raw value.</li></ul></td></tr><tr><td>4</td><td>Is there a risk when using a credential manager key that does not exist?</td><td>Yes. If a key does not exist in the credential manager, the system does not report an error about the missing key. Instead, it treats the entered text as a raw value and attempts to connect with it directly, which can fail without clearly indicating that the real issue was a missing or mistyped key.</td></tr><tr><td>5</td><td>When should the manual connection string option be used instead of auto?</td><td>Manual mode is used when an additional connection parameter is needed that is not available as a standard connector field, such as a specific setting required by the source system. The extra parameter can be appended directly to the connection string without needing a new attribute added to the connector.</td></tr><tr><td>6</td><td>Does the connector need to be validated before it can be saved?</td><td>No, a connector can be saved without validation. However, validation is required before crawling can be performed, and the same requirement applies to data access management.</td></tr><tr><td>7</td><td>Is the username and password stored securely?</td><td>Yes. Credentials are encrypted when stored. For SaaS environments using database authentication, credentials are stored in AWS Secrets Manager.</td></tr><tr><td>8</td><td>Are there restrictions on special characters in the connection name?</td><td>This was raised as an open question during training and had not been confirmed at the time of the session. It is expected to be documented separately once verified.</td></tr><tr><td>9</td><td>What does the number of objects or plug-in server field do?</td><td>The number of objects field relates to versioning functionality and is not generally used for this connector. The plug-in server field supports running the connector library outside the main application, intended for bridge light deployment cases.</td></tr><tr><td>10</td><td>Which license add-ons are supported for Redshift?</td><td>Autolineage, data quality, and data access management are supported as license add-ons for the Redshift connector.</td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling/Profiling" %}

<table><thead><tr><th width="59.109375">S. No</th><th width="163.23046875">Question</th><th width="555.88671875">Answer</th></tr></thead><tbody><tr><td>1</td><td>What objects are supported for crawling?</td><td>Schemas, tables, views, columns, procedures, functions, and relationships are supported. Triggers and materialized views are not supported. External views are supported only when their names end with a CSV suffix.</td></tr><tr><td>2</td><td>What permissions does the service account need for crawling and profiling?</td><td>Usage and select permissions are needed to read schema metadata, with select permissions needed on tables, views, procedures, and functions as well. Query execution for the data tab and query sheet also requires select permission.</td></tr><tr><td>3</td><td>What are the different profiling modes?</td><td><p>Four modes are available.</p><ul><li>Disable, which turns off profiling entirely.</li><li>Auto, which performs full profiling up to a configured row count limit, falling back to sample profiling if the table exceeds that limit.</li><li>Query, which profiles only up to the configured row count limit without falling back to sampling if exceeded.</li><li>Sample, which profiles a fixed number of rows specified as the sample size.</li></ul></td></tr><tr><td>4</td><td>How does the number of threads setting affect profiling performance?</td><td>More threads allow more tables to be profiled in parallel, which speeds up profiling for large numbers of tables. This should generally be used only when no other jobs are running in parallel, since higher thread counts consume more system memory.</td></tr><tr><td>5</td><td>What does the sample data count setting control?</td><td>It controls how many rows are shown on the table data preview page, separate from the profiling row count settings.</td></tr><tr><td>6</td><td>Can profiling and crawling schedules be restricted to certain hours?</td><td>Yes. A start time and end time can be configured so that profiling jobs only run within that window, such as limiting jobs to standard working hours.</td></tr><tr><td>7</td><td>How are include and exclude schema rules applied?</td><td>Regular expression patterns can be configured for schemas, tables, columns, procedures, and functions to control which objects are crawled. These rules are applied at the application level after data is retrieved from the source, not at the source system query level.</td></tr><tr><td>8</td><td>What are the two query policy options?</td><td><p>Two policies are available.</p><ul><li>Application follows application data permissions, where the service account credentials are used automatically, with no separate login prompt.</li><li>Application follows remote system permissions, where users must enter their own credentials when accessing the data tab, query sheet, or data catalog queries.</li></ul></td></tr><tr><td>9</td><td>Where can connection and query timeout settings be adjusted?</td><td>These were moved to the connection pooling settings section, which includes connection timeout and validation timeout options, replacing an earlier separate profiler timeout setting.</td></tr></tbody></table>
{% endtab %}

{% tab title="DAM" %}

<table><thead><tr><th width="58.578125">S. No</th><th width="206.5234375">Question</th><th width="584.87109375">Answer</th></tr></thead><tbody><tr><td>1</td><td>How is a DAM instance created?</td><td>A DAM instance is created automatically once the connection has been validated and saved. If multiple connections share the same IP address, they are grouped together under a single DAM instance.</td></tr><tr><td>2</td><td>What is the difference between instance-level and connector-level settings in DAM?</td><td>Instance-level settings, such as data access admins and timeouts, apply across all connections sharing that instance and work independently once set. Connector-level settings apply to that specific Redshift connection only.</td></tr><tr><td>3</td><td>What does DAM crawling actually bring in?</td><td>DAM crawling captures roles, groups, and users at the instance level, along with their associated privileges, group memberships, and password expiry details where available from Redshift.</td></tr><tr><td>4</td><td>Are users imported into the application through DAM syncing?</td><td>No. Users are not created automatically in the application, since doing so would increase license usage. The system checks whether a matching user already exists before linking any role information to that user.</td></tr><tr><td>5</td><td>Why are roles synced into the application if users are not?</td><td>Synced roles can be used within masking policies and allow permission parity with the source system without creating new licensed users. Only roles that are actively assigned to an object in the source system are synced.</td></tr><tr><td>6</td><td>What is the difference between system roles and remote roles?</td><td>Roles created directly within the application are considered system roles and cannot be deleted or modified once created, since they are treated as immutable. Roles that originate from the source system are labeled as remote roles.</td></tr><tr><td>7</td><td>Can role creation, editing, or deletion be restricted to certain users?</td><td>Yes. Permission settings control whether a user can add, edit, or delete roles, groups, or users within the DAM screen.</td></tr><tr><td>8</td><td>What do the notification settings in DAM control?</td><td><p>Notifications can be configured for two categories.</p><ul><li>Source system sync events, triggered each time a crawl runs.</li><li>Changes made directly within the DAM screen, such as adding, editing, or removing roles, groups, or users.</li></ul><p>Notifications are sent to configured data access admins, application users, teams, or roles.</p></td></tr><tr><td>9</td><td>What does enabling manage data permissions allow?</td><td>It allows schema and table-level permission operations to be performed directly from the DAM screen, including adding, replacing, or removing roles, groups, and users, either individually or in bulk across multiple schemas.</td></tr><tr><td>10</td><td>What is the difference between adding and replacing permissions?</td><td>Adding permissions supplements the existing configuration without removing anything already assigned. Replacing permissions overwrites the entire existing set with only the new parameters defined in that operation.</td></tr><tr><td>11</td><td>Does Redshift support table column level permissions?</td><td>No. Unlike Snowflake, Redshift does not support permissions at the table column level within this connector; permissions are managed at the schema and table level.</td></tr></tbody></table>
{% endtab %}

{% tab title="Masking Policies" %}

<table><thead><tr><th width="58.96875">S. No</th><th width="200.66796875">Question</th><th width="586.80078125">Answer</th></tr></thead><tbody><tr><td>1</td><td>How do masking policies in Redshift differ from Snowflake?</td><td>In Snowflake, users or roles given access through a masking policy can see the raw data. In Redshift, this is reversed: the roles and users assigned to a masking policy are the ones who are restricted and see the masked value, not the raw data.</td></tr><tr><td>2</td><td>How does the application handle the reversed Redshift masking behavior?</td><td>Two separate masking policies are typically created: one representing the full raw data view and one representing the masked view. These are combined using priority settings so that the intended users see raw data while everyone else sees the masked version.</td></tr><tr><td>3</td><td>Can multiple masking policies be applied to a single column in Redshift?</td><td>Yes. Unlike Snowflake, which allows only one masking policy per column, Redshift supports multiple masking policies on a single column, with priority settings determining how they are applied together.</td></tr><tr><td>4</td><td>Why can masking policies not be removed directly from the application?</td><td>Because Redshift can have multiple masking policies on a single column, the application cannot always determine which specific policy should be removed. To avoid deleting the wrong policy or corrupting the configuration, removal from the application is intentionally restricted.</td></tr><tr><td>5</td><td>What is the difference between the business masking policy and the technical masking policy options?</td><td>The business masking policy option lets a masking rule be defined using the application’s own schema-based query generation, which is translated and applied to Redshift automatically. The technical masking policy option allows the actual Redshift-style masking policy syntax to be entered directly, mirroring what would be created natively in Redshift.</td></tr><tr><td>6</td><td>Should both masking policy sync directions be enabled at the same time?</td><td>This is generally discouraged. Enabling both the sync from Redshift to the application and from the application to Redshift at the same time can create confusion, since masking changes are sensitive, and an unintentional removal in one direction could be misread as an intentional change in the other.</td></tr><tr><td>7</td><td>What are row access policies and how are they different from masking policies?</td><td>Masking policies hide or alter values within specific columns. Row access policies (RLS or Row-Level Security) control which rows of a table are accessible based on the defined policies. OvalEdge supports attaching, detaching, and dropping RLS policies in Redshift. However, the Data tab preview runs using the OvalEdge service account rather than the logged-in user's credentials. Therefore, row visibility in the Data tab may not reflect the RLS restrictions applicable to individual users.</td></tr><tr><td>8</td><td>Can multiple row access policies be applied to one table?</td><td>Yes. Multiple row access policies can be assigned to a single table, with an option to apply either one specific policy or all of them together. Each policy can be enabled or disabled using a switch rather than being removed.</td></tr><tr><td>9</td><td>Does the application sync row access policy changes back to Redshift?</td><td>No. There is no synchronization mechanism for row access policies between the application and Redshift, since they are not associated with a schema-level business masking concept. Visibility is instead driven entirely by the permissions assigned to the service account within Redshift itself.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

&#x20; Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/data-warehouse/amazon-redshift.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
