Re: Execute 650 mb sql script
Date: Mon, 11 Apr 2005 19:51:26 +0200
Message-ID: <d3ed8e$q7a$1_at_news6.zwoll1.ov.home.nl>
DA Morgan wrote:
> Frank van Bortel wrote:
>
>> Yes. Break up the 650MB file in small chunks. >> And and insert into table(...) values (...); will succeed, as long >> as that piece of code remains smaller than 32kB >> (or larger - latest version, which is absent again...)
>
>
> How can you give this advice when you have no more idea than the
> rest of us, I presume, as to what is in the script?
>
> Did I miss something in the thread?
Yes [, Paul's suggestion could be valid in *some* circumstances].
[If all you need to do is] break up the 650MB file is chunks.
The above two lines was mainly what I was reacting upon.
Oracle Designer product had this nice widget, called WebServer Generator (WSG) - it happily generated chunks > 32kByte, and I have suggested more than once to edit the file, and break it up in chunks. (or use server manager, as that used a larger buffer... not valid in this situation, 650MB is really too big)
And I have managed to generate an Offline Instantiation file for Advanced Replication of about 800 MB (eight hundred, yes). DVD burners had yet to be invented, then :(
So, I've been there, done some. And the suggestion that frequent commits e.g. every 5000 inserts, will cause ORA-1555 is simply not true *when 5000 inserts equals 5000 lines of code* There is overhead, sure, but "insert into ....; commit;" will not generate a snapshot too old.
[Quoted] For clarity: commit over a cursor (a.k.a. committing within a loop) will cause ORA-1555's.
-- Regards, Frank van BortelReceived on Mon Apr 11 2005 - 19:51:26 CEST