Re: SQL-Loader: how to handle more data fields than columns ?

Mike Dwyer wrote:

> You may be able to add a record size parameter to the INFILE statement in
>
> I did not find any examples or error messages referring to input records
> that exceed the specified record size. Also, if your records are
> variable-length, you obviously cannot use this approach.
>

they are variable length, of course :(

>
> If this fails, could you load a dummy table from beyond the end of the
> normal record? Or would that cause the "good" stuff to be rejected? (See
> Case 5 in the SQL*Loader docs.) Then check the dummy table after the load.
> It should be empty, but if it isn't your test case would presumably have
> occurred.
>

that's it. I tell Loader to insert one column into a table with other NOT NULL columns which produces an ORA-1400. if the ORA-1400 is real or forced by that extra Insert is readily apparent from the content of the resulting .bad file.

thank you!

>
> "Juergen Hartelt" <juergen.hartelt_at_t-mobil.de> wrote in message
> news:38F5FB37.3DA64EF0_at_t-mobil.de...
> > I load ASCII files with delimited data fields. one of the test cases
> > was to load a "user corrupted" data file, wherein two lines of data
> > have been joined.
> >
> > SQL-Loader just ignores the extra data on that line and does not signal
> > any error.
> >
> > can I change this behaviour somwhow? I
> > Jürgen
Received on Tue Apr 18 2000 - 12:04:49 CEST