> Red Hat Enterprise Linux 4* or Oracle Linux 4*
> Red Hat Enterprise Linux 5* or Oracle Linux 5*
Download Oracle Database 11g Release 2 (11.2.0.1.0) Enterprise/Standard Edition for Linux x86 (32 Bit): http://www.oracle.com/technetwork/datab ... index.html
Directions:
1. All files are in the .zip format. There is an unzip utility here (http://updates.oracle.com/unzips/unzips.html) if you need one.
2. Download and unzip both files to the same directory.
3. Installation guides and general Oracle Database 11g documentation are here (http://www.oracle.com/technetwork/datab ... index.html).
4. Review the certification matrix for this product here (http://www.oracle.com/technetwork/index ... 87287.html).
- Follow the procedure in Installing Red Hat Linux 4 for Oracle 10g R2 (32-bit) (http://www.oracle-forums.com/viewtopic.php?f=3&t=25) for installing the Operating System.
- Check Memory (RAM) and swap space requirement
Oracle recommends:
> Minimum Physical Memory should be at least 1024MB.
*** If the size of the RAM is less than the required size, then you must install more memory before continuing.
> For RAM Between 1 GB and 2 GB, Swap space is 1.5 times the size of the RAM.
> For RAM Between 2 GB and 16 GB, Swap space is Equal to the size of the RAM
> For More than 16 GB of RAM, Swap space is 16 GB
- Check Additional Hardware Requirements
> 1 GB of space in the /tmp directory. Adjust the size if needed or delete unnecessary files. Oracle Universal Installer (OUI) requires up to 1 GB of free space in the /tmp directory
> Between 1.5 GB and 3.5 GB of disk space for the Oracle software, depending on the installation type
> 1.2 GB of disk space for a preconfigured database that uses file system storage (optional)
- Validate that the system meets these requirements
> Check the physical RAM size: [oracle@oracle11g ~]$ grep MemTotal /proc/meminfo
> Check the configured swap space: [oracle@oracle11g ~]$ grep SwapTotal /proc/meminfo
> Check the available RAM and swap space: [oracle@oracle11g ~]$ free
> Check disk space available in the /tmp directory: [oracle@oracle11g ~]$ df -k /tmp
> Check the amount of free disk space on the system: [oracle@oracle11g ~]$ df -h
*** Below is the approximate disk space requirements for software files for each installation type.
For the benefit of newbies, we will perform installation in Graphical User Interface (GUI) mode.Installation Type Requirement for Software Files (GB)
Enterprise Edition 3.95
Standard Edition 3.88
- Display Requirements
> The minimum resolution for Oracle Database 11g Release 2 (11.2) is 1024 x 768 or higher.
- Check the Software Requirements
> Operating system: [oracle@oracle11g ~]$ cat /etc/issue
*** In this tutorial, I used Enterprise Linux Enterprise Linux AS release 4 (October Update 8)
> Kernel version: [oracle@oracle11g ~]$ uname -r
*** I used 2.6.9-89.0.0.0.1.ELsmp. Oracle recommends 2.6.9 or later.
- Install required Software Packages (RPMs)
> For Oracle Linux 4 and Red Hat Enterprise Linux 4, the following packages (or later versions) must be installed:
binutils-2.15.92.0.2-25 (i386)
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
> For Oracle Linux 5 and Red Hat Enterprise Linux 5, the following packages (or later versions) must be installed:
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
sysstat-7.0.2
> To check for the packages currently installed,
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' \
binutils compat-db compat-libstdc++ control-center gcc gcc-c++ glibc glibc-common \
libstdc++ libstdc++-devel make pdksh sysstat xscreensaver setarch libaio openmotif \
rsh compat-gcc-32 compat-gcc-32-c++ libaio-devel unixODBC-devel elfutils-libelf \
elfutils-libelf-devel glibc-headers libgcc numactl pdksh
- Once the basic installation of Guest Operating System is complete, install the following packages if not yet installed whilst logged in as the root user.[root@oracle11g RPMS]# rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' \
> binutils compat-db compat-libstdc++ control-center gcc gcc-c++ glibc glibc-common \
> libstdc++ libstdc++-devel make pdksh sysstat xscreensaver setarch libaio openmotif \
> rsh compat-gcc-32 compat-gcc-32-c++ libaio-devel unixODBC-devel elfutils-libelf \
> elfutils-libelf-devel glibc-headers libgcc numactl pdksh
binutils-2.15.92.0.2-25 (i386)
compat-db-4.1.25-9 (i386)
package compat-libstdc++ is not installed
control-center-2.8.0-12.rhel4.5 (i386)
gcc-3.4.6-11.0.1 (i386)
gcc-c++-3.4.6-11.0.1 (i386)
glibc-2.3.4-2.43 (i686)
glibc-common-2.3.4-2.43 (i386)
libstdc++-3.4.6-11.0.1 (i386)
libstdc++-devel-3.4.6-11.0.1 (i386)
make-3.80-7.EL4 (i386)
pdksh-5.2.14-30.6 (i386)
sysstat-5.0.5-25.el4 (i386)
xscreensaver-4.18-5.rhel4.14.0.1 (i386)
setarch-1.6-1 (i386)
libaio-0.3.105-2 (i386)
openmotif-2.2.3-10.5.el4 (i386)
rsh-0.17-25.4 (i386)
compat-gcc-32-3.2.3-47.3 (i386)
compat-gcc-32-c++-3.2.3-47.3 (i386)
libaio-devel-0.3.105-2 (i386)
unixODBC-devel-2.2.11-1.0.1.RHEL4.1 (i386)
elfutils-libelf-0.97.1-5 (i386)
elfutils-libelf-devel-0.97.1-5 (i386)
glibc-headers-2.3.4-2.43 (i386)
libgcc-3.4.6-11.0.1 (i386)
numactl-0.6.4-1.40 (i386)
pdksh-5.2.14-30.6 (i386)
[root@oracle11g ~]# cd /media/cdrom/Enterprise/RPMS/ <<< Ensure that you change to correct media location.
[root@oracle11g RPMS]# rpm -Uvh binutils*
[root@oracle11g RPMS]# rpm -Uvh compat-db*
[root@oracle11g RPMS]# rpm -Uvh compat-libstdc++*
[root@oracle11g RPMS]# rpm -Uvh control-center*
[root@oracle11g RPMS]# rpm -Uvh gcc-*
[root@oracle11g RPMS]# rpm -Uvh gcc-c++*
[root@oracle11g RPMS]# rpm -Uvh glibc*
[root@oracle11g RPMS]# rpm -Uvh glibc-common*
[root@oracle11g RPMS]# rpm -Uvh libstdc++*
[root@oracle11g RPMS]# rpm -Uvh libstdc++-devel*
[root@oracle11g RPMS]# rpm -Uvh make*
[root@oracle11g RPMS]# rpm -Uvh pdksh*
[root@oracle11g RPMS]# rpm -Uvh sysstat*
[root@oracle11g RPMS]# rpm -Uvh xscreensaver*
[root@oracle11g RPMS]# rpm -Uvh setarch*
[root@oracle11g RPMS]# rpm -Uvh libaio*
[root@oracle11g RPMS]# rpm -Uvh openmotif*
[root@oracle11g RPMS]# rpm -Uvh rsh-*
[root@oracle11g RPMS]# rpm -Uvh compat-gcc-32*
[root@oracle11g RPMS]# rpm -Uvh compat-gcc-32-c++*
[root@oracle11g RPMS]# rpm -Uvh libaio-devel*
[root@oracle11g RPMS]# rpm -Uvh unixODBC-devel*
[root@oracle11g RPMS]# rpm -Uvh elfutils-libelf*
[root@oracle11g RPMS]# rpm -Uvh elfutils-libelf-devel*
[root@oracle11g RPMS]# rpm -Uvh glibc-headers*
[root@oracle11g RPMS]# rpm -Uvh libgcc*
[root@oracle11g RPMS]# rpm -Uvh numactl*
[root@oracle11g RPMS]# rpm -Uvh pdksh*
- Perform the Oracle Installation Preinstallation Tasks
- Configure Name Resolution
> Perform the following steps whilst logged into Guest Operating System as the root user.
> The /etc/hosts file must contain the fully qualified host name.
> Fully qualified host name should be listed BEFORE the short-cut alias127.0.0.1 oracle11g.localdomain oracle11g
192.168.218.150 oracle11g.localdomain oracle11g
[oracle@oracle11g]$ cat /etc/hosts | grep `eval hostname`
- Verify that the host name has been set[oracle@oracle11g ~]$ cat /etc/hosts | grep `eval hostname`
192.168.218.150 oracle11g.localdomain oracle11g
> [oracle@oracle11g ~]$ hostname
- Verify that the domain name has not been set dynamically. This should not return any results.[oracle@oracle11g ~]$ hostname
oracle11g.localdomain
[oracle@oracle11g ~]$ domainname
- Configure Kernel Parameters[oracle@oracle11g ~]$ domainname
(none)
> Add or edit the following lines to the /etc/sysctl.conf file.
> Run the following command as root to reload the current value of kernel parameterskernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 6815744
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 1048576
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
/sbin/sysctl -p
> Increase the Resource Limits. Add the following lines to the /etc/security/limits.conf file.
> Add or edit the following line in the /etc/pam.d/login file, if it does not already exist.oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
- Create the Required Operating System Groups and Userssession required /lib/security/pam_limits.so
session required pam_limits.so
- The following operating system groups and user are required if you are installing Oracle Database:
> Login as root and create the groups.
[oracle@oracle11g ~]$ su -
> The OSDBA group (typically, dba): [root@oracle11g ~]# groupadd dba
*** This group identifies operating system user accounts that have database administrative privileges (the SYSDBA privilege).
> The OSOPER group for Oracle Database (typically, oper): [root@oracle11g ~]# groupadd 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 have the privileges granted by the SYSOPER privilege. By default, members of the OSDBA group have all privileges granted by the SYSOPER privilege.
> The Oracle Inventory group (oinstall): [root@oracle11g ~]# groupadd oinstall
*** This group owns the Oracle inventory, which is a catalog of all Oracle software installed on the system.
- The following operating system groups and user are required if you are installing Oracle Grid Infrastructure:
> The OSDBA group for Oracle ASM (typically, asmdba): [root@oracle11g ~]# groupadd asmdba
*** The OSDBA group for Oracle ASM can be the same group used as the OSDBA group for the database, or you can create a separate OSDBA group for Oracle ASM (typically, asmdba) to provide administrative access to Oracle ASM instances.
*** The Oracle Grid Infrastructure software owner (typically, grid) must be a member of the OSDBA group. Membership in the OSDBA group enables access to the files managed by Oracle ASM. If you have a separate OSDBA group for Oracle ASM, then the Oracle Restart software owner must be a member of the OSDBA group for each database and the OSDBA group for Oracle ASM.
> The OSASM group for Oracle ASM (typically, asmadmin): [root@oracle11g ~]# groupadd asmadmin
*** SYSASM privileges for Oracle ASM 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. Oracle ASM can support multiple databases.
*** Members of the OSASM group can use SQL to connect to an Oracle ASM instance as SYSASM using operating system authentication. The SYSASM privileges permit mounting and dismounting of 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.
> The OSOPER group for Oracle ASM (typically, asmoper): [root@oracle11g ~]# groupadd 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 group for Oracle ASM, then the Oracle Grid Infrastructure owner must be a member of this group.
> Login as root and create the Oracle Software Owner User which belongs to oinstall,dba,asmdba, oper, asmoper and asmadmin groups.
[root@oracle11g ~]# useradd -g oinstall -G dba,asmdba,asmadmin,oper, asmoper oracle
> Change the password for Oracle software owner: [root@oracle11g ~]# passwd oracle
- Create the directories in which the Oracle software will be installed.
> Oracle Base Directory: [root@oracle10g ~]# mkdir -p /u01/app/oracle
> Oracle Inventory Directory: [root@oracle10g ~]# mkdir -p /u01/app/oracle/oraInventory
> Oracle Home Directory: [root@oracle11g ~]# mkdir -p /u01/app/oracle/product/11.2.0/dbhome_1
> Database File Directory: (Optional): [root@oracle11g ~]# mkdir -p /u02/oradata
> Recovery File Directory (flash recovery area) (Optional): [root@oracle10g ~]# mkdir -p /u01/flash_recovery_area
> Installation Location:[root@oracle11g ~]# mkdir -p /home/oracle/staging/
- Ensure that the above Locations are owned by oracle.
[root@oracle11g ~]# chown -R oracle:oinstall /u01 /u02
- Login as the oracle user and add the following lines at the end of the .bash_profile file.
[oracle@oracle11g ~]$ vi ~/.bash_profile
- Install the Oracle Database SoftwareTMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1; export ORACLE_HOME
ORACLE_SID=ORCL11G; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:/home/oracle/staging/dbamenu:$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
> In this guide, we will just install x86 Oracle 10g Release 2 Database Software.
- As oracle user, upload the Oracle Database 11g installer (linux_11gR2_database_1of2.zip and linux_11gR2_database_2of2.zip to /home/oracle/staging) via FTP client.
> [oracle@oracle11g ~]$ cd /home/oracle/staging/
> [oracle@oracle11g staging]$ unzip linux_11gR2_database_1of2.zip
> [oracle@oracle11g staging]$ unzip linux_11gR2_database_2of2.zip
- Log in to VMware as oracle user.
> Change directory to unzipped installer (cd1)
[oracle@oracle11g ~]$ cd /home/oracle/staging/database
> Start Oracle Universal Installer
[oracle@oracle11g database]$ ./runInstaller
- Specify Oracle Configuration Manager Details
You can enable Oracle Configuration Manager during or after installation, or choose not to enable it. To enable it during installation, enter the Customer Identification Number (CSI), My Oracle Support (formerly OracleMetaLink) Account User name, and Country code associated with your service agreement.
Click Next.
The new dialog prompts you to accept the license agreement. Click Accept License Agreement.
If you select Decline License Agreement, then Oracle Configuration Manager is installed but not configured.
> From Configure Security Updates, you may uncheck "I wish to receive security updates via My Oracle Support". Click Next. Select "Yes" when prompted if you wish to remain uninformed of critical security issues in your configuration"
Select any one of the following install options and click Next.
@ Create and configure a database - Choose this option to create a new database alongwith sample schemas.
@ Install database software only - Choose this option to install only the database binaries. To configure the database, you must run Oracle Database Configuration Assistant after the software installation.
@ Upgrade an existing database - Choose this option to 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.
> In Select Installation Option, select "Install database software only"
*** Select the type of database installation you want to perform and click Next.
@ Single Instance Database Installation - This option installs the database and the listener.
@ Real Application clusters Database Installation - This option installs Oracle Real Application Clusters and the listener.
> Select "Single instance database installation" from Node Selection.
*** Select the languages in which you want to run your product.
The selection changes the language of the products, which are being installed, and not the language of the installation itself.
Select the product language from the Available Languages list, transfer it to the Selected Languages list, and click Next.
Note: You can select more than one language. If you want to move the selected language to the Selected Languages list one at a time, then click the ">" button, else click ">>" button to move them all together. English and the language based on the locale setting of your operating system session are selected by default.
> Choose "English" for Product Languages.
*** Select the database edition you want to install and click Next.
@ Enterprise Edition - This installation type is designed for enterprise-level applications. It is engineered for mission-critical, high-security online transaction processing (OLTP) and data warehousing environments. If you select this installation type, then all separately licensable Enterprise Edition options are installed.
@ Standard Edition - This installation type is designed for department or workgroup-level applications and for small and medium-sized enterprises (SMEs). It is engineered to provide core relational database management services and options. It installs an integrated set of management tools, full distribution, replication, Web features, and facilities for building business-critical applications.
@ Standard Edition One (Desktop and Single Instance Installations Only) - This installation type is designed for department, workgroup-level, or web applications. From single-server environments for small business to highly distributed branch environments, Oracle Database Standard Edition One includes all the facilities necessary to build business-critical applications.
@ Personal Edition (Microsoft Windows Operating Systems Only) - This installation type installs the same software as the Enterprise Edition installation type, with the exception of the management packs. However, it supports only a single-user development and deployment environment that requires full compatibility with Enterprise Edition and Standard Edition. Oracle RAC is not installed with Personal Edition.
If you click Select Options, then you are given an option to select or deselect the products from the components list. Click OK.
Note: The Select Option button is enabled, only if you select Enterprise Edition installation type.
> Select Enterprise Edition for the Database Edition.
*** Specify Oracle base, Software Location, and click Next.
@ Oracle Base - The Oracle base directory is a top-level directory for Oracle software installations. The Oracle base path appears by default. You can change the path based on your requirement.
@ Software Location - In the Software Location field, accept the default values or enter the Oracle home directory path in which you want to install Oracle software. The directory path should not contain spaces.
> Verify the correct Installation Location.
Specify the UNIX group names for the database administrators (OSDBA) group and optionally, the database operators (OSOPER) group, then click Next.
Note: The groups that you specify must already exist. For Oracle Real Application Clusters installations, the group ID (gid) for each group must be the same on all nodes of the cluster.
These groups have the following significance:
@ OSDBA group
UNIX users that are members of this group have database administrator privileges for this Oracle installation. Members of the group can use operating system authentication to connect to a database instance with the SYSDBA privilege (using the AS SYSDBA clause). The default name for this group is dba.
You can specify different OSDBA groups for separate installations of Oracle software on the same system.
@ OSOPER group
This is an optional group. UNIX users that are members of this group have database operator privileges for this Oracle installation. Members of the group can use operating system authentication to connect to a database instance with the SYSOPER privilege (using the AS SYSOPER clause). The SYSOPER privilege is a subset of the SYSDBA privilege.
If you want a separate group to have SYSOPER privileges, specify a group name that is different from the OSDBA group for the OSOPER group. Otherwise, specify the same group name for both groups.
You can specify different OSOPER groups for separate installations of Oracle software on the same system.
This screen appears only if the UNIX user that started the Installer is not a member of the dba group.
> Select the default value for Privileged Operating System Groups. Database Administrator (OSDBA) Group: dba and Database Operator (OSOPER) Group: oinstall
The prerequisite checks ensure that the minimum system requirements to carry out the database installation are met.
If you click Check Again, then you can run the prerequisite check again to see if the minimum requirements are met to carry on with the database installation.
Click Fix & Check Again, if you want the installer to fix the problem and check the system requirements again.
Note: The Fix & Check Again option generates a script (UNIX only) that sets some of the system parameters to Oracle-recommended values. You need to run the script as the root user. Oracle recommends that you do not modify the contents of this script.
From the list, select one of the following options:
@ Show Failed: To get a failed prerequirements list.
@ Show All: To get a list of all the prerequirement checks run.
@ Show Succeeded: To get a list of the prerequirement checks that were successful.
Note: You can check Ignore All to ignore all the errors and proceed with the database installation.
> Let the install performs prerequisite checks.
This dialog presents a summary of the options you selected during the installation process. Depending on your installation, the information might include the following :
*** Global Settings
@ Disk space
@ Source location
@ Installation method
@ Database edition
@ Oracle Base
@ Software Location
@ OSDBA group
*** Database information
@ Configuration
@ Global Database Name
@ Oracle system identifier (SID)
@ Allocated memory
@ Automatic memory management option
@ Database Character Set
@ Management method
@ Database storage mechanism
@ Database file location
@ Automated backup
Click Save Response File if you want to save all the installation steps into a response file.
Click Finish.
> Review the Summary of Installation. Then click on Finish.
The Install Product screen appears when the product is installing. Installation operations include executing actions such as file copy and adding services on Windows systems and linking on UNIX systems, and executing decision points and calculations.
A progress bar shows the status of the installation on a per component basis, based on the component size. The size is relative to the total size of the installation.
Note: For upgrades and reinstallations, OUI deinstalls earlier versions of the product first before starting the installation.
Click Details for more information about the installation of the database.
If there are no required or optional configuration assistants for the installation, then Finish screen appears when the installation is completed.
After the database is installed, you are prompted to execute some root configuration script for new inventory as a root user. Click Next.
> Product Installation is now initiated.
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/dbhome_1
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]: y
Copying dbhome to /usr/local/bin ...
The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]: y
Copying oraenv to /usr/local/bin ...
The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]: y
Copying coraenv to /usr/local/bin ...
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.
[root@oracle11g dbhome_1]#
> Click "OK" to finish the installation.
Refer to below procedures:
http://www.oracle-forums.com/unexpected ... -t633.html
-- End of Installation --
