Re: temporary space issue
From: Mladen Gogala <mgogala_at_no.address.invalid>
Date: Wed, 9 Feb 2011 00:58:47 +0000 (UTC)
Message-ID: <iisos7$chk$2_at_solani.org>
On Tue, 08 Feb 2011 10:25:58 -0800, ddf wrote:
>
> V$SORT_USAGE reports on sort segment activity where V$TEMPSEG_USAGE
> reports on both sort and hash activity and either one could be consuming
> large amounts of temp space. I suppose it's personal preference; I
> prefer to see both the hash and sort activity in the temporary
> tablespace.
>
>
> David Fitzjarrell
Date: Wed, 9 Feb 2011 00:58:47 +0000 (UTC)
Message-ID: <iisos7$chk$2_at_solani.org>
On Tue, 08 Feb 2011 10:25:58 -0800, ddf wrote:
> On Feb 8, 10:29 am, Mladen Gogala <n..._at_email.here.invalid> wrote:
>> On Tue, 08 Feb 2011 08:00:20 -0800, ddf wrote: >> > He's using 10.2.0.x so V$TEMPSEG_USAGE is a better view to query: >> >> > select u.username, s.sql_fulltext, u.segtype, u.extents, u.blocks >> > from v$tempseg_usage u, v$sql s >> > where s.sql_id = u.sql_id; >> >> This is a better view, because it shows the SQL that allocated the >> space, but I still have to join it with V$SESSION to get the SID and >> with the DBA_TABLESPACES to get the block size. Without block size, I >> can't deduce the usage in bytes. Basically, I don't think that the >> improvement is significant enough to change my script. >> >> --http://mgogala.byethost5.com
>
> V$SORT_USAGE reports on sort segment activity where V$TEMPSEG_USAGE
> reports on both sort and hash activity and either one could be consuming
> large amounts of temp space. I suppose it's personal preference; I
> prefer to see both the hash and sort activity in the temporary
> tablespace.
>
>
> David Fitzjarrell
David, V$TEMPSEG_USAGE is a synonym for V$SORT_USAGE
-- http://mgogala.byethost5.comReceived on Tue Feb 08 2011 - 18:58:47 CST