Feedback
Did this article resolve your question/issue?

   

Article

Connect64 for ODBC Greenplum driver hangs after "out of memory" error

Information

 
TitleConnect64 for ODBC Greenplum driver hangs after "out of memory" error
URL NameODBC-Driver-fro-Greenplum-hangs-after-out-of-memory-error
Article Number000182807
EnvironmentProduct: Connect64 for ODBC Greenplum
Version: 07.15.0226 (B0275, U0184)
OS: Linux X64
Database: GreenPlum
Application: all supported applications
Question/Problem Description
A memory leak is witnessed when Greenplum DB returns out of memory error or is restarted.
When spawning a number of ODBC processes and the GreenPlum Db is restarted for some reason (OOM for example), not all processes are terminated and hang indefinitely.

The hanging process(es) keep consuming more and more memory. 
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC Greenplum Wire Protocol driver][Greenplum] FATAL: terminating connection due to administrator command (File postgres.c;Line 3521;Routine ProcessInterrupts;)
[DataDirect][ODBC Greenplum Wire Protocol driver]Socket closed.
Defect NumberDefect # 30920
Enhancement Number
Cause
Resolution
Fixed in hot fix 07.15.0227 (B0276, U0184). 
Refer to “Connect and Connect64 for ODBC hot fix download and install instructions” for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date1/12/2016 10:13 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.