what is waiting for
Posted in 2006
A user on IDS 9.40 saw a session showing "cond wait(netnorm)" (with the 'Y' flag in onstat -u) and wanted to know what it was waiting on, especially as it held 31 locks. Respondents explained this is not a real wait: the server has finished all work the client asked for and the sqlexec thread is simply idle, waiting for the next request from the client (e.g. a dbaccess session left open). The poster confirmed there was no actual problem; his original onbar-cancel issue (session stuck in 'cleaning', eventually killed with onmode -z) was to be raised separately.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: General Discussion
I'd like to find out what is a session waiting for. I will appreciate
any cues to follow. Thanks in advance to the forum comunity.
This is what I have:
onstat -u
...
343ebe88 Y--P--- 29111 sigedw DELL 37b87588 031 54 0
...
onstat -g con |grep 37b8758810965 37b87588 netnorm 29178 5156
aditional information:
onstat -g ses 29111
IBM Informix Dynamic Server Version 9.40.FC2 -- On-Line -- Up
12:30:43 -- 1202176 Kbytes
session #RSAM total used
dynamic
id user tty pid hostname threads memory memory
explain
29111 sigedw DELL 352 10.13.65 1 69632 48008
off
tid name rstcb flags curstk status
29178 sqlexec 343ebe88 Y--P--- 5951 cond wait(netnorm)
Memory pools count 1
name class addr totalsize freesize #allocfrag
#freefrag
29111 V 39369040 69632 21624 100 17
name free used name free used
overhead 0 3248 scb 0 144
opentable 0 4712 filetable 0 1264
log 0 2184 temprec 0 3960
keys 0 208 gentcb 0 2064
ostcb 0 2864 sort 0 104
sqscb 0 18928 sql 0 72
rdahead 0 1856 hashfiletab 0 552
osenv 0 1320 sqtcb 0 4152
fragman 0 376
sqscb info
scb sqscb optofc pdqpriority sqlstats
optcompind directives
3859c050 3936a028 0 0 0 2
1
Sess SQL Current Iso Lock SQL ISAM F.E.
Id Stmt type Database Lvl Mode ERR ERR Vers
Explain
29111 - siad RR Not Wait 0 0
As I understand it, when the status on onstat -g ses is "cond wait(netnorm)"
that means the engine has completed everything the session requested and the
engine is now waiting for the session to make another request. The session is
not waiting on anything. This would be the situation if you were in dbaccess
and issued an SQL statement and the statement has completed but you are still
in dbaccess and have not closed your session. The engine is still waiting on
you.
Rob Schmitz
Informix DBA
rob.b.schmitz@sprint.com
schmitzr@us.ibm.com
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Néstor
Góme....
Sent: Friday, January 13, 2006 11:15 AM
To: ids@iiug.org
Subject: what is waiting for [6206]
I'd like to find out what is a session waiting for. I will appreciate
any cues to follow. Thanks in advance to the forum comunity.
This is what I have:
onstat -u
....
343ebe88 Y--P--- 29111 sigedw DELL 37b87588 031 54 0
....
onstat -g con |grep 37b8758810965 37b87588 netnorm 29178 5156
aditional information:
onstat -g ses 29111
IBM Informix Dynamic Server Version 9.40.FC2 -- On-Line -- Up
12:30:43 -- 1202176 Kbytes
session #RSAM total used
dynamic
id user tty pid hostname threads memory memory
explain
29111 sigedw DELL 352 10.13.65 1 69632 48008
off
tid name rstcb flags curstk status
29178 sqlexec 343ebe88 Y--P--- 5951 cond wait(netnorm)
Memory pools count 1
name class addr totalsize freesize #allocfrag
#freefrag
29111 V 39369040 69632 21624 100 17
name free used name free used
overhead 0 3248 scb 0 144
opentable 0 4712 filetable 0 1264
log 0 2184 temprec 0 3960
keys 0 208 gentcb 0 2064
ostcb 0 2864 sort 0 104
sqscb 0 18928 sql 0 72
rdahead 0 1856 hashfiletab 0 552
osenv 0 1320 sqtcb 0 4152
fragman 0 376
sqscb info
scb sqscb optofc pdqpriority sqlstats
optcompind directives
3859c050 3936a028 0 0 0 2
1
Sess SQL Current Iso Lock SQL ISAM F.E.
Id Stmt type Database Lvl Mode ERR ERR Vers
Explain
29111 - siad RR Not Wait 0 0
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Waiting on a netnorm condition usually means that the thread is waiting for the
client task to make a new request. Basically the thread is idle. Why the
concern? What's the 'problem' you're trying to track down?
Art S. Kagel
----- Original Message -----
From: NStor GMe.... <ids@iiug.org>
At: 1/13 12:14
I'd like to find out what is a session waiting for. I will appreciate
any cues to follow. Thanks in advance to the forum comunity.
This is what I have:
onstat -u
...
343ebe88 Y--P--- 29111 sigedw DELL 37b87588 031 54 0
...
onstat -g con |grep 37b8758810965 37b87588 netnorm 29178 5156
aditional information:
onstat -g ses 29111
IBM Informix Dynamic Server Version 9.40.FC2 -- On-Line -- Up
12:30:43 -- 1202176 Kbytes
session #RSAM total used
dynamic
id user tty pid hostname threads memory memory
explain
29111 sigedw DELL 352 10.13.65 1 69632 48008
off
tid name rstcb flags curstk status
29178 sqlexec 343ebe88 Y--P--- 5951 cond wait(netnorm)
Memory pools count 1
name class addr totalsize freesize #allocfrag
#freefrag
29111 V 39369040 69632 21624 100 17
name free used name free used
overhead 0 3248 scb 0 144
opentable 0 4712 filetable 0 1264
log 0 2184 temprec 0 3960
keys 0 208 gentcb 0 2064
ostcb 0 2864 sort 0 104
sqscb 0 18928 sql 0 72
rdahead 0 1856 hashfiletab 0 552
osenv 0 1320 sqtcb 0 4152
fragman 0 376
sqscb info
scb sqscb optofc pdqpriority sqlstats
optcompind directives
3859c050 3936a028 0 0 0 2
1
Sess SQL Current Iso Lock SQL ISAM F.E.
Id Stmt type Database Lvl Mode ERR ERR Vers
Explain
29111 - siad RR Not Wait 0 0
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
thanks Rob and Art for your comments. This is not a 'problem' indeed, is a
rather of 'trying to understand the status of processes on IDS'.
Everything begun when I had a real problem: I ran onbar and cancel it, then
the process stay locked on 'cleaning' steep. After 10 hours I try to find what
was doing the process for so long time and finished killing them with onmode
-z ID. After that, I started to testing commands and reading manuals to find
out tools to know the state of processes.
This thread and session took my attention because the number of locks was 31,
so I was looking why.
Thanks again. I will ask about my real problems on onbar, on another
post.
--Nestor
El vie, 13-01-2006 a las 12:25 -0500, ART KAGEL, .... escribio:
> Waiting on a netnorm condition usually means that the thread is waiting for
> the
> client task to make a new request. Basically the thread is idle. Why the
> concern? What's the 'problem' you're trying to track down?
>
> Art S. Kagel
>
> ----- Original Message -----
> From: NStor GMe.... <ids@iiug.org>
> At: 1/13 12:14
>
> I'd like to find out what is a session waiting for. I will appreciate
> any cues to follow. Thanks in advance to the forum comunity.
> This is what I have:
>
> onstat -u
> ....
> 343ebe88 Y--P--- 29111 sigedw DELL 37b87588 0> 31 54 0
> ....
>
> onstat -g con |grep 37b87588> 10965 37b87588 netnorm 29178 5156
>
> aditional information:
>
> onstat -g ses 29111>
> IBM Informix Dynamic Server Version 9.40.FC2 -- On-Line -- Up
> 12:30:43 -- 1202176 Kbytes>
> session #RSAM total used
> dynamic
> id user tty pid hostname threads memory memory
> explain
> 29111 sigedw DELL 352 10.13.65 1 69632 48008
> off
>
> tid name rstcb flags curstk status
> 29178 sqlexec 343ebe88 Y--P--- 5951 cond wait(netnorm)
>
> Memory pools count 1
> name class addr totalsize freesize #allocfrag
> #freefrag
> 29111 V 39369040 69632 21624 100 17
>
> name free used name free used
> overhead 0 3248 scb 0 144
> opentable 0 4712 filetable 0 1264
> log 0 2184 temprec 0 3960
> keys 0 208 gentcb 0 2064
> ostcb 0 2864 sort 0 104
> sqscb 0 18928 sql 0 72
> rdahead 0 1856 hashfiletab 0 552
> osenv 0 1320 sqtcb 0 4152
> fragman 0 376
>
> sqscb info
> scb sqscb optofc pdqpriority sqlstats
> optcompind directives
> 3859c050 3936a028 0 0 0 2
> 1
>
> Sess SQL Current Iso Lock SQL ISAM F.E.
> Id Stmt type Database Lvl Mode ERR ERR Vers
> Explain
> 29111 - siad RR Not Wait 0 0
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Yes, you are right.
Basically the "Y" flag in the first position of an
onstat -u or ( cond wait netnorm )means that there isnothing to do on the server side ( database server )
and the session is waiting for new messages from the
client side ( in your example dbaccess ).
esteban.-
--- "Schmitz, Ro...." <Rob.B.Schmitz@sprint.com>
escribió:
>
> As I understand it, when the status on onstat -g ses
> is "cond wait(netnorm)"
> that means the engine has completed everything the
> session requested and the
> engine is now waiting for the session to make
> another request. The session is
> not waiting on anything. This would be the situation
> if you were in dbaccess
> and issued an SQL statement and the statement has
> completed but you are still
> in dbaccess and have not closed your session. The
> engine is still waiting on
> you.
>
> Rob Schmitz
> Informix DBA
> rob.b.schmitz@sprint.com
> schmitzr@us.ibm.com
>
> -----Original Message-----
> From: ids-bounces@iiug.org
> [mailto:ids-bounces@iiug.org] On Behalf Of Néstor
> Góme....
> Sent: Friday, January 13, 2006 11:15 AM
> To: ids@iiug.org
> Subject: what is waiting for [6206]
>
> I'd like to find out what is a session waiting for.
> I will appreciate
> any cues to follow. Thanks in advance to the forum
> comunity.
> This is what I have:
>
> onstat -u
> .....
> 343ebe88 Y--P--- 29111 sigedw DELL 37b87588 0> 31 54 0
> .....
>
> onstat -g con |grep 37b87588> 10965 37b87588 netnorm 29178 5156
>
> aditional information:
>
> onstat -g ses 29111>
> IBM Informix Dynamic Server Version 9.40.FC2 --
> On-Line -- Up
> 12:30:43 -- 1202176 Kbytes
>
> session #RSAM total used
> dynamic
> id user tty pid hostname threads memory memory
> explain
> 29111 sigedw DELL 352 10.13.65 1 69632 48008
> off
>
> tid name rstcb flags curstk status
> 29178 sqlexec 343ebe88 Y--P--- 5951 cond
> wait(netnorm)
>
> Memory pools count 1
> name class addr totalsize freesize #allocfrag
> #freefrag
> 29111 V 39369040 69632 21624 100 17
>
> name free used name free used
> overhead 0 3248 scb 0 144
> opentable 0 4712 filetable 0 1264
> log 0 2184 temprec 0 3960
> keys 0 208 gentcb 0 2064
> ostcb 0 2864 sort 0 104
> sqscb 0 18928 sql 0 72
> rdahead 0 1856 hashfiletab 0 552
> osenv 0 1320 sqtcb 0 4152
> fragman 0 376
>
> sqscb info
> scb sqscb optofc pdqpriority sqlstats
> optcompind directives
> 3859c050 3936a028 0 0 0 2
> 1
>
> Sess SQL Current Iso Lock SQL ISAM F.E.
> Id Stmt type Database Lvl Mode ERR ERR Vers
> Explain
> 29111 - siad RR Not Wait 0 0
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
___________________________________________________________
1GB gratis, Antivirus y Antispam
Correo Yahoo!, el mejor correo web del mundo
http://correo.yahoo.com.ar
No sweat. Keep pounding away at understanding, that's how most of us got what
little knowledge we have.
Art
----- Original Message -----
From: NStor GMe.... <ids@iiug.org>
At: 1/13 13:01
thanks Rob and Art for your comments.
This is not a 'problem' indeed, is a rather of 'trying to understand
the status of processes on IDS'.=20
Everything begun when I had a real problem: I ran onbar and cancel it=
,
then the process stay locked on 'cleaning' steep. After 10 hours I tr=
y
to find what was doing the process for so long time and finished kill=
ing
them with onmode -z ID. After that, I started to testing commands and
reading manuals to find out tools to know the state of processes.
This thread and session took my attention because the number of locks
was 31, so I was looking why.
Thanks again. I will ask about my real problems on onbar, on another
post.
--Nestor
El vie, 13-01-2006 a las 12:25 -0500, ART KAGEL, .... escribi=C3=B3:
> Waiting on a netnorm condition usually means that the thread is wai=
ting for=20
> the=20
> client task to make a new request. Basically the thread is idle. Wh=
y the=20
> concern? What's the 'problem' you're trying to track down?=20
>=20
> Art S. Kagel=20
>=20
> ----- Original Message -----=20
> From: NStor GMe.... <ids@iiug.org>=20
> At: 1/13 12:14=20
>=20
> I'd like to find out what is a session waiting for. I will apprecia=
te=20
> any cues to follow. Thanks in advance to the forum comunity.=20
> This is what I have:=20
>=20
> onstat -u=20
> ....=20
> 343ebe88 Y--P--- 29111 sigedw DELL 37b87588 0=20
> 31 54 0=20
> ....=20
>=20
> onstat -g con |grep 37b87588=20> 10965 37b87588 netnorm 29178 5156=20
>=20
> aditional information:=20
>=20
> onstat -g ses 29111=20
>=20
> IBM Informix Dynamic Server Version 9.40.FC2 -- On-Line -- Up=20
> 12:30:43 -- 1202176 Kbytes=20
>=20> session #RSAM total used=20
> dynamic=20
> id user tty pid hostname threads memory memory=20
> explain=20
> 29111 sigedw DELL 352 10.13.65 1 69632 48008=20
> off=20
>=20
> tid name rstcb flags curstk status=20
> 29178 sqlexec 343ebe88 Y--P--- 5951 cond wait(netnorm)=20
>=20
> Memory pools count 1=20
> name class addr totalsize freesize #allocfrag=20
> #freefrag=20
> 29111 V 39369040 69632 21624 100 17=20
>=20
> name free used name free used=20
> overhead 0 3248 scb 0 144=20
> opentable 0 4712 filetable 0 1264=20
> log 0 2184 temprec 0 3960=20
> keys 0 208 gentcb 0 2064=20
> ostcb 0 2864 sort 0 104=20
> sqscb 0 18928 sql 0 72=20
> rdahead 0 1856 hashfiletab 0 552=20
> osenv 0 1320 sqtcb 0 4152=20
> fragman 0 376=20
>=20
> sqscb info=20
> scb sqscb optofc pdqpriority sqlstats=20
> optcompind directives=20
> 3859c050 3936a028 0 0 0 2=20
> 1=20
>=20
> Sess SQL Current Iso Lock SQL ISAM F.E.=20
> Id Stmt type Database Lvl Mode ERR ERR Vers=20
> Explain=20
> 29111 - siad RR Not Wait 0 0=20
>=20
>=20
> *******************************************************************=
************=20
> Forum Note: Use "Reply" to post a response in the discussion forum.=
=20
>=20
>=20
> *******************************************************************=
************=20
> Forum Note: Use "Reply" to post a response in the discussion foru=
m.=20
>=20
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.