Feedback
Did this article resolve your question/issue?

   

Article

"String data code page conversion failed" or "Invalid string or buffer length" error with ODBC Greenplum driver

Information

 
Title"String data code page conversion failed" or "Invalid string or buffer length" error with ODBC Greenplum driver
URL NameString-data-code-page-conversion-failed-or-Invalid-string-or-buffer-length-error-with-ODBC-Greenplum-driver
Article Number000185141
EnvironmentProduct: Connect64 for ODBC Greenplum driver
Version: 7.1
OS: Windows
Database: Greenplum
Application: all supported applications
Question/Problem Description
One of the below errors is returned intermittently when using the driver with the JDBC/ODBC bridge.
Steps to Reproduce
Clarifying Information
Error MessageWith v 7.1.0:

[DataDirect][ODBC Greenplum Wire Protocol driver]String data code page conversion failed.

With v 7.1.5:

[Microsoft][ODBC Driver Manager] Invalid string or buffer length
Defect Number
Enhancement Number
Cause
Resolution
Use the Connect for JDBC Greenplum driver instead of the Connect64 for ODBC Greenplum driver and the JDBC/ODBC bridge.

The issue is not related to the driver. After correcting the java application, the errors do no longer occur.
Workaround
Notes
Last Modified Date4/27/2016 1:04 PM
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.