OK folks, let's get the debate back on track please! The original
question was asking about possible causes of the following error:
ERROR [HY001] [Informix][Informix ODBC Driver]Memory allocation failure
I am a .NET programmer and so to me the error implies that the ODBC
driver is hogging memory client-side. So - if that is true - I want to
know how to be able to monitor that? If it is instead an internal
informix error, then onstat will be of use.
In any case - and this is the ultimate aim - is there anything I can do
within my calls to the ODBC driver to avert this?
Thanks
↪ replying to mauroc@beacon-ct.co.uk
mauroc@beacon-ct.co.uk wrote:
> OK folks, let's get the debate back on track please! The original
> question was asking about possible causes of the following error:
>
> ERROR [HY001] [Informix][Informix ODBC Driver]Memory allocation failure
>
> I am a .NET programmer and so to me the error implies that the ODBC
> driver is hogging memory client-side. So - if that is true - I want to
> know how to be able to monitor that? If it is instead an internal
> informix error, then onstat will be of use.
>
> In any case - and this is the ultimate aim - is there anything I can do
> within my calls to the ODBC driver to avert this?
>
> Thanks
>
You need to step though your code and when a DB connection is made, look
at the onstat -g ses for the session. It will have used x memory, keep
stepping through the code and check when you close the connection the
memory is realised. If it's not AND you are closing the connection then
I would start to suspect the driver. If it;s not AND you are NOT
closing the connection then this is probabyl your problem , you are
opening connections and not closing them
--
Paul Watson #
Oninit Ltd # Growing old is mandatory
Tel: +44 1436 672201 # Growing up is optional
Fax: +44 1436 678693 #
Mob: +44 7818 003457 #
www.oninit.com #