Re: SQL*Loader - using direct load path with a table during others performing delete/select

viktor wrote:

> I just need more detailed answer:

<snipped>

Viktor, without getting into all the details.. let me bounce the concept that has and still is working pretty well for me. I prefer to get the data into Oracle (in any format I can) and then process, scrub and clean it there.

A direct load of 30 million calls on an older HP-UX box we have here takes about 90 minutes. So my concerns are not about the loading part. I want it in Oracle as fast and simplistic as possible - and direct loading using SQL*Loader gives me that. Mucking about to save a few minutes of load time is not worth it IMO.

Then I tackle the work table (or staging table if you prefer to call it that). A couple of well placed indexes. Parallel query. Or even using partitioning on that work table.

Then finally zap it into the production table. It just reminded me... :-) In one extreme case we did that via a SQL*Plus spool into a pipe and direct SQL*Load from that pipe back into the same database (in the days before we had proper partitioning in Oracle).

That to me remains the fastest and simplest form of doing these data loading excercises... using Oracle for what it is pretty darn good at. A data processing platform.

--
Billy