"Christoph Seidel" <christoph.seidel1_at_gmx.de> wrote in message
news:b58481$26eol7$1_at_ID-143718.news.dfncis.de...
> NorwoodThree wrote:
>
> > I'm not sure why you would need it; please clarify...
> >
> > sqlldr in addition to log files, creates discard and bad files.
> > Anything in these types of files will show what was not loaded.
>
> Yes, but it is difficult to find the problem quickly.
>
> if i would have a log like:
>
> trying: insert into t (f1,f2) values (1,2);
> error: bla bla
>
> i would know what is wrong.
>
> But with sqlldr i have to find the row in the infile, the values in the
> infile, have to find out what stmt sqlldr has generated and so on. This is
> time consuming, especially when the infile has many bug and is very large
> (rows and cols).
>
>
You might be better off using old ETL techniques: Load the source data into
a staging table without constraints, then use PL/SQL to validate and move
staging table to real table.
Regards,
Paul
Received on Wed Mar 19 2003 - 15:06:36 CST
