Re: sqlldr is ignoring the errors option

Back from the weekend break...

Well, that would really be strange. There seems to be nothing wrong with your control file or your command-line. Even specifying the ERRORS option in both would only result in one overriding the other (the dominant of which I can't remember).

If you haven't solved this yet, show us your logfile and let's see. More info on OS/DB/Client versions would also help. You could try opening an iTar but I doubt that it's a bug of some sort. Someone should have reported it by now if that's the case; sqlload is heavily used by a lot of people.

rolympia_at_hotmail.com (Romeo Olympia) wrote in message news:<42fc55dc.0406101930.6e35f818_at_posting.google.com>...
> What exactly are the errors you're getting? If there are any non-data
> dependent errors, then the load is discontinued immediately.
>
> ken_at_kendenny.com (Ken Denny) wrote in message news:<ba944bc3.0406101032.3ec95ff0_at_posting.google.com>...
> > I have a file I need to load into a table. There are many duplicates
> > in the file and I want to ignore all the errors. I put
> > "errors=1000000" in both the command line and the control file. At
> > first I had it only in the command line, but I added it to the control
> > file when I couldn't get it to work there. No matter what I do, sqlldr
> > stops after 50 errors.
> >
> > My command line:
> > sqlldr USERID=$CONNECTSTRING, silent=feedback, errors=1000000, \
> > control=${WIRX_DATA}/extr/load_ld_prsc_trgt.ctl, \
> > data=${WIRX_DATA}/data/all_targets.dat, \
> > log=${LOGDIR}/targets.log, bad=${LOGDIR}/targets.bad
> >
> > My control file:
> > --
> > -- Load the ld_prsc_trgt table
> > --
> > options (errors=1000000)
> > Load Data
> > append into table ld_prsc_trgt
> > Fields (
> > qtr_cd position (1 : 6) ,
> > cid position (23 : 33) ,
> > mkt_id position (34 : 44) ,
> > brnd_id position (45 : 55) ,
> > prsc_of position (83 : 84) ,
> > trgt_typ position (85 : 86)
> > )
> >
> > But still it stops after 50 errors.
> > The database is Oracle 9i and sqlldr is 9.2.0.4.0.
> >
> > Anyone aware of this problem? And do you know how to correct it?
> >
> > Thanks
> > Ken Denny
Received on Mon Jun 14 2004 - 03:42:16 CDT