Release Notes > Connector and connectivity issues > Amazon Redshift V2 Connector
  

Amazon Redshift V2 Connector

Fixed issues

The tables in this section describe recent fixed issues for Amazon Redshift V2 connector in Metadata Command Center. Not all monthly releases include fixed issues.
October 2026 fixed issues
Issue
Description
SCAN-35241
When you run a metadata extraction job, view column assets appear to reference themselves instead of their source table columns.
This issue occurs when the standard information schema in the database does not include view column metadata.
SCAN-42574
When you run a metadata extraction job on a Redshift view whose definition uses a scalar function expression as the LIMIT value, the job fails with the following error: Parse error (NoViableAlt) on token
SCAN-40667
When you run a metadata extraction job on views or stored procedures, the job fails with the following PL/SQL parsing error:
Parse error(NoViableAlt) on token or Failed to process PL/SQL call. Too many arguments in call.
This issue occurs due to unsupported grammar tokens and function signatures in the Redshift source scripts and views.
April 2026 fixed issues
Issue
Description
SCAN-30614
When you run a metadata extraction job on stored procedures that contain the 'WITH' keyword, the job fails with an error.
November 2025 fixed issues
Issue
Description
SCAN-24111
When you specify additional parameters in the JDBC URL to connect to the Amazon Redshift cluster and run a catalog source job, Data Governance and Catalog appends the additional parameter to the database name.
July 2025 fixed issues
Issue
Description
CDGC-79527
Data profiling tasks on databases fail with the following error: Workflow generation failed for object: java.lang.ClassCastException