doubt in onstat -g ses

[bala peddi]

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

Thanks in advance for your help

PEDDI
bala....@fmr.com

INFORMIX-OnLine Version 7.23.UC2 -- On-Line -- Up 11 days 19:10:45 --
416472 Kbytes

session #RSAM total used
id user tty pid hostname threads memory memory
689 navuser console 1894 cali.fmr 1 286720 134584

tid name rstcb flags curstk status
16573 sqlexec c042a18 Y--P--- 1872 c042a18 cond wait(netnorm)

Memory pools count 3
name class addr totalsize freesize #allocfrag #freefrag
689 V c46e018 221184 104208 391 49
689_SORT_0 V c3de018 32768 15904 7 2
689_SORT_1 V cb8e018 32768 32024 12 3

name free used name free used
overhead 0 360 scb 0 96
opentable 0 7624 filetable 0 912
ru 0 224 log 0 2136
temprec 0 3144 ralloc 0 68952
gentcb 0 8472 ostcb 0 2016
sort 0 17520 sqscb 0 8288
srtmembuf 0 144 rdahead 0 448
hashfiletab 0 280 osenv 0 2280
buft_buffer 0 8544 sqtcb 0 2344
fragman 0 448 shmblklist 0 352

Sess SQL Current Iso Lock SQL ISAM F.E.
Id Stmt type Database Lvl Mode ERR ERR Vers
689 - nav30prod NL Not Wait 0 0 7.20

Last parsed SQL statement :

select * from xxx;

[Art S. Kagel]

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

[David Williams]

In article <3497ED...@fmr.com>, bala peddi <bala....@fmr.com>
writes

>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
>

>Thanks in advance for your help
>
>PEDDI
>bala....@fmr.com
>
>
>INFORMIX-OnLine Version 7.23.UC2 -- On-Line -- Up 11 days 19:10:45 --
>416472 Kbytes
>
>session #RSAM total used
>id user tty pid hostname threads memory memory
>689 navuser console 1894 cali.fmr 1 286720 134584

^^^^
pid of 'client'.

>
>tid name rstcb flags curstk status
>16573 sqlexec c042a18 Y--P--- 1872 c042a18 cond wait(netnorm)

^^^^^^^^^^^^^^^^^^

This is a normal wait for a reply from the 'network' i.e. it is
waiting for the client to send something.

>
>Memory pools count 3
>name class addr totalsize freesize #allocfrag #freefrag
>689 V c46e018 221184 104208 391 49
>689_SORT_0 V c3de018 32768 15904 7 2
>689_SORT_1 V cb8e018 32768 32024 12 3

^^^^^^^^^^
Temporary memory pools used for sorting.

>
>name free used name free used
>overhead 0 360 scb 0 96
>opentable 0 7624 filetable 0 912
>ru 0 224 log 0 2136
>temprec 0 3144 ralloc 0 68952
>gentcb 0 8472 ostcb 0 2016
>sort 0 17520 sqscb 0 8288
>srtmembuf 0 144 rdahead 0 448
>hashfiletab 0 280 osenv 0 2280
>buft_buffer 0 8544 sqtcb 0 2344
>fragman 0 448 shmblklist 0 352
>
>Sess SQL Current Iso Lock SQL ISAM F.E.
>Id Stmt type Database Lvl Mode ERR ERR Vers
>689 - nav30prod NL Not Wait 0 0 7.20
>
>Last parsed SQL statement :
>
>select * from xxx;

--
David Williams

[David Williams]

In article <349837...@bloomberg.com>, "Art S. Kagel"
<ka...@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

[SaTriGuy]

>Could anyone please explain me the meaning of the following state of
>the informix session. This the out put of

>

>tid name rstcb flags curstk status
>16573 sqlexec c042a18 Y--P--- 1872 c042a18 cond wait(netnorm)
>
>

The netnorm wait is simply saying that the session is waiting for input from
the client and that the client is using tcp. If this had been using a shared
memory interface, it would have been condtion(smwait).
Madison Pruet