Re: Execute 650 mb sql script

IANAL_VISTA wrote:
> Frank van Bortel <fvanbortel_at_netscape.net> wrote in
> news:d3ed8e$q7a$1_at_news6.zwoll1.ov.home.nl:
>
>>For clarity: commit over a cursor (a.k.a. committing within a
>>loop) will cause ORA-1555's.
>
>
> 1) The above statement is not true in all cases.
>
> s/will/can/
>

I was expecting that :)
And no - I will kepp on stating that it will. If it doesn't, consider yourself lucky.

>
> 2) In my post I purposefully said "may" cause ORA-01555.
>

Paul said:

>be the problem. I would *_assume_* that most of the script is of the
>> nature of INSERT INTO TableBlah VALUES (blah1, blah2..... blahn).
>>
>>
>> Try putting "COMMIT;" at the end of every block of 5000 or so records?
>> Or even at the end of each completed table entry?
>>

Your reply:

> Intervening COMMITs may increase the chances for ORA-01555 error;
> and consumes more resources.

Please explain when you perceive an ORA-1555 when having thousands of lines like
INSERT INTO TableBlah VALUES (blah1, blah2..... blahn)

It's not going to happen.

-- 
Regards,
Frank van Bortel