utl_file can only write to a directory that the executing process can see
...
if it is executing on the server ... there is no way to write to the client.
what are you trying to do?
if you want the server to create the file, then it must be on a filesystem
that both the server and client can mount. which maybe a NTFS systems or a
unix FS served up by samba or NFS to the client, assuming a PC.
The only other way is to use a PL/SQL engine on the client side, like the
one that comes with forms, but it uses TEXT_IO and not UTL_FILE.
Thor HW
Dave Owens wrote in message <35F8012D.DF4910A7_at_criticaldata.com>...
>I don't know what the doc is referring to about client side file io but I
am
>using Forms 4.5 builtin called TEXT_IO to read and write files on the
client
>side. The downside is that you would need Forms (which comes with its own
>PL/SQL compiler), but it works reliably.
>
>- Dave
>
>Ivan Bajon wrote:
>
>> First of all - thanks to all of you for helping me out. I got the script
>> running by adding utl_file_dir = [path] to the database init file. This
>> enables me to output data to a file on the server. The problem is,
however,
>> that what I really wanna do is write the file in a dir on the client
machine
>> from which the procedure is called. The documentation states:
>>
>> "The PL/SQL file I/O feature is available for both client and server side
>> PL/SQL. The client implementation is subject to normal operating system
file
>> permission checking, and so does not need any additional security
>> constraints."
>>
>> What does it take to output to a file on the client using utl_file?
>>
>> - Ivan Bajon
>>
>> Jpmakar wrote in message
>> <1998090902430900.WAA06090_at_ladder01.news.aol.com>...
>> >You can't just open any file via the UTL_FILE package. The directory
path
>> has
>> >to be defined in the init.ora file. You can find whether you currently
>> have it
>> >set by looking in sys.v$parameters (UTL_FILE_DIR). You have to declare
the
>> >path in your PL/SQL EXACTLY the way it is in the parm (i.e. It is case
>> >sensitive). Also make sure the read/write permissions in the o/s allow
the
>> ID
>> >to access the directory tree.
>
>
>
Received on Wed Sep 16 1998 - 18:29:01 CDT
