Data Integration Connector Release Notes > Data Integration Connectors > Amazon Redshift V2 Connector

Amazon Redshift V2 Connector

Fixed issues

The following table describes fixed issues:

Issue	Description
CCON-96547	When you run multiple Amazon Redshift V2 mappings concurrently, the connector creates duplicate S3 staging locations and the mappings fail at runtime with the following error: ERROR CCITaskUtils - Unload/Copy command failed with error: [Amazon](500310) Invalid operation: Specified unload destination on S3 is not empty. (May 2024)

Known issues

The following table describes known issues:

Issue	Description
CCON-98473	When you create a mapping in SQL ELT mode to load data to Amazon Redshift, incorrect messages are logged in the session log. For example, the session log shows execution of pre-SQL and post-SQL queries even though you do not define the pre-SQL and post-SQL queries. (July 2024)
CCON-98156	When you create a mapping in SQL ELT mode to load data to Amazon Redshift, the mapping fails in the following cases: - If you use data driven or upsert target operation. - If you read a complex file from an Amazon S3 source. - If you use the Log() function with optional arguments. (July 2024)
CCON-91838	When you configure a SQL transformation with stored procedure and use in, out, and in-out parameters for columns of SUPER data type, the mapping fails with the following warning: EP_13248 DLL Error Msg: ERROR in SQL tx (November 2023)
CCON-91581	When you use COPY command to write data to an Amazon Redshift target that contains SUPER data type columns and insert a string value to a SUPER data type column, the mapping in advanced mode fails. (November 2023)
CCORE-2089	When you enable the staging optimization property for lookups configured to use persistent cache, the mapping fails at runtime for consecutive runs. (July 2023)
CCORE-1845	When you configure a lookup transformation and configure the staging optimization property for lookups, the logs are duplicated for source and lookup transformations in the session logs. (July 2023)
CCORE-1836	When you read from an Amazon Redshift source table that has NULL data in char data type and then configure the staging optimization property, the mapping is successful but there is a mismatch in the data that is written to the target. (April 2023)
CCORE-1835	When you enable the staging optimization property with the unload command ESCAPE=OFF and run a mapping to read from an Amazon Redshift source that have data delimiters, the data written to the target is truncated until the delimiter value. (April 2023)
CCORE-1834	When you enable the staging optimization property for the source and run a parameterized mapping, the mapping task runs without optimizing the performance. (April 2023)