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.
Hi all experts,
We noticed sequential scans was over 1 millions times for one table in
sysmaster:sysptprof table. But we didn't know what users/processes/sessions
hit this huge number. Is there any way to find out?
Thanks.
I have a script which captures all sql calls to the
server. U can run it for some
time and go thru it. U can know the source of the rogue SQL very soon.
Please email me if you are interested.
Ravi.
----- Original Message -----
From: "SIMON LIU" <simon.liu@priszm.com>
To: <ids@iiug.org>
Sent: Friday, July 11, 2003 09:47
Subject: Sequential scans [1547]
> Hi all experts,
>
> We noticed sequential scans was over 1 millions times for one table in
sysmaster:sysptprof table.
But we didn't know what users/processes/sessions hit this huge number. Is
there any way to find out?
>
> Thanks.
>
>
You can
use onstat -g ppf (columns partnum, seqsc) or
sysmaster:sysptprof or syssesprof.
SIMON LIU wrote:
> Hi all experts,
>
> We noticed sequential scans was over 1 millions times for one table in
sysmaster:sysptprof table. But we didn't know what users/processes/sessions
hit this huge number. Is there any way to find out?
>
> Thanks.
>
>
--
=== Michael Mueller ==================
Tel. + 49 8171 63600
Fax. + 49 8171 63615
Web: http://www.mm.kay-mueller.dehttp://www.planets.kay-mueller.de
======================================
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.