About
Installation of Oracle Database 11g Release 2 (11.2) on Oracle Enterprise Linux 5.
Articles Related
Prerequisites
Preinstallation Requirements
- login as root
Memory
- RAM: At least 1 GB
[root@oel11g ~]# grep MemTotal /proc/meminfo
MemTotal: 1010816 kB
- swap space
The following table describes the relationship between installed RAM and the configured swap space requirement:
| RAM | Swap Space |
|---|---|
| Between 1 GB and 2 GB | 1.5 times the size of RAM |
| Between 2 GB and 16 GB | Equal to the size of RAM |
| More than 16 GB | 16 GB |
To determine the size of the configured swap space, enter the following command:
[root@oel11g ~]# grep SwapTotal /proc/meminfo
SwapTotal: 2031608 kB
- To determine the available RAM and swap space, enter the following command:
[root@oel11g ~]# free
total used free shared buffers cached
Mem: 1010816 452556 558260 0 63788 313508
-/+ buffers/cache: 75260 935556
Swap: 2031608 0 2031608
Add Swap space if needed.
System Architecture
Verify that the processor architecture matches the Oracle software release that you want to install.
[root@oel11g ~]# uname -m
i686
Disk Space
Tmp Directory
At least 1 GB of disk space in the /tmp directory
[root@oel11g ~]# df -h /tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
18G 7.5G 9.1G 46% /
If necessary, enter commands similar to the following to create a temporary directory on the file system that you identified, and set the appropriate permissions on the directory:
$ sudo mkdir /mount_point/tmp
$ sudo chmod a+wr /mount_point/tmp
# exit
Enter commands similar to the following to set the TMP and TMPDIR environment variables for the Bourne, Bash, or Korn shell:
$ TMP=/mount_point/tmp
$ TMPDIR=/mount_point/tmp
$ export TMP TMPDIR
Disk space requirements
The following tables describe the disk space requirements on Linux x86:
| Installation Type | Software (GB) | Data (GB) |
|---|---|---|
| Enterprise Edition | 3.95 | 1.7 |
| Standard Edition | 3.88 | 1.5 |
Operating System (Distribution) and kernel
Check that you have the minimal operating system and kernel of OEL: Linux - How to know the version of the distribution (Operating system)
Minimal Distribution
| On Linux x86 | On Linux x86-64 |
|---|---|
| Oracle Enterprise Linux 4 Update 7 Oracle Enterprise Linux 5 Update 2 | Oracle Enterprise Linux 4 Update 7 Oracle Enterprise Linux 5 Update 2 |
Minimal Kernel
- Oracle Enterprise Linux 4: 2.6.9 or later
- Oracle Enterprise Linux 5: 2.6.18 or later
Package - RPM
Oracle recommends that you install your Linux operating system with the default software packages (RPMs), unless you specifically intend to perform a minimal installation.
The following packages (or later versions) must be installed:
| OEL 4 (x86) | OEL 5 (x86) |
|---|---|
| binutils-2.15.92.0.2 compat-libstdc++-33-3.2.3 elfutils-libelf-0.97\\elfutils-libelf-devel-0.97 gcc-3.4.6 gcc-c++-3.4.6 glibc-2.3.4-2.41 glibc-common-2.3.4 glibc-devel-2.3.4 glibc-headers-2.3.4 libaio-devel-0.3.105 libaio-0.3.105 libgcc-3.4.6 libstdc++-3.4.6 libstdc++-devel-3.4.6 make-3.80 numactl-0.6.4.i386 pdksh-5.2.14 sysstat-5.0.5 unixODBC-2.2.11 unixODBC-devel-2.2.11 | binutils-2.17.50.0.6 compat-libstdc++-33-3.2.3 elfutils-libelf-0.125 elfutils-libelf-devel-0.125 elfutils-libelf-devel-static-0.125 gcc-4.1.2 gcc-c++-4.1.2 glibc-2.5-24 glibc-common-2.5 glibc-devel-2.5 glibc-headers-2.5 kernel-headers-2.6.18 ksh-20060214 libaio-0.3.106 libaio-devel-0.3.106 libgcc-4.1.2 libgomp-4.1.2 libstdc++-4.1.2 libstdc++-devel-4.1.2 make-3.81 numactl-devel-0.9.8.i386 sysstat-7.0.2 unixODBC-2.2.11 unixODBC-devel-2.2.11 |
More … Package Requirements
The numa package link for Linux x86 is /usr/lib and Linux x86-64 is /usr/lib64/
To determine whether the required packages are installed, enter commands similar to the following:
rpm -qa | grep beginning_of_the_package_name
[root@oel11g Server]# rpm -qa | grep elfutils
elfutils-libelf-devel-static-0.137-3.el5
elfutils-libelf-devel-0.137-3.el5
elfutils-libelf-0.137-3.el5
If a package is not installed, then install it from the Linux distribution media or download the required package version from the Linux vendor's Web site.
rpm -Uvh elfutils-libelf-devel*
rpm -Uvh kernel-headers*
rpm -Uvh glibc-headers*
rpm -Uvh glibc-devel*
rpm -Uvh libgomp*
rpm -Uvh gcc-4.1.2*
rpm -Uvh libstdc++-devel*
rpm -Uvh gcc-c++-4.1.2*
rpm -Uvh libaio*
rpm -Uvh libaio-devel*
rpm -Uvh numactl-devel*
rpm -Uvh sysstat*
rpm -Uvh unixODBC*
Database Connectivity
Oracle ODBC Drivers
If you intend to use ODBC, then install the most recent ODBC Driver Manager for Linux. Download and install the Driver Manager from the following URL:
Linux RPMs are also available on this Web site.
To use ODBC, you must also install the following additional ODBC RPMs, depending on your operating system
| Distribution | On Linux x86 | On Linux x86-64 |
|---|---|---|
| OEL 4 | unixODBC-2.2.11 (32 bit) or later unixODBC-devel-2.2.11 (32 bit) or later | unixODBC-2.2.11 (32 bit) or later unixODBC-devel-2.2.11 (64 bit) or later unixODBC-2.2.11 (64 bit ) or later |
| OEL 5 | unixODBC-2.2.11 (32 bit) or later unixODBC-devel-2.2.11 (32 bit) or later | unixODBC-2.2.11 (32 bit) or later unixODBC-devel-2.2.11 (64 bit) or later unixODBC-2.2.11 (64 bit) or later |
Oracle JDBC/OCI Drivers
You can use JDK 6 Update 10 (Java SE Development Kit 1.6 u10) or JDK 5 (1.5.0_16) with the JNDI extension with the Oracle Java Database Connectivity and Oracle Call Interface drivers. However, these are not mandatory for the database installation. Please note that IBM JDK 1.5 is installed with this release.
Parameters
Installation Fixup Scripts
During installation, for certain prerequisite check failures, you can click Fix & Check Again to generate a fixup script (runfixup.sh). You can run this script as a root user to complete the required preinstallation steps.
The fixup script does the following:
- Checks and sets kernel parameters to values required for successful installation, including:
- Shared memory parameters
- Semaphore parameters
- Open file descriptor and UDP send/receive parameters
- Sets permissions on the Oracle Inventory directory.
- Reconfigures primary and secondary group memberships for the installation owner, if necessary, for the Oracle Inventory directory, and for the operating system privileges groups.
- Sets up virtual IP and private IP addresses in /etc/hosts.
- Sets shell limits to required values, if necessary.
- Installs the Cluster Verification Utility packages (cvuqdisk rpm).
Using fixup scripts will not ensure that all the prerequisites for installing Oracle Database are satisfied. You must still verify that all the preinstallation requirements are met to ensure a successful installation.
Network Setup
Multihomed computer
You can install Oracle Database on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name. In addition, you can set up aliases for the host name.
By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, then Oracle Universal Installer determines the host name from the /etc/hosts file.
Example of /etc/hosts file with oel11g.localdomain as hostname
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 oel11g.localdomain oel11g
127.0.0.1 localhost.localdomain localhost
Clients must be able to access the computer either by using this host name or by using aliases for this host name. To verify this, ping the host name from the client computers using the short name (host name only) and the full name (host name and domain name). Both tests must be successful.
Use the following procedure to set the ORACLE_HOSTNAME environment variable. For example, if the fully qualified host name is somehost.us.example.com, then enter the following commands for the Bourne, Bash, or Korn shell:
$ ORACLE_HOSTNAME=oel11g.localdomain
$ export ORACLE_HOSTNAME
Multiple aliases
A computer with multiple aliases is registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer. Before installing Oracle Database on such a computer, set the ORACLE_HOSTNAME environment variable to the computer whose host name you want to use.
DNS
Verify the value of the DNS configuration file resolv.conf. The nameserver must be not set or set to a valid DNS server and you can add the two time-out parameters.
Operating System Groups and Users
If you prefer to allocate operating system user privileges so that you can use:
- one administrative user
- and one group for operating system authentication for all administrative privileges,
then you can use:
- the oracle user as the installation owner,
- and use one group as the primary group for any user requiring administrative privileges for Automatic Storage Management, and Oracle Database administration. This group must also be the Oracle Inventory group. To simplify using the defaults for Oracle tools the group name should be oinstall.
You can also create custom configuration groups and users based on job role separation. A custom configuration is a configuration with groups and users that divide access privileges granted by membership in separate operating system groups and users. You can create a single user (for example, oracle) to own both Oracle database, and Oracle grid infrastructure installations. Alternatively, you can create a separate user (for example, grid) to own the Oracle grid infrastructure installation.
Log in as root to create groups and users.
Installation Groups
You can designate a unique group, separate from database administrator groups, or you can use the same group as the OSASM and OSDBA group, to grant system privileges to administer both the ASM instances and Oracle Database instances.
| Oracle Documentation Group | Linux Group in examples | Description |
|---|---|---|
| Database Groups | ||
| Create the following operating system groups if you are installing Oracle Database: | ||
| OSDBA | dba | This group identifies operating system user accounts that have database administrative privileges (the SYSDBA privilege). |
| OSOPER | oper | This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of database administrative privileges (the SYSOPER privilege). This group cannot directly connect as SYSOPER, unless explicitly granted. However, they will have the privileges granted by the SYSOPER privilege. |
| For Oracle grid infrastructure and Automatic Storage Management | ||
| Create the following operating system groups if you are installing Oracle grid infrastructure for Automatic Storage Management : | ||
| OSDBA | asmdba | The OSDBA group for Automatic Storage Management can be the same group used as the OSDBA group for the database, or you can create a separate OSDBA group for Automatic Storage Management (typically, asmdba) to provide administrative access to Automatic Storage Management instances. The Oracle grid infrastructure software owner (typically, grid) must be a member of the OSDBA group. Membership in the OSDBA group allows access to the files managed by Automatic Storage Management. If you have a separate OSDBA group for Automatic Storage Management, then the Oracle Restart software owner must be a member of the OSDBA group for each database and the OSDBA group for Automatic Storage Management |
| OSASM | asmadmin | SYSASM privileges for Automatic Storage Management files provide administrator privileges for storage file. In Oracle documentation, the operating system group whose members are granted SYSASM privileges is called the OSASM group, and in command lines, is referred to as asmadmin. Automatic Storage Management can support multiple databases. Members of the OSASM group can use SQL to connect to an Automatic Storage Management instance as SYSASM using operating system authentication. The SYSASM privileges permit mounting and dismounting disk groups, and other storage administration tasks. SYSASM privileges provide no access privileges on an RDBMS instance. If you do not designate a separate group as the OSASM group, then the OSDBA group you define is also by default the OSASM group. |
| OSOPER | asmoper | This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of Oracle instance administrative privileges (the SYSOPER for ASM privilege), including starting up and stopping the Oracle ASM instance. By default, members of the OSASM group also have all privileges granted by the SYSOPER for ASM privilege. If you want to have an OSOPER for ASM group, then the grid infrastructure owner must be a member of this group. |
/usr/sbin/groupadd -g 502 dba
/usr/sbin/groupadd -g 505 oper
/usr/sbin/groupadd -g 504 asmadmin
/usr/sbin/groupadd -g 506 asmdba
/usr/sbin/groupadd -g 505 asmoper
Creating the Oracle Inventory Group
When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file. This file identifies:
- the name of the Oracle Inventory group (typically, oinstall),
- and the path of the Oracle Inventory directory.
An oraInst.loc file has contents similar to the following:
inventory_loc=central_inventory_location
inst_group=group
where:
- central_inventory_location is the location of the Oracle Central Inventory,
- and group is the name of the group that has permissions to write to the central inventory.
To determine if the Oracle Inventory group exist, enter the following command:
# grep oinstall /etc/group
To determine whether the oraInst.loc file exists, enter the following command:
# more /etc/oraInst.loc
If the oraInst.loc file exists, then the output from this command is similar to the following:
inventory_loc=/u01/app/oraInventory
inst_group=oinstall
In the previous output example:
- The inventory_loc group shows the location of the Oracle Inventory
- The inst_group parameter shows the name of the Oracle Inventory group (in this example, oinstall).
If the oraInst.loc file does not exist, then create the Oracle Inventory group by entering the following command:
# /usr/sbin/groupadd oinstall
Users for Oracle Installations with Job Role Separation
Oracle recommends that you create one software owner to own each Oracle software installation (typically, oracle, for the database software and grid for the Oracle Restart owner user). You must create at least one software owner the first time you install Oracle software on the system.
Oracle software owners must have the Oracle Inventory group as their primary group, so that each Oracle software installation owner can write to the Central Inventory. The database software owner (typically, oracle) must also have the OSDBA group of the grid infrastructure home so that database instances can log on to Automatic Storage Management, and (if you create it) the OSOPER group as secondary groups. In Oracle documentation, the Oracle software owner users are referred to as oracle users.
For Oracle grid infrastructure only, the grid user (grid) needs to be in the OSDBA group of every database home.
You must create an Oracle software owner user in the following circumstances:
- If an Oracle software owner user does not exist; for example, if this is the first installation of Oracle software on the system.
[root@oel5u5 ~]# id oracle
id: oracle: No such user
- If an Oracle software owner user exists,
[root@oel5u5 ~]# id oracle
uid=502(oracle) gid=507(oinstall) groups=507(oinstall),502(dba),505(oper),506(asmdba)
but you want to use a different operating system user, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation.
- If you have created an Oracle software owner for Oracle grid infrastructure, such as grid, and you want to create a separate Oracle software owner for Oracle Database software, such as oracle.
To create an oracle user, enter a command similar to the following:
[root@oel5u5 ~]# /usr/sbin/useradd -u 502 -g oinstall -G dba,asmdba,[oper] oracle
In the preceding command:
- The -u option specifies the user ID. Using this command flag is optional, as you can allow the system to provide you with an automatically generated user ID number. However, you must make note of the oracle user ID number, as you require it later during preinstallation.
- The -g option specifies the primary group, which must be the Oracle Inventory group–for example, oinstall
- The -G option specifies the secondary groups, which must include the OSDBA group, and, if required, the OSOPER and ASMDBA groups. For example: dba, or asmdba,oper
Set the password of the oracle user:
[root@oel5u5 ~]# passwd oracle
If the oracle user exists, but its primary group is not oinstall, or it is not a member of the appropriate OSDBA or OSOPER groups, then modify it as follows:
Specify the primary group using the -g option and any required secondary group using the -G option:
[root@oel5u5 ~]# /usr/sbin/usermod -g oinstall -G dba,asmdba[,oper] oracle
You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer you must configure the environment of the oracle user. Configuring the oracle User's Environment
Shell limits for the Oracle installation owners (for instance oracle and grid user)
To improve the performance of the software, you must increase the following shell limits for the Oracle installation owners (such as oracle and grid user):
| Shell Limit | Item in limits.conf | Hard Limit |
|---|---|---|
| Maximum number of open file descriptors | nofile | 65536 |
| Maximum number of processes available to a single user | nproc | 16384 |
| Maximum size of the stack segment of the process | stack | 10240 |
To increase the shell limits:
Depending on your environment, make the following changes for all Oracle installation owners. The steps below only show the user oracle.
- Add the following lines to the /etc/security/limits.conf file: (the following example shows only the software account owner oracle):
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
- Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:
session required pam_limits.so
Kernel Parameters
The kernel parameter values shown in the following section are minimum values only.
| kernel parameter | Minimum Value | Configuration File |
|---|---|---|
| semmsl | 250 | /proc/sys/kernel/sem |
| semmns | 32000 | /proc/sys/kernel/sem |
| semopm | 100 | /proc/sys/kernel/sem |
| semmni | 128 | /proc/sys/kernel/sem |
| shmall | 2097152 | /proc/sys/kernel/shmall |
| shmmax | Either 4 GB - 1 byte, or half the size of physical memory (in bytes), whichever is lower. Default: 536870912 | /proc/sys/kernel/shmmax |
| shmmni | 4096 | /proc/sys/kernel/shmmni |
| file-max | 6815744 | /proc/sys/fs/file-max |
| aio-max-nr | Maximum: 1048576 Note: This value limits concurrent outstanding requests and should be set to avoid I/O subsystem failures. | /proc/sys/fs/aio-max-nr |
| ip_local_port_range | Minimum: 9000 Maximum: 65500 | /proc/sys/net/ipv4/ip_local_port_range |
| rmem_default | 262144 | /proc/sys/net/core/rmem_default |
| rmem_max | 4194304 | /proc/sys/net/core/rmem_max |
| wmem_default | 262144 | /proc/sys/net/core/wmem_default |
| wmem_max | 1048576 | /proc/sys/net/core/wmem_max |
If the current value for any parameter is greater than the value listed in this table, then the Fixup scripts do not change the value of that parameter.
To get the value of a parameter:
[root@oel11g /]# /sbin/sysctl -a | grep fs.aio-max-nr
fs.aio-max-nr = 65536
Using a text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following as it's explain in this article: On Linux, how to change the Kernel Parameter values (sysctl.conf)?
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
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 = 1048586
net.ipv4.tcp_wmem = 262144 262144 262144
net.ipv4.tcp_rmem = 4194304 4194304 4194304
The minimum value required for shmmax is 0.5 GB. However, Oracle recommends that you set the value of shmmax to 2.0 GB for optimum performance of the system.
Directories
Oracle base directory
The Oracle base directory is a top-level directory for Oracle software installations.
To create an appropriate directory:
- Check the free disk space on each mounted file system using the following command:
# df -h
- Create the Oracle Base Directory
mkdir -p /u01/app/oracle
chown -R oracle:oinstall /u01/app/oracle
chmod -R 775 /u01/app/oracle
chmod -R 775 /u01/app
- set the ORACLE_BASE environment variable for the user Oracle to specify the Oracle base directory that you have created.
OraInventory
The Oracle Inventory directory (oraInventory) stores an inventory of all software installed on the system.
mkdir -p /u01/app/oraInventory
chown -R oracle:oinstall /u01/app/oraInventory
chmod -R 775 /u01/app/oraInventory
Oracle Home Directory
The Oracle home directory is the directory where you choose to install the software for a particular Oracle product.
Oracle Universal Installer creates this directory path that you specify under the Oracle base directory and then you do not need to create this directory.
Storage Option
When you create a database during the installation, you can specify one of the following storage options for database files:
Prepare storage for Asm
Oracle Database - Prepare Storage for Oracle Automatic Storage Management on Linux
Steps
To continue: Configuring Storage for Oracle Database Files Using Block Devices
Disable secure linux
Disable secure linux by editing the /etc/selinux/config file, making sure the SELINUX flag is set as follows:
SELINUX=disabled
Alternatively, this alteration can be done using the GUI tool.
Configuring the oracle User's Environment
You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer you must configure the environment of the oracle user.
Shell Startup Script
To set the environement variable, we will modify the shell startup script.
Do not install Oracle Database 11g Release 2 (11.2) software into an existing Oracle home.
for a Bourne, Bash, or Korn shell
Login as the oracle user and add the following lines at the end of the login configuration file which depend of your shell.
For the Bourne, Bash, or Korn shell, add the environment variables to the .profile file, or the .bash_profile file for the Bash shell. on Red Hat Enterprise Linux
# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_HOSTNAME=oel11g.localdomain; export ORACLE_HOSTNAME
ORACLE_UNQNAME=orcl; export ORACLE_UNQNAME
ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1; export ORACLE_HOME
ORACLE_SID=orcl; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
Some installation changes the default profile but as you have environment variables that can be different from one user to another (such as ORACLE_HOME), the login script is preferred rather than the default profile
For information: Ulimit
for a C shell
Login as the oracle user and add the following lines at the end of the login configuration file which depend of your shell.
For the C shell, add the environment variables to the .login file.
setenv TMP /tmp
setenv TMPDIR /tmp
setenv ORACLE_BASE /u01/app/oracle
setenv ORACLE_SID DB11G
if ( \$USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
umask 022
endif
For information: Linux - Umask (user mask)
On the shell
Enter the following commands to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:
Bourne, Bash, or Korn shell
unset ORACLE_HOME
unset TNS_ADMIN
C shell
unsetenv ORACLE_HOME
unsetenv TNS_ADMIN
Installation
Run the installer
The installation files are on the hard disk, then we change in the directory to the database directory and enter the runInstaller command.
If the installation files are on installation media, enter commands similar to the following, where directory_path is the path of the database directory on the installation media:
/directory_path/runInstaller
Oracle Universal Installer automatically installs the Oracle-supplied version of the JRE. This version is required to run Oracle Universal Installer and several Oracle assistants. Do not modify the Java Runtime Environment (JRE) except by using a patch provided by Oracle Support Services.
[oracle@oel11g ~]$ cd /tmp/database
[oracle@oel11g database]$ ./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 80 MB. Actual 2238 MB Passed
Checking swap space: must be greater than 150 MB. Actual 1983 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010-07-10_11-09-06AM. Please wait ...
[oracle@oel11g database]$
Configure Security Updates
Next
Installation Option
You can choose one of this options:
- Create and Configure a Database: This option creates a new database along with sample schemas.
- Install Database Software Only: This option only installs the database binaries. To configure database, you must run Oracle Database Configuration Assistant after the software installation.
- Upgrade an Existing Database: This option installs the software binaries in a new Oracle home. At the end of the installation, you can upgrade the existing database.
Choose “Create and configure an database”. Click Next
System Class
You can choose one of the following options:
- Desktop Class: Choose this option if you are installing on a laptop or desktop class system. This option includes a starter database and allows minimal configuration. This option is designed for those who want to get up and running with the database quickly.(The ORACLE_HOSTNAME Environment Variable must be set)
- Server Class: Choose this option if you are installing on a server class system, such as what you would use when deploying Oracle in a production data center. This option allows for more advanced configuration options. Advanced configuration options available using this option include Oracle RAC, Automatic Storage Management, backup and recovery configuration, integration with Enterprise Manager Grid Control, and more fine-grained memory tuning, among many others.
Choose “Desktop Class” and click Next
Typical Installation
The default character set suggested or used by Oracle Universal Installer and Database Configuration Assistant in this release is based on the language configuration of the operating system but Oracle recommend AL32UTF8
Installation Methods:
- Typical Installation: This installation method is selected by default. It lets you quickly install Oracle Database using minimal input. It installs the software and optionally creates a general-purpose database using the information that you specify on this screen.
- Advanced Installation: This installation method enables to perform more complex installations, such as creating individual passwords for different accounts, creating specific types of starter databases (for example, for transaction processing or data warehouse systems), using different language groups, specifying e-mail notifications, and so on.
Create Inventory
By default, the Oracle Inventory directory is not installed under the Oracle Base directory. This is because all Oracle software installations share a common Oracle Inventory, so there is only one Oracle Inventory for all users, whereas there is a separate Oracle Base for each user.
Prerequisite check
If you don't have enough swap space (minimum 1.5 the total amount of physical memory), check in this article on how to increase it : Linux - Swap / Paging
Summary
Finish
Configuration script
[root@oel11g database]# /u01/app/oraInventory/orainstRoot.sh
Changing permissions of /u01/app/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete.
[root@oel11g database]# /u01/app/oracle/product/11.2.0/db_1/root.sh
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/11.2.0/db_1
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
Finished product-specific root actions.
When you run the root.sh script, the script prompts you for the path of the local bin directory and automatically copies the oraenv, coraenv, and dbhome scripts to the directory that you specify. The default local bin directory is /usr/local/bin. If you do not run the root.sh script, then you can manually copy the oraenv or coraenv and dbhome scripts from the ORACLE_HOME/bin directory to the local bin directory.
Finish
Try then connect to the database control of the machine using the user name SYSTEM and connect as SYSDBA:
Postinstallation Tasks
When you install Oracle Database, some options are enabled and others are disabled. If you want to enable or disable a particular database feature for an Oracle home, then shut down the database and use the chopt tool.
Backup of root.sh
Oracle recommends that you back up the root.sh script (ORACLE_HOME/root.sh) after you complete an installation. If you install other products in the same Oracle home directory, then Oracle Universal Installer updates the contents of the existing root.sh script during the installation. If you require information contained in the original root.sh script, then you can recover it from the backed up root.sh file.
PL/SQL recompilation
Start the script utlrp.sql as sys. This script recompiles all PL/SQL modules that might be in an invalid state, including packages, procedures, and types.
@?/rdbms/admin/utlrp.sql
Getting Started
Status verification
lsnrctl status
emctl status dbconsole
Start
lsnrctl start
emctl start dbconsole
[oracle@oel11g ~]$ sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Mon Sep 13 15:35:43 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> startup
ORA-01031: insufficient privileges
SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 619360256 bytes
Fixed Size 1338280 bytes
Variable Size 423625816 bytes
Database Buffers 188743680 bytes
Redo Buffers 5652480 bytes
Database mounted.
Database opened.
Support
Very slow connection through the listener
Verify the value of the DNS configuration file resolv.conf. The nameserver must be not set or set to a valid DNS server and you can add the two time-out parameters.