setting table as nologging will "do nothing", nothing whatsoever for an import.

commit=y is the way to make imp run SLOWER.


the importing of lobs and longs is done slow by slow (row by row) and that is the major cause of the slow performance. It must be though because the clobs could literally be HUGE.

if you are going to be doing this over and over, I would suggest you exp slices of the table and import them in parallel, much like I just suggested here:
</code> http://asktom.oracle.com/pls/asktom/f?p=100:11:::::P11_QUESTION_ID:42796274859286 <code>

The other thing to look at is how the lob is defined.

For the import, it would be nice of the lob was "cached" so import didn't have to wait for the direct IO to disk to complete on each row.

But, you might not want it cached after that, that would be upto you. But you can alter it to be cache/nocache so you might consider precreating the table, caching the lob, doing the load and then putting it back to nocache if that is what you want.