Re: Oracle 7.3.2.3 import performance

Er, don't use an export file in the first place! :-)

I'd suggest you first create a 'flat file' of your data from the database. Use SQL*Plus with the 'spool' command (see the SQL*Plus manual for setting for creating flat file output) or use A.N.Other tool (Pro*C, Powerbuilder, something connected through ODBC, etc.)

Obviously you are going to have to think about indexes and constraints (i.e. PKs, which are implemented via indexes anyway). For a big load, maybe hold of until you've loaded the data (no problem with integrity as you knew the data was OK as it's in the database in the first place) and add the indexes and constraints once the data is loaded. You can dig the indexes out from the export file (but not sure about the constraints... try 'grep'ing them out). Still, you should have copies of your database application schema scripts anyway; if not, just reverse-engineer them.

Just my thoughts.

Steve Phelan.

H. Fellinghauer wrote in message <3503a1ff.3118343_at_news>...
>Hi Jerry,
>
>can you do a SQL*Loader direct path load with an export file?
>How do you get your SQL*Loader data source file?
>
>tia
> Harry
>---
>"There is more than one way to do it!"
>
>(Remove -NOSPAM- from my email address)
>
>On Sat, 07 Mar 1998 23:16:49 -0500, Jerry Gitomer <jgitomer_at_p3.net>
>wrote:
>
>>Alan,
>>
>>Try doing selects and then doing direct path SQL Loads. In my case it
>>was much faster than running exports and imports.
>>
>>Regards
>>
>>Jerry
>>--
>>Jerry Gitomer Since I know how to spell DBA I became one.
>>jgitomer_at_p3.net
>
Received on Wed Mar 11 1998 - 00:00:00 CST