RE: Quota on TEMP

That sounds like a good enhancement request.

One dirty workaround would be to just to periodically monitor the temporary segment users and if anybody without proper permission is using more than X megabytes of temp space, then just kill their session.

Also you could enable the resumable space allocation database wide and write an AFTER SUSPEND trigger which scans for worst temp space users on firing and kills those sessions ;) *evil grin*

But I think a better question is - why do you allow users to run such queries in the database?

Either size the tablespace properly or try to limit running such queries by other means. If it's a production database - nobody should be able to run ad-hoc SQL there anyway, especially if it's known to cause problems..

Tanel.  

> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Deepak Sharma
> Sent: Thursday, September 21, 2006 01:07
> To: davidsharples_at_gmail.com
> Cc: hkchital_at_singnet.com.sg; oracle-l_at_freelists.org
> Subject: Re: Quota on TEMP
>
> What you are suggesting is good and valid, and I don't disagree.
>
> But back to my question - is there a way to set quota for
> Temp (using Res Mgr, profile, anything out there, that
> someone may have used)?
>

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