Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Too bad performance of nested table insert operation

Re: Too bad performance of nested table insert operation

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Sun, 30 May 2004 23:07:06 -0700
Message-ID: <1085983633.822611@yasure>


Hans Forbrich wrote:

> Min-Koo Seo wrote:
>
>

>>BTW, could you possibly why I have to commit when I really have to?
>>
>>By commit at a regular basis, I can achieve some goals:
>>- I can see the progress of my application by using select comands.

>
>
> You can also use autonomous transactions and/or DBMS_PIPE to provide such
> information outside of the current transaction. This helps isolate the
> transaction from the instrumentation.
>
>
>>- No *large* rollback segments are needed.

>
>
> At the risk of having a ORA-1555. And the 'large rollback segment' ends up
> providing a potentially significant performance benefit.
>
> Is disk really that expensive (for example, compared to your wage in trying
> to come up with a workaround) that the size of the rollback segment is
> significant?
>
> IIRC, typically a commercial grade 80GB SCSI disk is under the $1000 mark.
>
>
>>- If my application fails, I can continue the running of the
>>application from that point.

>
>
> In my experience, this frequently means the original application really was
> not a true transaction but rather a series of transactions that happen to
> run in a tight sequence. For example, a payroll run for 100 employees
> might be a single 100-employee transaction or 100 single-employee
> transactions. There are significant differences in the way each should be
> set up.
>
>
> Have you had a chance to look at either of Thomas Kyte's books?
>
> Effective Oracle by Design (Osborne ORACLE Press Series)
> by Thomas Kyte (Author) ISBN: 0072230657
>
> Expert One-on-One Oracle
> by Thomas Kyte (Author) ISBN: 1590592433
>
> These walk through the implications of your frequent commit proposal in
> great detail, especially addressing performance and resource impacts. Both
> are relevant and each shows different things that a skilled Oracle
> programmer needs to watch.
>
> /Hans

Or in some situations DBMS_APPLICATION_INFO.SET_SESSION_LONGOPS which is my favorite.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)
Received on Mon May 31 2004 - 01:07:06 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US