Ken said:
Forward slashes are generally used to execute the stored proc...
Here are some observations regarding the "/" character as it relates to Oracle and pre-defined meanings/effects for the "/" character:[ul][li]"/" does not mean "execute the previous procedure"; it is a directive to SQL*Plus to interpret/complile the code that precedes the "/"
on previous lines. To "execute" a procedure within SQL*Plus, we use the SQL*Plus "EXEC" or "EXECUTE" command.[/li][li] If a slash appears on a line with other code, and the "/" is not contained in a literal string, then the only pre-defined use of the "/" in Oracle is as a operator to
divide the left operand by the right operand. Otherwise, a syntax error occurs.[/li][li]A slash contained in a data expression during execution should have no adverse effect on that execution.[/li][/ul]To illustrate:
Code:
SQL> create or replace procedure keenan (x varchar2) is
begin
dbms_output.put_line(x);
end; /
/
PLS-00103: Encountered the symbol "/" The symbol "/" was ignored.
SQL> create or replace procedure keenan (x varchar2) is
begin
dbms_output.put_line(x);
end;
/
Procedure created.
SQL> exec keenan('Hello')
Hello
SQL> exec keenan('Hello/There')
Hello/There
Notice that the "/", when part of a literal in an expression, should have no adverse effect on execution.
So, I'm not convinced that we have identified Keenan's problem. Keenan, is your code short enough (and non-proprietary enough) that you could post it here for diagnosis?
![[santa] [santa] [santa]](/data/assets/smilies/santa.gif)
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services:
www.dasages.com]
“Beware of those that seek to protect you from harm. The cost will be your freedoms and your liberty.”