Re: UTL_FILE

utl_file_dir=* does work, its the only wildcard which does.

Going back to the comment by somebody saying never use the wildcard since it gives developers access to everything. They will only have access to all areas which the OS will allow the 'oracle' user to have.

e.g If the oracle user cannot see /usr/tmp in UNIX, it cannot be seen using UTL_FILE even if the utl_file_dir is set to *. The OS permissions are never overridden. Try it.

Mark

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:<ttcvia9v2gpda1_at_corp.supernews.com>...
> "rob" <rob_at_dsdelft.nl> wrote in message news:9r5q76$9vu$1_at_news.tudelft.nl...
> >
> > > but the UTL_FILE_DIR parameters ( init.ora ) have to be initialize to
> the
> directory
> > > you want allow Oracle to create the file or you can choose a larger
> option
> with
> > > positioning UTL_FILE_DIR = * if you don't where you to create the files
> ( it's not
> > > a good solution i think )
> >
> > No it's not. Never put UTL_FILE_DIR=* in init.ora. It allows all oracle
> > users that have access to utl_file package to edit all files on the server
> > as if they are user oracle. You can even edit oracle datafiles, init.ora,
> > etc.
> >
> > Rob.
> >
> >
> Also AFAIK utl_file_dir=* (or any wildcard for that matter) doesn't work,
> you have to include individual directories separated by ;
>
> Regards,
>
> Sybrand Bakker
> Senior Oracle DBA
Received on Tue Oct 30 2001 - 12:13:41 CET