2014 - Deploying Oracle Database 12c on Red Hat Enterprise Linux 6

Updated -

Red Hat Enterprise Linux 6 provides an excellent foundation for database deployments with demonstrated stability, scalability, and performance. With the support for Oracle Database 12c Release 1 (12.1.0.2.0) on Red Hat Enterprise Linux 6, customers can increasingly look to deploy Oracle Databases in advanced configurations.

The steps and procedures described in this reference architecture should provide system, database, and storage administrators the blueprint required to create a robust and performing solution based on Oracle Databases. Administrators can reference this document to simplify and optimize the deployment process and employ the recommended practices for configuring Red Hat technologies while implementing the following tasks:
- Deploying Oracle Grid Infrastructure 12c Release 1 (12.1.0.2.0)
- Deploying Oracle Database Software 12c Release 1 (12.1.0.2.0)
- Deploying an Oracle Database 12c Release 1 (12.1.0.2.0) with shared SAN disks
- Using Oracle ASM disks with udev rules or with Oracle ASMLib
- Securing the Oracle Database 12c environment with SELinux

Attachments

Table of Contents

No

12 Comments

The following is mentioned under section "3.4.2 Partitioning Device Mapper Shared Disks":
"Partitioning of the device mapper shared disks is only required when using Oracle ASMLib.
This reference environment provides instructions to configure either Oracle ASMLib or udev
rules. Partitions for each device mapper volume are created to comply with either option."

Does it mean that it is not necessary to create partition on DM devices when using udev and not using ASMLib?

Then under section "3.4.3.1 Oracle ASMLib Alternative: Configuring udev Rules", the following is mentiuoned:
"As the root user, identify the Device Mapper Universally Unique IDentifier (DM_UUID)
for each device mapper volume."

But here, the "udevadm info --query=all" command uses disk partition names?

This is confusing. Can someone clarify if disk partition of device mapper devices is needed when using udev?

Hi Amir,

Sorry for the confusion. To answer your question, if you are using udev rules you do not need to create a partition. In Section 3.4.2 Parititoning Device Mapper Shared Disks, I mention that partitions are created because creating partitions complies with both ways of setting up asm disks (either with asmlib or device mapper).

Hi Roger,
I opened an SR with Oracle asking whether it is mandatory to create partitions on disks even if we are not using ASMLib. Oracle replied that it is mandatory to create partitions on disks even when not using ASMLib with Device Mapper devices. The document referenced by Oracle for the SR is 1365511.1.
I have had discussions with other people on this subject as well and they have all suggested that partitions are needed with multipath device mapper devices without ASMLib.

Hi Amir,
I'm suprised that Oracle says it's mandatory because definitely you can use the device mapper volume directly without a partition(I've done it many times). What I can say about not creating a partition, is if say an admin after the disk has been stamped with asm devices goes off and say labels the disk with fdisk it could override the asm header. This is probably why they recommend to create a partition. In my doc, I just wanted to point out that you had either option. In any case, I'll go ahead and update the doc to make the user create a parition as its overall probably a better option anyway.

Hi Roger,
When partitioning Multipath devices, do we need to partition the underlying /dev/sd devices or the multipath devices (dev/mapper/mpath)?

/dev/mapper/mpath

What should be the offset? 1M?

RHEL6 should properly align. All you should need to do is something like:
parted /dev/mapper/mpathX mklabel gpt mkpart primary "1 -1"

Do you have another document for Oracle 12c RDBMS on Red Hat Enterprise Linux 7 Best Practices as I would like to move forward with RHEL 7.x.

Mark,

RHEL7 + Oracle 12c can be found here: https://access.redhat.com/articles/1357883 . It doesn't address ASMFD or ASMLib. ASMLib was not addressed at the time of the writing as it was not available for RHEL7 when I wrote the paper. The use of udev rules is used instead. I can definitely look into the optional tool ASMFD that you mentioned as another way to setup ASM disks. I plan on updating RHEL7+Oracle12c paper later this year.

The Oracle 12c RDBMS on RHEL 7 would hopefully address the use of ASMFD instead of ASMLIB as well.

Just noticed that using the "nobarrier" mount option inside of virtual guests (i.e.: VMware) is no longer recommended. https://access.redhat.com/solutions/715923

I see the the included tuned profile was adjusted from previous versions, and removed this option? Is it safe to assume one should go back to previously configured servers, and update to the latest tuned profile - especially for virtualized Oracle DB servers?