Re: Permissions on dump logs

Since setting oracle's umask (AIX) or something like it on Sun is the only thing that comes do mind and doesn't seem like a good idea, what about just making this "backup process" have oinstall as a secondary group. You can belong to more than one group, no?

On Sun, 05 Aug 2001 20:25:23 -0800, you wrote:

>Brian,
>
>I guess I wasn't clear about what I wanted to do. I would like the
>files under $ORACLE_BASE/admin/$ORACLE_SID/adump, bdump, cdump and udump
>to have permissions of 644 WITHOUT having to manually change them. Yes,
>I could always go in and change the permissions on the files. What I
>would like is for the backup process, not owned by oracle or in the
>group oinstall, to always be able to read the dump files so that they
>can be backed up.
>
>Thanks for the reply,
>Lou Avrami
>
>------------------------------
>
> From: "Brian Haas" <bhaas_at_musiciansfriend.com>
> Date: Fri, 3 Aug 2001 11:05:29 -0700 (PDT)
> Subject: Re: Permissions on dump logs
>
>On Thu, 2 Aug 2001, Louis Avrami wrote:
>
>1. Since the group ownership of the files is oinstall and the
>permissions are
>640, then the dba group would not have read permissions on those files.
>The group chosen on install (dba) is only for os authentcation to
>connect to the
>database as sysdba,sysoper for users belonging to that group
>
>
>2. if you can login as oracle(the files owner) or root, you can do a
>chmod 644
>or a chmod a+r on the files to give world read access to them, or do a
>chown oracle:dba <file name>
>to change the group ownership to dba therefore giving that group read
>access to
>the files
>
>
>HTH,
>
>-Brian
>
>>Hello all,
>>
>>In an Oracle 8.1.7 instance that I have inherited on a Soalris
>>2.7 server, the owner of the logfiles under
>$ORACLE_BASE/admin/$ORACLE_SID/adump,
>>bdump, cdump and udump is the UNIX ID oracle, group oinstall.
>> The permissions on these files are 640; in other words, only
>>the oracle ID and any ID in the oinstall group can read these
>>log files.
>>
>>We have a backup process that runs under another ID, with a group
>>of dba.
>>
>>The backup process cannot see these log files in order to back
>>them up.
>>
>>Two questions, first one:
>>If the group dba had been chosen as the SYSDBA and/or SYSOP as
>>part of the installation process, would the dba group have read
>>permissions on these files?
>>
>>Question two:
>>Can something be set to make these files readable by other users?
>> I don't think "_trace_files_public = true" will do it.
>>
>>
>>Thanks,
>>Lou Avrami
>
>
>
>
>--
>Please see the official ORACLE-L FAQ: http://www.orafaq.com

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Doug C
  INET: dcowles_at_i84.net

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).