Re: doubt in onstat -g ses

In article <34983772.6D85@bloomberg.com>, "Art S. Kagel" <kagel@bloomberg.com> writes >bala peddi wrote: >> >> Could anyone please explain me the meaning of the following state of >> the informix session. This the out put of >> >> One of the client application is connecting through ESQL/C program and >> this application is will not close the informix session , it runs 7 x >> 365 >> days. This application reads SQL from user and submits it informix >> through the existing session that it had already open >> >> Thia is snapshot of onstat -g ses 1123 when there is no SQL is running > >I've seen the same behavior from time to time. We can usually track it >to an application that is reopening cursors that have never been closed. > >Check the code of this SQL server and make sure that there is no code >path that can return to the calling function or process without closing >all open cursors. > >Art S. Kagel I have seen something similar when we run a Dephi 1 application against the database. We are using Intersolve 2.5 ODBC drivers and find that the each time we run a query the memory allocated to the session INCREASES. We DO close the query but still the memory keeps rising. >95% of the memory is in the 'ralloc' pool. This has even reached 24Mb for a session and causing online to allocate 11(!!) more virtual segments. After the session is disconnected onmode -F WILL free the memory. Informix reckon the ODBC driver needs to be compile with '-edc' flag and Intersolv are currently invesigating. We've been asked to use SQLIDEBUG to trace the session and use sqliprint to printout the trace. Has anyone else had this problem. This is against Online 7.12 so Online 7.2 undocumented onstat options will not help. Any idea under Online 7.1x how you find out what the memory allocated to a sesssion is used for? PS Please note I have NEVER said it was a bug just a problem which is under investigation by the ODBC Vendor!!! -- David Williams