Re: How sql loader handle the error throw back from DB?

that should read "... coded a nice exception handler into the TRIGGER..." Bricklen Anderson wrote:
>
> Hmmm... Not sure why sqlloader would cause a Dr. Watson error on that,
> assuming that a bad row is a bad row and would be logged in the error
> file. Have you coded in a nice exception handler into the view yet? I
> would think that between the two (sqlldr and exception trap) you could
> handle pretty much anything thrown your way. Obviously I'm not seeing
> something here, probably something obvious. ;-)
>
> Bricklen
>
> C Chang wrote:
> >
> > Bricklen Anderson wrote:
> > >
> > > What do you mean by "crash"? What crashed? How? Is sqlldr loading the
> > > data fine into you view (insert errors should be caught by your sqlldr
> > > error log file), then there are problems when the trigger pops the data
> > > into the table? (btw, are you using an "instead of" trigger?). If that's
> > > the case, have you coded an exception handler into the trigger itself to
> > > catch and/or redirect errors?
> > > Or is there something else involved with your loading process?
> > >
> > > C Chang wrote:
> > > >
> > > > I have an batch file using the sqlldr to insert raw data into a view,
> > > > which triggers an insert into a real table. Apparently I did not have
> > > > some exception in that procedure to handle the insert error. So when it
> > > > crash, it caused the sqlldr failed and since there is no handle, so it
> > > > generated a Dr. Waston error on screen. I want to know is there an
> > > > error handling by sql loader? ( I know I can handle the exception inside
> > > > the sql procedure) but what if I still miss somthing. Thanks
> > > >
> > > > C Chang
> > >
> > > --
> > > -----------------------------
> > > * http://pipers.hypermart.net *
> > > -----------------------------
> > Bricklen:
> > Thanks for your answer. As I said, there is no exception in the
> > Trigger where an insert of extra long string casued the error. Since
> > there is no handler, so the trigger failed and subsequently SQLLDR did
> > not finish and there was nothing in sqlldr error file. HOwever, my
> > question is whether there is any process in sqlldr to handle this, even
> > there is an exception in PL/SQL. Just in case. So I will not get a Dr.
> > Waston error for DOS mode.
> >
> > C Chang
>
> --
>
>
> -----------------------------
> * http://pipers.hypermart.net *
> -----------------------------

-- 
 
 
 -----------------------------
* http://pipers.hypermart.net *
 -----------------------------