monitoring sequential scans in 9.40FC4W4
I
used to use the following sql to tell me what tables were being sequentially
scanned on my database. This was on 9.40FC4
database sysmaster;
select tabname, sum(seqscans) tot_scans
from sysptprof
where seqscans > 0
and dbsname not like 'sys%'
group by 1
order by 2 desc
Since we upgraded to a patched version of IDS 9.40FC4W4 I seem to get strange
results. For example my onstat command will show a small number like 28850
under seqscans :
bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans
7665 0 486112554 0 0 94 336454 28850
but If I run the above sql I get output with crazy numbers
tabname sysfragments
tot_scans 1384513536
tabname systables
tot_scans 1285619712
tabname user_form_log
tot_scans 22216704
tabname request
tot_scans 6160384
tabname parts
tot_scans 5636096
Anybody know why?
Looks
like they may all be 65536 times too big. All the lower order bits in
those numbers seem to be zeroes...
Andy Lennard
>From: "DAVID FORTUNE" <david.fortune@ingenicofortronic.com>
>To: ids@iiug.org
>Subject: monitoring sequential scans in 9.40FC4W4 [3440] Date: Fri, 17 Sep
>2004 04:53:38 -0400 (EDT)
>
>I used to use the following sql to tell me what tables were being
>sequentially scanned on my database. This was on 9.40FC4
>
>database sysmaster;
>select tabname, sum(seqscans) tot_scans
>from sysptprof
>where seqscans > 0
>and dbsname not like 'sys%'
>group by 1
>order by 2 desc>
>Since we upgraded to a patched version of IDS 9.40FC4W4 I seem to get
>strange results. For example my onstat command will show a small number
>like 28850 under seqscans :
>
>bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans
>7665 0 486112554 0 0 94 336454 28850
>
>but If I run the above sql I get output with crazy numbers
>
>tabname sysfragments
>tot_scans 1384513536
>
>tabname systables
>tot_scans 1285619712
>
>tabname user_form_log
>tot_scans 22216704
>
>tabname request
>tot_scans 6160384
>
>tabname parts
>tot_scans 5636096
>
>Anybody know why?
>
_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today!
http://www.msn.co.uk/messenger
In addition to this question, this parameter with as another one can be related
for knowing if all are working well? Like Art Kagel's ratios.sh script ..
Thanks
Paola
este parametro con cual otro se puede relacionar para saber si el motor esta
funciondo bien?
Mensaje citado por DAVID FORTUNE <david.fortune@ingenicofortronic.com>:
> I used to use the following sql to tell me what tables were being
> sequentially scanned on my database. This was on 9.40FC4
>
> database sysmaster;
> select tabname, sum(seqscans) tot_scans
> from sysptprof
> where seqscans > 0
> and dbsname not like 'sys%'
> group by 1
> order by 2 desc>
> Since we upgraded to a patched version of IDS 9.40FC4W4 I seem to get strange
> results. For example my onstat command will show a small number like 28850
> under seqscans :
>
> bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans
> 7665 0 486112554 0 0 94 336454 28850
>
> but If I run the above sql I get output with crazy numbers
>
> tabname sysfragments
> tot_scans 1384513536
>
> tabname systables
> tot_scans 1285619712
>
> tabname user_form_log
> tot_scans 22216704
>
> tabname request
> tot_scans 6160384
>
> tabname parts
> tot_scans 5636096
>
> Anybody know why?
>
>
>