How do I Install a Standalone Oracle Database?
RHEL 6.x, OL6.x
This document applies to Oracle Database 11g R2 running on Red Hat Enterprise Linux 6.x AS x86_64 or Oracle Enterprise Linux 6.x AS x86_64.
Software and Hardware Requirements
The following table describes the disk space required for an Oracle installation:
Minimum Disk Space Requirements
Software Installation Location
Grid Infrastructure home Oracle Database home
4.5 GB Space 4 GB of Space
Shared storage disk space
Sizes of database and Flashback Recovery Area
[top] Operating System Requirements
Preparing for Oracle Installation
Attaching to RHN/ULN Repository
NOTE: The documentation provided below discusses how to setup a local yum repository using your operating system installation media. If you would like to connect to the RHN/ULN channels, see the appropriate documentation. For Red Hat see, redhat.com/red_hat_network. For information relating to ULN network see, linux.oracle.com.
This section discusses hosting the repository files from a local filesystem storage. While other options to host repository files exist, they are outside of the scope of this document. It is highly recommended to use local filesystem storage for speed and simplicity of maintenance.
Installing the Dell Validated RPM
Once the Database node is attached to the appropriate yum repository, we will need to install the Dell Validated RPM package. The Dell Validated RPM package automates certain pieces of the installation process required for the installation of Oracle.
The process to install the Dell Validated RPM package is as follows:
Installing the Dell Oracle Utilities RPM
The Dell Oracle utilities RPM is designed to do the following Dell and Oracle recommended settings:
The process to install the Dell Oracle utilities RPM is as follows:
NOTE: The Dell-Oracle-Deplyoment tar contains the latest supported drivers provided from our Software Deliverable List (SDL). Consult the README file found within the Dell-Oracle-Deployment tar for installation instructions of the latest drivers. [top]
Oracle Software Binary Location
The Oracle software binaries should be located on the database node. It is important to note that starting with Oracle 11g R2 (188.8.131.52), Oracle Database patch sets are full installation of the Oracle software. For more information on how this impacts future Oracle deployments, see My Oracle Support note: 1189783.1 Important Changes to Oracle Database Patch Sets Starting with 184.108.40.206. [top]
Setting up the Network
NOTE: Ensure that the public IP address is a valid and routable IP address. To configure the public network :
Preparing Shared Storage for Oracle Installation
NOTE: In this section, the terms disk(s), volume(s), virtual disk(s), LUN(s) mean the same and are used interchangeably, unless specified otherwise. Similarly, the terms Stripe Element Size and Segment Size both can be used interchangeably. Oracle Standalone using Oracle ASM requires LUNs for storing Oracle Database files, and Flash Recovery Area (FRA). To ensure high availability it is recommended that you have:
NOTE: The use of device mapper multipath is recommended for optimal performance and persistent name binding. NOTE: For more information on attaching shared LUNs/volumes, see the Wiki documentation found at: http://en.community.dell.com/dell-groups/enterprise_solutions/w/oracle_solutions/3-storage.aspx [top]
Partitioning the Shared Disk
This section describes how to use Linux’s native partition utility fdisk to create a single partition on a volume/virtual disk that spans the entire disk.
To use the fdisk utility to create a partition:
Setting up Permissions for ASM disks using udev rules
Red Hat Enterprise Linux 6/Oracle Linux 6 have the ability to use udev rules to ensure that the system properly manages permissions of device nodes. In this case, we are referring to properly setting permissions for our LUNs/volumes discovered by the OS. It is important to note that udev rules are executed in enumerated order. When creating udev rules for setting permissions, please include the prefix 20- and append .rules to the end of the filename. An example file name is 20-dell_oracle.rules
In order to set udev rules, one must capture the WWIDs of each disk to be used within your ASM device using the scsi_id command.
The command is as follows:
scsi_id --page=0x83 --whitelisted --device=/dev/sdX
where sdX is the name of your block device.
If one must run this command to capture multiple WWIDs, one could use the following for loop to do just that via the shell:
[root@rhel6 ~]# for i in sdb sdc sdd sde; do \ printf "%s %s\n" "$i" \ "$(scsi_id --page=0x83 --whitelisted --device=/dev/$i)"; done
sdb 360026b900061855e000008a54ea5356a sdc 360026b9000618571000008b54ea5360b sdd 360026b900061855e000008a54ea5356a sde 360026b9000618571000008b54ea5360b
Once the WWIDs have been captured, create a file within the /etc/udev/rules.d/ directory and name it 20-dell_oracle.rules. A separate KERNEL entry must exist for each storage device and will require adding the WWID to the "RESULT==" field.
An example of what needs to be placed in the /etc/udev/rules.d/20-dell_oracle.rules file
#------------------------ start udev rule contents ------------------#
KERNEL=="dm-*", PROGRAM="scsi_id --page=0x83 --whitelisted --device=/dev/%k",RESULT=="360026b9000618571000008b54ea5360b", OWNER:="grid", GROUP:="asmadmin"
KERNEL=="dm-*", PROGRAM="scsi_id --page=0x83 --whitelisted --device=/dev/%k",RESULT=="360026b900061855e000008a54ea5356a", OWNER:="grid", GROUP:="asmadmin"
#-------------------------- end udev rule contents ------------------#
As you can see from the above, the KERNEL command looks at all dm devices, executes the PROGRAM which captures the WWID, if the RESULT of the WWID is matched, appropriately assign the grid user as the OWNER and the asmadmin group as the GROUP.
Installing Grid Infrastructure for Standalone Server
Before you install the Oracle 11g R2 Grid Infrastructure software for a Standalone Server on your system:
In the Select Installation Option window, select Install and Configure Grid Infrastructure for a Standalone Server and click Next.
In the Create ASM Disk Group window, enter the following information:
Click on Use Same Passwords for these accounts & Click Next
Leave the Operating System Groups to be default, Ignore the Warning and Click Next
Choose the Oracle Base and Software Location, and Click Next.
The Prerequisite Checks are performed& the summary screen is presented. Click Next on the summary screen.
The Installation proceeds. And the Progress is seen in the setup screen.
After the installation is complete, the Execute Configuration Scripts wizard is displayed. Complete the instructions in the wizard and click Ok.
Now that the Grid Infrastructure is installed, let’s now install the Database.
Creating Database Using DBCA
In the operations window, select Create Database, and Click Next
Select Custom Database Option the Database Templates Screen
In the Database Identification window:
In the Management Options window, select the default values and click Next.
In the Database Credentials window, enter the appropriate credentials for your Database.
In the Database File Location window, select:
In the Select Disk Group sub window, Select the Disk Group
In the Recovery Configuration window,
a) Specify Fast Recovery Area
b) Enable Archiving
Choose these options according to your environment and click Next
In the Database Content Window, Click Next
In the Initialization Parameters window:
In the Database Storage window, click Next
In the Creation Options Window, click Next
In the Summary window, click Ok to create Database.
Click Exit on the Database Configuration Assistant window after the database creation is complete.