Re: sqlldr and discarded records

I may have missed why you have not, but, if you put a primary key on the table you are importing into, any duplicates ( that is, previously loaded and committed by the failed loader job) will be rejected..set your errors parameter high enough and it should be fine...

"Christoph Seidel" <christoph.seidel1_at_gmx.de> wrote:

>FC wrote:
>> "Christoph Seidel" <christoph.seidel1_at_gmx.de> wrote in message
>> news:b4qf62$231hvv$1_at_ID-143718.news.dfncis.de...
>
>> If the loader dies unexpectedly, there should be a mechanism in place
>> such that it detects the anomaly of the situation.
>> If you are loading data into staging tables, the load failure could
>> trigger an action deleting the partially loaded data or taking some
>> other "clever" action.
>> There are several different methods of loading data, if there are any
>> complex business rules and/or sensible data involved, I normally load
>> everything in staging tables, minimising the data filtering at the sql
>> loader level and deferring it to some more manageable level, like
>> stored procedures that can return much more significant error
>> messages than sql loader can.
>
>I just load the data into a simple table, no complex stuff.
>It seems that the ldr does not know that he already has imported something.
>So i have to adjust the input file or the control file (skip), right?
>
Received on Fri Mar 14 2003 - 09:01:32 CST