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

From: <TESTAJ3_at_nationwide.com>
Date: Wed, 11 Mar 2009 12:28:09 -0400
Message-ID: <OFFB02FC33.F637D427-ON85257576.005A653E-85257576.005A784C_at_lnotes-gw.ent.nwie.net>

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_at_society.servebeer.com> To:
oracle-l_at_freelists.org
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_at_freelists.org

> 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





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

Received on Wed Mar 11 2009 - 11:28:09 CDT