Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle for Linux
Summery of Pre-installation Steps:
1)-Tasks to Perform as the root User
Log in as the root user and perform the following tasks as necessary to set up your environment for the Oracle8 Server:
Configure LINUX Kernel for Oracle Create Mount Points Create LINUX Groups for Database Administrators Create LINUX Account to Own Oracle Software Create a Local bin Directory Create the oratab File
Configure LINUX Kernel for Oracle
Configure the LINUX kernel Interprocess Communication (IPC) parameters to accommodate the SGA structure of the Oracle8 Server. You will not be able to start up the database if the system does not have adequate shared memory to accommodate the SGA.
1.Use the ipcs command to obtain a list of the system's current shared memory and semaphore segments, and their identification number
and owner.
2.Set the kernel parameters corresponding to:
maximum size of a shared memory segment (SHMMAX) maximum number of shared memory segments in the system (SHMMNI) maximum number of shared memory segments a user process can attach (SHMSEG) maximum amount of shared memory that can be allocated system-wide (SHMMNS) The total allowable shared memory is determined by the formula:
SHMMAX * SHMSEG The parameters in Table 2-2 control the allocation of semaphores and shared memory. The recommended values are optimal for one
instance and are based on the default initsid.ora file. If you plan to install more than one instance, or to modify the initsid.ora file
extensively, set these parameters higher.
Oracle Corporation recommends you set these parameters as high as possible for the operating system; however, setting these
parameters too high for the operating system can prevent the machine from booting up. Refer to the operating system documentation
for parameter limits.
Table 2-2 Shared Memory and Semaphore Parameters
Parameter Recommended Value Description SHMMAX 4294967295 The maximum size(in bytes) of a single shared memory segment.
SHMMIN
1 The minimum size(in bytes) of a single shared memory segment.
SHMMNI
100 The number ofshared memory identifiers.
SHMSEG
10 The maximum number of shared memory segments that can be attached by a process. SEMMNS 200 The number ofsemaphores in the system.
SEMMNI
70 The number of semaphore set identifiers in the system. SEMMNI determines the number of semaphore sets that can be created at any one time. SEMMSL equal to or greater than the value of the PROCESSES initialization parameter The maximum number of semaphores that can be in one semaphore set. Should be equal tothe maximum number of Oracle processes.
Create Mount Points
The Oracle8 Server requires at least four mount points when creating an OFA-compliant installation: one for the software and at least three for database files.
All software and database mount point names used for Oracle should match the pattern /pm where p is a string constant and m is a fixed-length key to distinguish between mount points. Table 2-3 shows a sample naming scheme.
Table 2-3 Sample Mount Point Naming Scheme
Software Mount Point
Database Mount Points/u01
/u02
/u03
/u04
See Also:
Optimal Flexible Architecture is described in detail in Chapter 1 of the Oracle8 Administrator's Reference for LINUX.
Create LINUX Groups for Database Administrators
The Installer assigns Oracle DBA and OPERATOR privileges to LINUX groups during Installation. Oracle documentation refers to these LINUX groups as the OSDBA and OSOPER groups. Members of these groups have DBA or OPERATOR privileges on the Oracle system by virtue of their membership in the corresponding LINUX groups. The group(s) you designate for these roles should be created before you start the Installer.
On LINUX 2.0.33, use the groupadd utility to create a group named dba. You can name the group something other than dba, but the Installer relinks the oracle executable if you do. If you plan to designate a separate group for the OSOPER group, create that group also.
The Installer offers the group you designate as OSDBA as the default choice for the OSOPER group. If you accept the default, there is effectively no OPERATOR role, because its privileges are simply a subset of the DBA privileges already assigned to the group.
Create LINUX Account to Own Oracle Software
The oracle account is the LINUX account that owns the Oracle distribution. You must run the Installer under this account.
On LINUX 2.0.33, use the operating system administration utility useradd to create an oracle account with the following properties:
Login Name
Can be anything, but this document refers to it as the oracle account.
Default GID
Corresponding to the OSDBA group.
Home Directory
Choose a home directory consistent with other user home directories. The home directory of the oracle account does not
have to be the same as the ORACLE_HOME directory.
Login Shell
The default shell can be /bin/sh, /bin/csh, or /bin/ksh, but the examples in this document assume the Bourne shell
(/bin/sh).
Note:
The oracle account should be used only for installing and maintaining Oracle software. Never use it for purposes
unrelated to the Oracle Server. Do not log in as a database user when using the oracle (LINUX) account.
Sites with multiple Oracle servers may install them under the same oracle
account, or separate ones. If multiple installations share an oracle
account, the DBAs for each installation have access to the other
installations. If this presents security problems, install each Oracle
system
under a different oracle account.
Create a Local bin Directory
Having a common environment for Oracle users greatly simplifies system administration. Part of creating a common environment is creating a local bin directory, outside the ORACLE_HOME directory, for shared software.
1.Create a local bin directory, such as /usr/local/bin. 2.Verify that this directory is included in each user's PATH, and that the users have execute permissions on the directory.
The Installer places the oraenv (coraenv for the C shell) and dbhome scripts in $ORACLE_HOME/bin. After installation, the root.sh script copies the files to the /usr/local/bin directory. The Installer cannot place them there directly because you must not run the Installer as the root user.
Copying oraenv (coraenv) and dbhome to the local bin directory ensures they continue to provide a common environment, even if the search path is changed to point to a different ORACLE_HOME directory.
You can also place other software that you want accessible to all users in the local bin directory.
Create the oratab File
Information about Oracle instances is stored in the oratab file. This file
is owned by the oracle account, but resides in a directory that
requires root privileges when creating the file. Run the
cdrom_mount_point/orainst/oratab.sh script to create or set the permissions
of
the oratab file in the /var/opt/oracle directory.
2)-Tasks to Perform as the oracle User
Log in to the oracle account and perform the following tasks as necessary:
Set Permissions for File Creation Set Environment Variables Update the Environment for Current SessionReceived on Sat Nov 21 1998 - 13:52:55 CST