Re: To commit or not to commit - That is the question?

You could use the dbms_pipe package to send the error-messages to another sql*plus session. Dbms_pipe messages 'ignore' transactions (rollbacks don't affect them).

hth,
gert

-- 
reply address is altered to keep the spam down
remove the nospamplease part to reply...

Ian Quennell <ian.quennell_at_handc.com> wrote in article
<01bcbd3e$23cb9da0$c69d73c1_at_QRPIQ.handc.com>...


> I have a number of SQL*Plus procedures which need to run in sequence.


 These


> procedures validate and load data in tables and place any validation

> failures in an error table.

> However, if, for example the third procedure fails all procedures must be

> rolled back.

> This is fine except that the validation failures are then rolled back as

> well.


> Any ideas on how it is possible to keep these failures