OraFAQ Forum: Server Utilities » SQL*Loader

Home » RDBMS Server » Server Utilities » SQL*Loader - loading problem

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

SQL*Loader - loading problem [message #70910]

Mon, 12 August 2002 15:52

sai
Messages: 27
Registered: October 2001

Junior Member

I'm loading 5 tables - each with about 20 million rows. When I load individually using DIRECT=True and PARALLEL=TRUE, I'm able to load in about 35 minutes. But when I run all the sqlldr scripts at the same time to load the 5 tables simultaneously, the processes are taking forever and seem to go into a frozen state.

Also, I was planning on running an import for 12 other tables (smaller - between 200,000 and 2 million rows) at the same time as the sqlldr. Would there be any problems if I did that?

Could someone please help me with these two issues.

Thank you
Sai

Report message to a moderator

Re: SQL*Loader - loading problem [message #70914 is a reply to message #70910]

Tue, 13 August 2002 04:56

Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille

Senior Member
Account Moderator

Try again using COMMIT=Y

Report message to a moderator

Re: SQL*Loader - loading problem [message #70917 is a reply to message #70914]

Tue, 13 August 2002 16:37

sai
Messages: 27
Registered: October 2001

Junior Member

Hello Mahesh,
is COMMIT=Y a valid flag for sqlldr? If you meant COMMIT=Y for imp, then I'm already doing it. My main main problem is with sqlldr and the 5 tables loading simultaneously.
Thank you,
Sai

Report message to a moderator

Re: SQL*Loader - loading problem [message #70919 is a reply to message #70910]

Wed, 14 August 2002 02:35

Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille

Senior Member
Account Moderator

sorry for that...commit=y is for import
try these.
1.Run the SQL*Loader job as the owner of the table.
2.Temporarily remove the degree of parallelism from the table
before running the job (if DP is set).
3.if sqlnet tracing is enabled ....turn it off.
4.also increase your sort_area_size and make sort_area_retained_size
equal to it.
5.u can also try to use UNRECOVERABLE
(if applicable..becuase..it doesnt create any logs).

Report message to a moderator

Re: SQL*Loader - loading problem [message #70933 is a reply to message #70910]

Thu, 15 August 2002 10:58

Grant
Messages: 578
Registered: January 2002

Senior Member

If the datafiles being used by the tablespace(s) are on the same disk I would suggest running 2 jobs at a time or you will have an I/O bottle neck nightmare.

Report message to a moderator

Previous Topic:	SQL*Loader - how to exit back to calling batch file
Next Topic:	Manual creation of DB

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Apr 29 13:55:35 CDT 2024