r, Ian A. [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 10, 2002 4:40 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Statspack Intervals
>
>
> I don't think it will. V$SQLAREA gives information on
> executions, disk reads, logical reads, etc
AIL PROTECTED]>
cc:
Subject:RE: Statspack Intervals
Statspack is a very nice tool, however if one really wants to find
problems lurking in a database even five minute intervals can be too long.
By finding problems I mean locating inefficiencies proactively. As good
as
I don't think it will. V$SQLAREA gives information on executions, disk reads,
logical reads, etc.
It tells nothing about waits. Joining the two tables you mention does not show you
who has been running the queries, just who parsed them originally. Yes, the rest of
statspack does have infor
Dennis, thanks for the tip.
I checked the site, oracle-dba, and found a lot of interesting articles.
I printed them and will go over then when I have time .
Yechiel Adar
Mehish
- Original Message -
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002
do it, if interested.
Jared
"MacGregor, Ian A." <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/10/2002 09:13 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject:RE: Statspack Inter
Thanks Dennis, I'll take that on board.
Lee
-Original Message-
Sent: 10 July 2002 15:33
To: Multiple recipients of list ORACLE-L
Lee - Good advice from Anjo. If you're getting into STATSPACK this heavily,
you may want to take a look at Burleson's High-Performance Tuning with
STATSPACK
tiple recipients of list ORACLE-LSubject: Re:
Statspack Intervals
Lee,
The rule of thumb is:
Monitoring: 15 to 30 minute
interval
Problem solving: 5 to 15 minute
interval.
Really wrong are intervals of an hour or
so(only
Hey Ian,
I'm a little confused (hopefully not just because of this stupid cold I'm
fighting). Offending SQL in your DB is purged out of the shared pool in
less than five minutes? I would think that joining V$SQLTEXT to V$SQLAREA,
even after a particularly nasty query/DML was completed, would po
MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
-Original Message-From: Anjo Kolk
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, July 10, 2002 3:33
AMTo: Multiple recipients of list ORACLE-LSubject: Re:
Statspack Intervals
Lee,
The rule of thumb is:
Mo
We
take level 5 snapshots every 15 minutes and keep data for 7 days to a month
depending on the table. We rebuild indexes weekly with nologging. I wouldn't
bother with backing up this data. It may help to keep the SQL statements in
stats$sql_summary to identify bad SQL in monthly report spik
Lee - Good advice from Anjo. If you're getting into STATSPACK this heavily,
you may want to take a look at Burleson's High-Performance Tuning with
STATSPACK. He has a lot of ideas for using STATSPACK as a comprehensive
proactive monitoring tool. He also has some good info on his web site.
Dennis W
Thanks
for that.
Regards
Lee
-Original Message-From: Anjo Kolk
[mailto:[EMAIL PROTECTED]]Sent: 10 July 2002 11:33To:
Multiple recipients of list ORACLE-LSubject: Re: Statspack
Intervals
Lee,
The rule of thumb is:
Monitoring: 15 to 30 minute interval
Problem
Lee,
The rule of thumb is:
Monitoring: 15 to 30 minute interval
Problem solving: 5 to 15 minute
interval.
Really wrong are intervals of an hour or so(only
usefull for comparision)
Anjo.
- Original Message -
From:
Robertson Lee -
lerobe
To: Multiple recipients o
13 matches
Mail list logo
