SQl*Loader poor perfomance

Quote:

---

Originally posted by tamilselvan
==
So??? You obviously know there is a PARALLEL parameter there, but do you know what it's for?
==

You mentioned about breaking of input file and load them in parallel. Why do you break the input file and do the work in parallel?
SO YOU ALSO DO NOT KNOW WHAT IT IS FOR ?

Tamil

---

At the risk of stepping on a hornet's nest, I read it as, if he only loads one file then Parallel won't help, because with parrallel mode each process can load a file, hence you need to load multiple files in order to load in parallel. Am I wrong?

Quote:

---

Initiating Multiple SQL*Loader Sessions
Each SQL*Loader session takes a different datafile as input. In all sessions executing a direct load on the same table, you must set PARALLEL to true. The syntax is:

http://download-west.oracle.com/docs...2/parallel.gif

---

btw, it seems that the more files you can break the load into, the easier it will be to increase parrallelism, and the better Oracle will be able to balance the load among the various processes. Although I'm sure that there is a diminishing return somewhere.

The parallel clause is just an enabler of parallelism in the load, in that it modifies the allocation of new extents (and presumably the locking as well).

Even only one input file is used but the table is partitioned, Oracle uses parallel threads for loading the data in to different partitions, if you use parallel=true option in sqlldr.

Tamil

Thanks for help, but i know these issues;

But i don't understand why the four CPU are not used. sqlldr is multithreading, so why don't it use the four CPUs ?

Another question is that event "SQL*Net more data from client" a sign of lack of CPU ?

thanks in advcance