Re: so ok one of the users blew out temp during production flows last night
From: Rich Jesse <rjoralist_at_society.servebeer.com>
Date: Wed, 11 Mar 2009 11:14:13 -0500 (CDT)
Message-ID: <197a6613a2b271bbf12a4cba4c80db83.squirrel_at_society.servebeer.com>
> 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
Date: Wed, 11 Mar 2009 11:14:13 -0500 (CDT)
Message-ID: <197a6613a2b271bbf12a4cba4c80db83.squirrel_at_society.servebeer.com>
> 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-lReceived on Wed Mar 11 2009 - 11:14:13 CDT