Oracle 11g Release 2 – Single database binary installation guide
Local System configuration
Installation took place on laptop with CentOS 5 x86_64 (Kernel 2.6.18-128.2.1.el5)
- 4 GB Memory
- 500 GB local disk
Steps required to install Oracle 11g Release 2
- Configure Storage
- Check and fulfill pre-requirements
- Binary installation of database
- Listener configuration
- Creation of database
Check and fullfill requirements
Storage Requirements
- As always – recommendation: SAME (stripe and mirror everything)
- Valid storage options for single database instance:
- file system (ext3, reiser, xfs, etc al)
- ASM
- ACFS (!! only for non-database files (i.e. Binary files, trace files and so on!!)
- NFS
- ISCSI
- RAW Disks (read documentation; deprecated option!)
SWAP
- Between 1 and 2 GB RAM –> SWAP 1.5 times the size of RAM
- Between 2 and 16 GB RAM –> SWAP equal to size of RAM
- > 16 GB RAM –> 16 GB SWAP
Automatic Memory Management
- Required /dev/shm with appropriate size (i.e. SGA of 16 GB required /dev/shm to be 16 GB+)
- Huge Pages and autom. Memory Management are INCOMPATIBLE
Supported Operating Systems
- on 32-bit Linux
- Asianux 2 Update 7 (Kernel 2.6.9 or later)
- Asianux 3 (Kernel 2.6.18 or later)
- Oracle Enterprise Linux 4 Update 7 (Kernel 2.6.9 or later)
- Oracle Enterprise Linux 5 Update 2 (Kernel 2.6.18 or later)
- Red Hat Enterprise Linux 4 Update 7 (Kernel 2.6.9 or later)
- Red Hat Enterprise Linux 5 Update 2 (Kernel 2.6.18 or later)
- SUSE Linux Enterprise Server 10 SP2 (Kernel 2.6.16.21 or later)
- SUSE Linux Enterprise Server 11 (2.6.27.19 or later)
!! ACFS and ADVM are ONLY supported on RHEL 5 and OEL 5 !!
- on 64-bit Linux
- Asianux 2 (Kernel 2.6.9 or later)
- Asianux 3 (Kernel 2.6.18 or later)
- Oracle Enterprise Linux 4 Update 7 (Kernel 2.6.9 or later)
- Oracle Enterprise Linux 5 Update 2 (Kernel 2.6.18 or later)
- Red Hat Enterprise Linux 4 Update 3 (Kernel 2.6.9 or later)
- Red Hat Enterprise Linux 5 Update 2 (Kernel 2.6.18 or later)
- SUSE Linux Enterprise Server 10 SP2 (Kernel 2.6.16.21 or later)
- SUSE Linux Enterprise Server 11 (2.6.27.19 or later)
!! ACFS and ADVM are ONLY supported on RHEL 5 and OEL 5 !!
Required Packages
refer to: http://download.oracle.com/docs/cd/E11882_01/install.112/e10840/pre_install.htm
Users and Groups
For separation of rights (i.e. Manage ASM storage, manage database instance)
Available groups:
- OSDBA (typical: “dba”; have SYSDBA privileges on database)
- SYSOPER (typical: “sysoper”; optional, limited set of administrative priv)
- OSDBA for ASM (typical: “asmdba”; full administrative access to ASM instance)
- OSASM for ASM (typical: “asmadmin”; administrative access to ASM instance via SQL*Net)
- OSOPER for ASM (typical: “asmoper”; optional, like SYSOPER group for limited access)
- Minimal group needed: OSDBA group
(in this document the osdba group is named “dba”)
Shell Limits
- In /etc/security/limits.conf
oracle soft nproc 16384
oracle hard nproc 16384
oracle soft nofile 65536
oracle hard nofile 65536
(replace “oracle” with user holding the installation)
- In /etc/pam.d/login add if not existssession required pam_limits.so
Kernel Limits (MINIMUM values) in /etc/sysctl.conf
kernel.sem=250 32000 100 128
kernel.shmall=2097152
kernel.shmmax=536870912
kernel.shmmni=4096
fs.file-max=6815744
fs.aio-max-nr=1048576
net.ipv4.ip_local_port_range=9000 65500
net.core.rmem_default=262144
net.core.rmem_max=4194304
net.core.wmem_default=262144
net.core.wmem_max=1048576
– SuSE only –
vm.hugetlb_shm_group=<gid of osdba group>
The values in /etc/sysctl.conf should be tuned (i.e. according to the number of instance, available memory, number of connections,…)
Kernel Limits – how to calculate them
The values in /etc/sysctl.conf should be tuned (i.e. according to the number of instance, available memory, number of connections,…)
see Part 2 for guides how to calculate the kernel parameters
User Profile file (minimum file) ~/.bash_profile (RHEL, OEL) or ~/.profile (SuSE)
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/11.2/ora11r2p
export ORACLE_SID=ORA11R2P
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
umask 022
ATTENTION: This profile file is for use with a dedicated user for each database binary installation. If you wish to install several binary installation under one single user make sure ORACLE_HOME and TNS_ADMIN is unset
Installing the database binaries
We will install an Oracle 11g Release 2 database (stand-alone without grid infrastructure, without asm), operating system user is named “ora11”, osdba group named “dba” with home directory “/u01/app/oracle/product/11.2.0/ora11”.
Note: According to OFA the directory shall be named “…11.2.0/db_1” For easy management we install a dedicated binary installation under a dedicated user for every database which runs on the system and name them accordingly.
For instance binary database installation for database with SID “ORA11” is held by operating system user named “ora11” with home directory “…11.2.0/ora11”.
The binary installation for the database with SID “ORA11T” is held by the user named “ora11t” with home directory “@…11.2.0/ora11t”.
You can of course use one single user on operating system level for having one or more binary installations. It´s up to you.
Create User
mkdir -p /u01/app/oracle/product/11.2.0/ora11
useradd -g dba -d /u01/app/oracle/product/11.2.0/ora11 ora11
passwd ora11
Create profile file
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/ora11
export ORACLE_SID=ORA11
export NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
export TMP=$ORACLE_HOME/tmp
export TNS_ADMIN=$ORACLE_HOME/network/admin
export TEMP=$TMP
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
Check, if X11 works
export DISPLAY=localhost:0.0
xterm
Check Limits
ulimit -a (as user “ora11”)
Note: “open files” and “max user processes” should show values greater or equial the requisites.
Start installer and perform binary installation
Thats it!
The next step would be creating the database itself. A guide how to do this can be found here.