Rationale Behind The Group Used On Directories Created By The Exadata BCU Script (Doc ID 1479863.1)

Last updated on AUGUST 03, 2012

Applies to:

Exadata Database Machine X2-8 - Version Not Applicable and later
Exadata Database Machine V2 - Version Not Applicable and later
Exadata Database Machine X2-2 Full Rack - Version Not Applicable and later
Exadata Database Machine X2-2 Hardware - Version Not Applicable and later
Exadata Database Machine X2-2 Qtr Rack - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

The Exadata BCU script creates NFS shares on a ZFSA and then mounts them to the DBM nodes.  The user guide uses the group oinstall, and the script uses this too.
It would seem that a more natural group would be the OSDBA group i.e. if permissions are opened up should it be the members of the group who can install any Oracle software on a host who should be able to access backups - or should it be DBAs for the database who should be able to access backups?

Is it possible to explain the reasoning around using the Oracle software owner group (oinstall) for the group ownership of the directory used to host dastabase backups for a specific database.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms