Re: UTL_FILE.FOPEN and Unix Permissions

Holger.Kreft_at_sutter.de (Holger Kreft) wrote in <3a5c2761$1_at_news.ic-marl.de>:

>Hi Christopher,
>This is the usual behaviour of the system: The UTL_FILE functions - most
>interesting: the file access on Unix - are executed by the database
>processes owned by the Unix(!) user which started the database (usually
>named "oracle"). The name of the Oracle(!) user calling the UTL_FILE
>functions does not matter. As I know all Oracle users writing and
>reading files via UTL_FILE have the same access rights. If one can read
>or write it - all can read or write it.

The problem is that the name of the user logged into the OS AND Oracle DOES matter. That is the file is created as oracle/oinstall - but if user 'bob' can't access the directory he cannot write to the file. Even thow oracle has write access to the directory and file.

>> The problem is that I cannot get other users to write to this log
>> file...

 I
>> don't want to put them all in the admin group - I just want to log
>> their calls to several stored procedures.
>
>So, this should not be a problem. (Did you try it?) The problems may
>begin as you want several Unix users to access the file. Then you have
>to check the "umask" of the Unix user "oracle".

Thats all fine - oracle as a user has no problem, but the users logging into oracle seem to also need write permissions to the directory/file, thats what I want to remove.

>May be I am wrong, but I think your failure is to mix the meaning of
>users on Oracle and users on Unix. They are independend from each other
>- even if you give them the same names.

users on Oracle == users on Unix as they all use 'external' Authentication, which mean unix user BOB logs in as Oracle user BOB.

>
>regards
>
>Holger Kreft
>
>
>
Received on Thu Jan 11 2001 - 17:22:55 CST