Stephen, It's obviously a problem linked to rights on /dir_a. Just a stupid thought, when you connect through SQL*Net, and if you aren't using shared servers, the shadow process is forked by tnslsnr that then excutes oracle (the program). Could you check in $ORACLE_HOME/bin if you really see something like this: $ ls -l oracle tnslsnr -rwsr-s--x 1 oracle dba 152692986 2009-01-18 18:44 oracle -rwxr-x--x 1 oracle dba 833609 2009-01-18 18:45 tnslsnr If you don't see all the 's' for oracle, and if for an unknown reason tnslsnr belongs to the wrong user/group, I could make sense of what you describe. HTH Stéphane Faroult Stephen Andert wrote: > Sort of strange scenario. > > Oracle 10.2.0.2 64 bit > SunOS 5.10 > > Added a new directory to utl_file. Let's call it /dir_a > > When a user (user1) connects locally (beq, not SQL*Net) to the db and > writes a file to /dir_a it works fine. > > When the same user (user1) connects to the db using listener > (@dbtest), they are not able to write to /dir_a, UNLESS the file is > already there. The error is: > > ORA-29283: invalid file operation > ORA-06512: at "SYS.UTL_FILE", line 475 > ORA-29283: invalid file operation > ORA-06512: at line 12 > > Same user can create a file in the directory outside the db as can the > oracle user. > > Any ideas? > > Thanks In Advance > > > > *Stephen Andert* > Blog <http://cactustri.blogspot.com/> | Flowing Desert Photography > <http://flowingdesert.com/> > Twitter <http://www.twitter.com/CactusTri> > > -- //www.freelists.org/webpage/oracle-l