I'm going through the class materials for the Oracle University 8i
Performance and Tuning course I took a year ago. That's why I'm using
utlbstat/utlestat. How long should I run utlbstat/ultestat to get meaningful
stats? This system hardly has any load on it, so I'm taking the results with
a grain of salt anyways.
"Sybrand Bakker" <gooiditweg_at_sybrandb.demon.nl> wrote in message
news:kj72vugtgiehn28kdsmbe5kij0oesaghqf_at_4ax.com...
> On Fri, 06 Dec 2002 20:40:59 GMT, "Brian E Dick" <bdick_at_cox.net>
> wrote:
>
> >For all clients? That would explain it. I guess I need to dig into the
> >utlbstat/utlestat code.
> >
> >"Brian E Dick" <bdick_at_cox.net> wrote in message
> >news:GT7I9.161$we.9094_at_news2.east.cox.net...
> >> The times for the wait events are in hundredths of seconds. I waited
334
> >> seconds between running utlbstat and utlestat. The SQL_Net message from
> >> client total time is 63684. That's 636.84 seconds, right? Am I dense or
> >> what? How can the total wait time be greater than the run time?
> >>
> >> Later,
> >> BEDick
> >>
> >> Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
> >> PL/SQL Release 8.1.7.0.0 - Production
> >> CORE 8.1.7.0.0 Production
> >> TNS for 32-bit Windows: Version 8.1.7.0.0 - Production
> >> NLSRTL Version 3.4.1.0.0 - Production
> >>
> >>
> >>
>
>
> I don't think so. Utlbstat/utlestat is not meant to run at such small
> intervals and the data you are getting is probably useless.
> Also in 8i you'd better use statspack.
>
>
> >
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Fri Dec 06 2002 - 16:28:11 CST
