Feedback
Did this article resolve your question/issue?

   

Article

Parameter conversions are not allowed by the Amazon Redshift ODBC driver.

Information

 
TitleParameter conversions are not allowed by the Amazon Redshift ODBC driver.
URL NameRedshift-ODBC-driver-not-allowing-parameter-conversions
Article Number000117230
EnvironmentProduct : Connect for ODBC Amazon Redshift Wire Protocol driver
Version : All supported versions
Database : Amazon Redshift
OS : All supported platforms
Application : All supported applications
Question/Problem Description
The Connect for ODBC driver for Amazon Redshift does not allow a conversion for the parameter when executing a parameterized where clause. 
The backend type is an integer, but the SQLBindParameter is done with a SQL_C_CHAR/SQL_VARCHAR. When running SQLExecute with this conversion specified, below error is returned. 
 
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC Redshift Wire Protocol driver][Redshift]ERROR: insufficient data left in message(File /home/awsrsqa/padb/src/pg/src/backend/libpq/pqformat.c; Line 609; Routine pq_copymsgbytes; )
Defect NumberDefect 32689
Enhancement Number
Cause
Resolution
Fixed in hot fix 07.16.0090.
Refer to Connect for ODBC and Connect64 hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date3/31/2016 11:45 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.