RE: DBA_HIST_SQLSTAT

From: Walker, Jed S <Jed_Walker_at_cable.comcast.com>
Date: Tue, 20 Nov 2012 20:52:40 +0000
Message-ID: <BAA6E28B6241F046AED1E62D8697516C6F558DCE_at_COPDCEXMB08.cable.comcast.com>



I've been looking at this now and am wondering about VERSION_COUNT. The definition is "Number of children associated with the cursor". What exactly is meant by children?

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Andy Klock Sent: Tuesday, November 20, 2012 12:25 PM To: oratune_at_yahoo.com
Cc: Christopher.Taylor2_at_parallon.net; oracle-l_at_freelists.org Subject: Re: DBA_HIST_SQLSTAT

On Tue, Nov 20, 2012 at 12:24 PM, David Fitzjarrell <oratune_at_yahoo.com>wrote:
> They don't, actually. The executions_total is the total executions
> since the database was started, the elapsed_time_total is the total since the db
> was started and the deltas are for each snapshot and don't roll up. I
> came into a shop where a script was running to generate execution
> time reports for long-running queries but it didn't take into account
> that the deltas don't roll up. I rewrote it to provide total
> execution times across snapshots for a given sql_id:
>

My experience is hit and miss when making calculations with executions_total and executions_delta. The reason being these numbers aren't cumulative to the start of the instance but rather since the time they've been in the library cache. (same as v$sqlstats). So, sometimes for long running queries (that span across multiple snapshots) it's possible that they will never show an execution in AWR.

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l
Received on Tue Nov 20 2012 - 21:52:40 CET

Original text of this message