You can define your own exceptions in the declare section, then RAISE that
exception.
> -Original Message-
>
> I want to trap the case where either no value for i_runcr is
> specified at
> runtime (and thus the assignment should be NULL) or a
> non-numeric character
> is specified (e.g
Title: RE: trapping errors from assignment of SQL*Plus Input Variables
this
was the right direction -
I
changed the assignment line to this:
v_runcr := nvl(to_number('&&i_runcr'), 0);
and it catches the 6502 (numeric or value error) quite
nicely.
Tha
Title: RE: trapping errors from assignment of SQL*Plus Input Variables
Well, seems to me the script won't execute unless A value for v_runcr is specified, or v_runcr is defined in the sqlplus environment prior to execution. Now, numeric or not, sqlplus doesn't care, of course. I
Title: RE: trapping errors from assignment of SQL*Plus Input Variables
yes -
would it matter?
-Original Message-From: Koivu, Lisa
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 10, 2002
1:05 PMTo: '[EMAIL PROTECTED]';
'[EMAIL PROTECTED]'Subject: RE:
Title: RE: trapping errors from assignment of SQL*Plus Input Variables
Bill, is this an anonymous block you are talking about?
Lisa Koivu
Oracle Diaper Administrator
Fairfield Resorts, Inc.
5259 Coconut Creek Parkway
Ft. Lauderdale, FL, USA 33063
-Original Message-
From
