Re: temporary space issue

From: dba cjb <chris.brown_at_providentinsurance.co.uk>
Date: Wed, 9 Feb 2011 03:07:28 -0800 (PST)
Message-ID: <a060e919-fc12-4dad-9e16-7c55ebc77414_at_c10g2000vbv.googlegroups.com>

On Feb 9, 12:58 am, Mladen Gogala <mgog..._at_no.address.invalid> wrote:
> 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.com- Hide quoted text -
>
> - Show quoted text -

thanks to everyone for their input

My aim in raising the post was to try to achieve the following:-

1. Advise user of problem query and who ran it
2. Investigate monitoring options to catch this happening in the future

I appreciate assumption of temp full = crash was flawed

regards
Chris B Received on Wed Feb 09 2011 - 05:07:28 CST