Re: WHENEVER SQLERROR does'nt always work
This is a discussion on Re: WHENEVER SQLERROR does'nt always work within the Oracle Database forums, part of the Database Server Software category; --> On 26 Jun 2003 05:09:48 -0700, ni4ni@hotmail.com (Guy) wrote: >Hi > >I have a set of sql scripts that ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-22-2008, 05:55 PM
| ||||
| ||||
 Re: WHENEVER SQLERROR does'nt always work On 26 Jun 2003 05:09:48 -0700, ni4ni@hotmail.com (Guy) wrote: >Hi > >I have a set of sql scripts that creates several tables and them >populates them with rows (via insert statements). >Each script begins with WHENEVER SQLERROR... and WHENEVER OSERROR... >So it should halt once an error occures. I thought this will cover all >possible errors. >The problem is that it doesnt work with all kinds of errors. For >example, if I wrote "nsert into" instead of "insert into" then >SQL*PLUS throws this error message: SP2-0734: unknown command >beginning "NSERT INTO..." but execution doesnt stop. > >Does it mean that WHENEVER SQLERROR doesnt catch "SP2" errors ? is >there a way to catch this kind of errors ? I could'nt find a clue in >SQL*PLUS documentation. > > >T.I.A > >Guy Why catch parsing errors? Your scripts are static aren't they? Just correct the incorrect statement obviously Sybrand Bakker, Senior Oracle DBA To reply remove -verwijderdit from my e-mail address      |
 |
« Re: Oracle 8i with Forms 6i and Firewall
|
9iLite - CONS-10004: USER_INVALID in Consolidator auth; Logon denied »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 03:45 PM.
