Feedback
Did this article resolve your question/issue?

   

Article

OpenAccess ODBC Client "Out Of Memory" error when fetching large varchar columns

Information

 
TitleOpenAccess ODBC Client "Out Of Memory" error when fetching large varchar columns
URL Nameopenaccess-odbc-client-out-of-memory-error-when-fetching-large-varchar-columns
Article Number000117031
EnvironmentProduct: OpenAccess SDK
Version: All supported versions
OS: All supported platforms
Database: Hive
Application: All supported applications
Question/Problem Description
Using OpenAccess in pass through mode to Hive, an error occurs when fetching data from string data type.
The backend JDBC driver describes the string data type as VARCHAR(2147483647).
The actual data in the rows is a maximum of 50 characters.
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC OpenAccess SDK driver]Out Of Memory
Defect Number
Enhancement Number
Cause
OpenAccess allocates the buffer based on the column size.
Resolution
In the IP, map the string column to LONGVARCHAR or WLONGVARCHAR.  This will cause OpenAccess to return the data in chunks to the client.
It is recommended when data is larger than ~8K to use the long data type.
Workaround
Notes
Last Modified Date2/21/2018 9:30 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.