Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Direct vs. Embedded call to SQL script

Re: Direct vs. Embedded call to SQL script

From: Alan D. Mills <alanmNOSPAM_at_uk.europe.mcd.mot.com>
Date: Thu, 6 Aug 1998 15:44:04 +0100
Message-ID: <6qcfev$dnl$1@schbbs.mot.com>


Can you supply example code. namely the calling SQl script (scrip2.sql) and the SQL script being run (scrip1.sql)?

--
Alan D. Mills

Ariel Kirson wrote in message <35C975C0.7EF153EC_at_exlibris.co.il>...
>Hello all,
>
>I have a SQL script named "script1.sql" which expects
>to receive 2 parameters (&1,&2).
>
>I have noticed that when running the script directly from
>the command prompt (AIX Unix Environment), i.e. :
>
> sqlplus usr/pwd @script1 val1 val2
>
>The results differ in comparison with embedding the
>following statement in "script2.sql":
> @script1 val1 val2
>
>(in this case, running sqlplus usr/pwd @script2 produces
>various errors, which I do not know the reasoning for, such
>as ERROR, found DROP when expecting to find BEGIN...)
>
>I would greatly appreciate any insights as to why this
>happens.
>
>Many thanks,
>
>Ariel Kirson
>Ex Libris.
>
Received on Thu Aug 06 1998 - 09:44:04 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US