Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Michal Hajek (IDS 7.31.UC6, HP-UX 10.20) wanted to find which users and statements cause large, slow reads among 150 active users. Jean-Guy Charron and William Rice suggested onstat -g sql. Michal needed to identify the heaviest reader first, so Art Kagel advised onstat -u and sorting on the nreads column. Answered.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Michal Hajek — — source: Informix-list mailing list archive (1991-1998)
Hi,
IDS 7.31UC6, HP-UX 10.20.
I'd like to know, for who and what statement IDS is reading
amount of data. I'd like to find why I see quite huge and long
time taking reads ...
Is this possible ?
Thank you,
Michal Hajek
--
--------------------------------------------------------------
Michal Hajek mailto:hajek@nspuh.cz
--------------------------------------------------------------
↪ replying to Michal Hajek
Jean-Guy Charron — — source: Informix-list mailing list archive (1991-1998)
onstat -g sql
Jean-Guy
"Michal Hajek" <hajek@nspuh.cz> a 'crit dans le message news:
39B63A89.2C85B2F5@nspuh.cz...
> Hi,
>
> IDS 7.31UC6, HP-UX 10.20.
>
> I'd like to know, for who and what statement IDS is reading
> amount of data. I'd like to find why I see quite huge and long
> time taking reads ...
>
> Is this possible ?
>
> Thank you,
> Michal Hajek
>
>
> --
> --------------------------------------------------------------
> Michal Hajek mailto:hajek@nspuh.cz
> --------------------------------------------------------------
↪ replying to Michal Hajek
William Rice — — source: Informix-list mailing list archive (1991-1998)
Michal Hajek wrote:
> Hi,
>
> IDS 7.31UC6, HP-UX 10.20.
>
> I'd like to know, for who and what statement IDS is reading
> amount of data. I'd like to find why I see quite huge and long
> time taking reads ...
>
> Is this possible ?
>
> Thank you,
> Michal Hajek
>
>
> --
> --------------------------------------------------------------
> Michal Hajek mailto:hajek@nspuh.cz
> --------------------------------------------------------------
Would onstat -g sql <sid>
be what you were looking for?
Will
↪ replying to William Rice
Michal Hajek — — source: Informix-list mailing list archive (1991-1998)
William Rice wrote:
> Michal Hajek wrote:
> > I'd like to know, for who and what statement IDS is reading
> > amount of data. I'd like to find why I see quite huge and long
> > time taking reads ...
>
> Would onstat -g sql <sid>
> be what you were looking for?
>
Hi !
Yes, but only as a second step.....
I have more the 150 users active and as first step I need
to know for who is IDS reading the biggest amount of data...
Then I can use -g sql.
Thanks,
Michal
--
--------------------------------------------------------------
Michal Hajek mailto:hajek@nspuh.cz
--------------------------------------------------------------
↪ replying to Michal Hajek
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
onstat -u and look at the nreads column or even sort on it:onstat -u | sort +64d -74
Art S. Kagel
Michal Hajek wrote:
>
> William Rice wrote:
> > Michal Hajek wrote:
> > > I'd like to know, for who and what statement IDS is reading
> > > amount of data. I'd like to find why I see quite huge and long
> > > time taking reads ...
> >
> > Would onstat -g sql <sid>
> > be what you were looking for?
> >
>
> Hi !
> Yes, but only as a second step.....
> I have more the 150 users active and as first step I need
> to know for who is IDS reading the biggest amount of data...
> Then I can use -g sql.
>
> Thanks,
> Michal
>
> --
> --------------------------------------------------------------
> Michal Hajek mailto:hajek@nspuh.cz
> --------------------------------------------------------------
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.