multiple userthreads per session

We have noticed that since we have dropped and recreated some indexes over the weekend, that we now see multiple userthtreads per session when we do an onstat -u. Previously, we would see only one userthread per session. We are on IDS 7.31.Here is a sample of the output: c000000066f76c90 Y-B---- 4664 jjohnson t0d c000000067529a68 0 28 0 0 c000000066f77378 Y-B---- 4664 jjohnson t0d c0000000647ab978 0 28 0 0 c000000066f77a60 Y-B---- 4664 jjohnson t0d c00000006689c640 0 28 0 0 c000000066f78148 Y-B---- 2885 agoodwin ttc c0000000677b71f8 0 16 0 0 c000000066f78830 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f78f18 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f79600 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f79ce8 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f7a3d0 Y-B---- 4664 jjohnson t0d c00000006741de28 0 28 0 0 c000000066f7aab8 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f7b1a0 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 What causes this?

Hi, while this shows, that there are several user threads, it unfortunately doesn't show, what these threads are doing in detail. You probably want to do the following onstat commands also: "onstat -g ath", "onstat -g ses <session id>", "onstat -g sql <session id>" and possibly filter the output so as to get just that relevant for the one session ... That will give much better insight into what these are doing. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions "ANTHONY JUDISH" <ajudish@lextron-inc.com> Sent by: forum.subscriber@iiug.org 11.05.2004 16:14 To ids@iiug.org cc Subject multiple userthreads per session [2943] We have noticed that since we have dropped and recreated some indexes over the weekend, that we now see multiple userthtreads per session when we do an onstat -u. Previously, we would see only one userthread per session. We are on IDS 7.31. Here is a sample of the output: c000000066f76c90 Y-B---- 4664 jjohnson t0d c000000067529a68 0 28 0 0 c000000066f77378 Y-B---- 4664 jjohnson t0d c0000000647ab978 0 28 0 0 c000000066f77a60 Y-B---- 4664 jjohnson t0d c00000006689c640 0 28 0 0 c000000066f78148 Y-B---- 2885 agoodwin ttc c0000000677b71f8 0 16 0 0 c000000066f78830 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f78f18 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f79600 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f79ce8 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f7a3d0 Y-B---- 4664 jjohnson t0d c00000006741de28 0 28 0 0 c000000066f7aab8 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 0 c000000066f7b1a0 Y-B---- 4664 jjohnson t0d c0000000677c9bd0 0 28 0 What causes this?

Hi, maybe your environment variable PDQPRIORITY was set to a value greater than zero while you did "oninit" ?