Re: SQL PLUS Double-At (_at_@) fails
Date: Wed, 08 Jan 2003 13:31:00 GMT
Message-ID: <oKVS9.95454$R45.4492212_at_news2.tin.it>
If you don't want to hardcode paths, you can presumably pass them as arguments or store them in environment variables. Normally I try to use relative paths, so that once the root path is known, everything else can be easily derived and you can also relocate stuff very easily.
Coming to your specific question, this is an excerpt of Sql Plus User's Guide and Reference (8.1.7):
When you enter _at__at_file_name.ext from within a command file, SQL*Plus runs file_name.ext from the same directory as the command file. When you enter _at__at_file_name.ext interactively, SQL*Plus runs file_name.ext from the current working directory. If SQL*Plus does not find such a file, SQL*Plus searches a system-dependent path to find the file. Some operating systems may not support the path search. See the Oracle installation and user's manual(s) provided for your operating system for specific information related to your operating system environment
Bye,
Flavio
"Phil Jollans" <phil.Jollans_at_messring.de> wrote in message
news:dee3c315.0301080037.6a42032b_at_posting.google.com...
> We have very mixed experience using the double-at (_at_@) operator in our
> SQL scripts, to include other scripts in the same directory.
>
> On most, but not all, machines it fails. I think that the error is
> SP2-0310 (file not found).
>
> I am quite certain that the files are all present and in the same
> directory as the main script.
>
> The client machines are usually running Windows 2000 (but may be NT or
> XP).
>
> Since the alternative is to hard code the path of the scripts in the
> top level script, we would very much like to use the useful double-at
> operator.
>
> Has anybody any idea why it would fail?
>
> Phil
Received on Wed Jan 08 2003 - 14:31:00 CET