so what if the user who is using all the temp gets their query stopped, you are doing the same thing by wanting to limit their resources.
You could change your on call if the 1652 was for this temp tablespace
Dont let the tempfiles expand was his point
By creating a separate Temp, how will that stop the ORA-1652, for a run-away query? The difference is that with ORA-1652, our on-call gets called, and if we had a quota, then the User would get a message (quota exceeded). The intention is to avoid the 1st one.
What did you mean by limit the sizes of Tempfiles?