Re: Execute 650 mb sql script
From: IANAL_VISTA <IANAL_Vista_at_hotmail.com>
Date: Sun, 10 Apr 2005 17:53:34 GMT
Message-ID: <Xns96346ECEC2BEESunnySD_at_68.6.19.6>
>
>
> I'm not sure whether this will work or not, but when I was doing a
> project, I put the scripts for all the different tables into different
> files and then launched a "mother-script" which went through all of
> the different files (with regular COMMITS) - maybe this might work?
>
> How often do you COMMIT during the script? If never, then this *_may_*
> 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?
>
Date: Sun, 10 Apr 2005 17:53:34 GMT
Message-ID: <Xns96346ECEC2BEESunnySD_at_68.6.19.6>
[Quoted] Paul <paulsnewsgroups_at_hotmail.com> wrote in news:g4oi51tni6vnlmf3du3dsu4lktch8g7pes_at_4ax.com:
>
>
> bhawin13_at_indiatimes.com wrote:
>
>
>>I have 650 mb sql script. how to run such big size script sucessfully. >>I have 1 gb ram.
>
>
> I'm not sure whether this will work or not, but when I was doing a
> project, I put the scripts for all the different tables into different
> files and then launched a "mother-script" which went through all of
> the different files (with regular COMMITS) - maybe this might work?
>
> How often do you COMMIT during the script? If never, then this *_may_*
> 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?
>
[Quoted] Intervening COMMITs may increase the chances for ORA-01555 error; and consumes more resources. Received on Sun Apr 10 2005 - 19:53:34 CEST