Re: so ok one of the users blew out temp during production flows last night
Date: Wed, 11 Mar 2009 10:13:00 -0600
Gotta love that old Panic and Point dance...Why not just increase the temp space to 42 terabytes and kick all users out of the database? <knee jerk sarcasm>
I presume that the session who consumed the temp space was unrelated to the process. What was the session doing? If there was a statement consuming too much temp space, then tuning/rewriting is in order. It would be an opportunity to explain to someone about resource issues within a database. If the statement has been running fine and there are not any indications of changes, you might be encountering an issue where temp space is not being freed properly and/or overconsumed. I've dealt with this issue in several databases and never received a satisfactory answer from Oracle support.
-- Daniel Fink OptimalDBA.com - Oracle Performance, Diagnosis, Data Recovery and Training OptimalDBA http://www.optimaldba.com Oracle Blog http://optimaldba.blogspot.com Lost Data? http://www.ora600.be/ TESTAJ3_at_nationwide.com wrote:Received on Wed Mar 11 2009 - 11:13:00 CDT
> 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
> 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.