And anybody who would be concerned that if they set their temp and undo to set sizes, folks would be less than understanding if they were to hit the threshold, (even when it's poor coding as the problem...) have you considered using dbms_resumable? We have it set in all our databases and a script that monitors for it. If anything does go awry, the transaction simply goes into a time out until we can take a quick look and address the problem, (like kill the query that is using all the temp) allowing the rest of the transactions to "resume" once temp or undo issues are resolved. Kellyn Pedersen Multi-Platform DBA I-Behavior Inc. http://www.linkedin.com/in/kellynpedersen www.dbakevlar.blogspot.com "Go away before I replace you with a very small and efficient shell script..." --- On Mon, 1/18/10, Michael McMullen <ganstadba@xxxxxxxxxxx> wrote: From: Michael McMullen <ganstadba@xxxxxxxxxxx> Subject: RE: How to clear UNDOTBS- Slightly OT To: "'Oracle-L Freelists'" <oracle-l@xxxxxxxxxxxxx> Date: Monday, January 18, 2010, 10:56 AM I never set my undo or temp to autoextend. It’s the easiest database “tell” that somebody has written something screwy if the tablespaces blow up From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kellyn Pedersen Sent: Monday, January 18, 2010 12:26 PM To: ecandrietta@xxxxxxxxx; wellmetus@xxxxxxxxx Cc: ORACLE-L Subject: Re: How to clear UNDOTBS- Slightly OT How many DBA's inspect what is utilizing temp and undo? How many DBA's see a large temp and/or UNDO tablespace as a red flag in a database? Kellyn Pedersen Multi-Platform DBA I-Behavior Inc. http://www.linkedin.com/in/kellynpedersen www.dbakevlar.blogspot.com "Go away before I replace you with a very small and efficient shell script..." --- On Mon, 1/18/10, Roger Xu <wellmetus@xxxxxxxxx> wrote: Hi,