If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Originally posted by patel_dil Great. So did you use Import for loading data or SQL Loader?

Are you asking me?
If yes, I used exp/imp and direct-load insert. No SQL*Loader
Our databases typically consist of six large tables 1-30 mil rows and tens smaller tables, up to 50,000 rows. I used exp/imp (ROWS=N) to copy structures first, then exp/imp to copy the data of the smaller tables and direct-load insert for the large tables.

Once I tried to use exp/imp for the large tables and I'll never do it again!

AlesThe whole difference between a little boy and an adult man is the price of toys

IMHO, since you are switching platforms with a large database, your best bet is to use export/import. You don't really know if your target OS will support files larger than 2G.

I would all the object owners in one shot, seperating the data into multiple 2000M files. There are several advantages to this method. First, you data will be loaded in the correct order (Which isn't relevent anyway because the constraints are put on at the end). Second, your data will load quicker than across a database link.

A varient of the following command should suffice:
exp system/manager file=f1.dmp,f2.dmp,f3.dmp...fN.dmp filesize=2000M owner=schema1,schema2,schema3,...schemaN log=foo.bar

(I wouldn't use DIRECT=Y in this particular case because you are switching platforms and you have several large export files. There have been some bugs reported with direct=y)

Remember, when you transfer data from Windoz to Unix, you must ftp in binary mode.