Re: so ok one of the users blew out temp during production flows last night

the own ts thing i brought up as an option but was shot down as a 
secondary thing to try after putting in oracle profiles and limiting 
things like cpu.

joe

_______________________________________
Joe Testa, Oracle Certified Professional 
Senior Consultant
Data Engineering and Administration
Nationwide Investments

(Work) 614-677-1668
(Cell) 614-312-6715

Interested in helping out your marriage?
Ask me about "Weekend to Remember"
Dec 11-13, 2009 here in Columbus.




From:
"Rich Jesse" <rjoralist@xxxxxxxxxxxxxxxxxxxxx>
To:
oracle-l@xxxxxxxxxxxxx
Date:
03/11/2009 12:14 PM
Subject:
Re: so ok one of the users blew out temp during production flows      last 
night
Sent by:
oracle-l-bounce@xxxxxxxxxxxxx



> Some panic has set it in.
>
> One of the ideas thrown out is to boot all users (except batch flowid) 
out
> of the database as say 6P, or not allow login from users starting at 6P,
>
> what would be the best way (or can we) to do the above concepts.
>
> thanks, joe

Have you considered giving your "batch flowid" it's own TEMP TS?  I do 
that
for our ad-hoc userids so when they attempt to sort all rows in our 
largest
table and fills TEMP_AD_HOC, it only potentially affects other ad-hoc
transactions.

Rich


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

Other related posts: