 |
|
Creating the
Necessary Groups for an Oracle Install
Oracle Database Tips by Donald Burleson |
There are two Unix/Linux groups necessary for an
Oracle install. The first group is the Oracle Inventory Group ‑ oinstall.
The oinstall
group owns all of the software and the database files. The Oracle9i
Installation Guide (Part No. A96167-01) states, 'the Oracle user and
ORAINVENTORY (oinstall)
group are the only users that should have read privileges for all data
files, redo logs, and control files to maintain discretionary access
to data.?
The second group is the OSDBA Group ‑ dba. This
group is used to identify users with SYSDBA database privilege.
Members of this group can login to the database with SYSDBA privilege
using operating system authentication.
A third group, the OSOPER group ‑ oper, is an
optional group and will not be used in this book. The OSOPER group is
used to allow a user to connect to the database with SYSOPER database
privilege using operating system authentication.
Any name could be used for the ORAINVENTORY and
OSDBA groups. For the sake of simplicity, this book will use the
default names oinstalland dba. All scripts and instructions included in
this book will use these two names. If there is a need to use
non-default names or to assign a name to the OSOPER group, choose a
custom install from the Universal Installer.
Adding a group is very simple. From the command
line, use the groupaddcommand as shown in Figure 4.7. Use the grep
command to verify that the group was added to the /etc/group file. The
grep command searches
through a text file to find a particular string and returns the lines
where the string is found.
Creating the Oracle
Software Owner
A single user must own the Oracle software. The
default name for that user is ?oracle.? Figure 4.8 shows the
useraddcommand used to create the Oracle user with the
oinstallgroup as his primary group and
dba as a secondary group.
Use the passwd command to
change the password of the Oracle account. Linux may complain that the
password does not contain enough different characters, but it should
accept the new password anyway.
Fedora Linux offers a GUI tool that makes
administering operating system users and groups simple. The
redhat-config-users command launches the Redhat User Manager as shown
in Figure 4.9.
Setting up rshOracle uses the remote shell service to run commands on
both nodes during the software install. Although
rsh is not secure, it is the
only option for Oracle 9i. Oracle 10g installs can use either
rsh or
ssh, the secure version of
remote shell. Run the commands shown in Figure 4.10 to set up
rsh. As a safeguard measure,
the kerberosversion of
rsh is renamed to ensure
that the standard version is used in its place. Do not be concerned if
Linux reports ?No such file.? This would simply indicate that kerberos
is not installed.
Once rshhas been started on each node, it must be tested.
The Oracle user is set up to use
rsh. Figure 4.11 demonstrates switching to the Oracle user with
the sucommand, then running the hostname command on the
remote node via each network connection. This test should be run on
each node as shown in Figure 4.11.
Ensure that ?nobody?
Exists
Ensure that the user:group combination ?nobody?
exists as seen in Figure 4.12. This user:group should have been
included with the Linux install. Oracle software will assign various
files to this user and group. If the user and group do not exist,
switch to root and add it with the command, /usr/sbin/useradd nobody.
 |
If you want to learn RAC at home, get the bestselling book "Personal
Oracle Real Application Clusters" by Edward Stoever.
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot of Oracle tuning scripts. |
|
and include the URL for the page.
