RE: Session's memory
> -----Original Message-----
> From: owner-informix-list@iiug.org
[mailto:owner-informix-list@iiug.org] On
> Behalf Of rotor
> Subject: RE: Session's memory
>
> > Hi, rotor (Leonid ?)
> Yes, I am. :-)
[AS] Nice to see You..
>
> > onstat -g afr SESSION_ID> Don't understand what I can see here.
[AS] What type of fragments dominate here?
>
> > There is a chance that that the memory leak is caused by
> > the server bug...
> Not sure. This is IDS 7.31.TD6 - from my experience stable enough.
>
> > the application doesn't deallocate
> > the cursor or prepared SQL statement
> Yes, I also think the same. But don't know how to prove (there
> isn't '-g stm' option).
>
> Problematic session is Oracle Transparent Gateway really. Hard to
> believe that Oracle developers doesn't closes their cursors...
[AS] It might happen, the 'Gateway' itself is working normally.
May be, it is constructed to close the cursor only if 'Oracle'
application closes the cursor. BTW, Oracle applications written
in Pro/C can easily cause the same problem (memory leak if
application doesn't properly closes it's cursors) in the Oracle server.
Fortunately, with Oracle, it is possible to limit the maximal number
of session's cursors.
-Alexey
sending to informix-list