2016 - Deploying Oracle RAC Database 12c on RHEL 7 - Best Practices

Updated -

IT organizations face challenges of optimizing Oracle database environments to keep up with the ever increasing workload demands and evolving security risks. This reference architecture provides a step-by-step deployment procedure with the latest best practices to install and configure an Oracle Real Application Clusters (RAC) Database 12c Release 1 (12.1)* with Oracle Automatic Storage Management (ASM). It is suited for system, storage, and database administrators deploying Oracle RAC Database 12c Release 1 (12.1) on Red Hat Enterprise Linux 7. It is intended to provide a Red Hat | Oracle reference architecture that focuses on the following tasks:
• Deploying Oracle Grid Infrastructure 12c Release 1 (12.1.0.2.0)
• Deploying Oracle RAC Database Software 12c Release 1 (12.1.0.2.0)
• Deploying an Oracle RAC Database 12c Release 1 (12.1.0.2.0) with shared SAN disks
• Using Oracle ASM disks with udev rules
• Securing the Oracle RAC Database 12c environment with SELinux

Attachments

10 Comments

Hello,

i'm using the documentation and i try to do what is tell in the section 3.2.2 Public Network Configuration and it don't seem to work
with the graphical tool it' creating the bond but after that my network is not working anymore.

so i have done it by creating manually the bond file and changing the net file configuration for each interface and stopping the network manager service and using the network service instead and that method work.

is it possible to test the method and see if their is something missing in this part to make it work or just use the manual method in the documentation.

also in the section 3.4.2 you got the following text:

Once the partitions are created, on all the nodes in the Oracle RAC Database cluster, run the
following kpartx command on each device mapper volume in order to update the partition
table mapping.

this part is not true:

you don't have to create the partition on the other node but just reboot the other node and they will see the new partition that have been create after that.

If you could modified the document to included those change it would be great because i search 1 day to find my solution.

Stephane

Hi Stephane,

Sorry you had some issues with a few of the steps. I plan on making some edits to the paper in the new future and when I do I'll make the adjustments accordingly. With regards to the kpartx, using that command "should" show the new partitions on the systems but if it doesn't as you mentioned a simple reboot works.

Is there an updated version of this document for 12c R2 (12.2) ? I havn't been able to find it,

At this time there isn't any update for Oracle 12c R2 scheduled.

Hello, is it a given you need a gpt label / primary partition for all asm disks?

Hi Andrew,

A primary partition for each disk is recommended.

Thanks for the reply, Roger. None are setup yet however we see errors such as this during the setup. It is OEL 7.6

Shared Storage Accessibility:/dev/dm-4,/dev/dm-5,/dev/dm-12,/dev/dm-23,/dev/dm-13,/dev/dm-24,/dev/dm-14,/dev/dm-25,/dev/dm-15,/dev/dm-2,/dev/dm-26,/dev/dm-20,/dev/dm-21,/dev/dm-11,/dev/dm-22,/dev/dm-33,/dev/dm-16,/dev/dm-17,/dev/dm-18,/dev/dm-19 - This test checks the shared access of storage across the cluster nodes. Operation Failed on Nodes: [odsdb-kn-u12,  odsdb-kn-u11]
Verification result of failed node: odsdb-kn-u12  Details:  -  PRVG-0802 : Storage type for path "/dev/dm-4" could not be determined on node "x". PRVG-0801 : invalid internal command tags  - Cause:  An error occurred while attempting to determine the storage type of the indicated path. Accompanying messages provide further details.  - Action:  Resolve the issues described in any accompanying messages and retry.  -  PRVG-0802 : Storage type for path "/dev/dm-5" could not be determined on node "x". PRVG-0801 : invalid internal command tags  - Cause:  An error occurred while attempting to determine the storage type of the indicated path. Accompanying messages provide further details.  - Action:  Resolve the issues described in any accompanying messages and retry.  - 

I have not seen that error personally. However, it seems like it is looking for your dm device instead of your say multipath device i.e. /dev/mapper/mpathp1 for example. The device mapper device points to a dm device. When using shared storage it should point to that not the /dev/dm-*

Hope that helps

Roger

Hi Roger, thanks for the reply.

I have put a little output here if that's ok, the link is auto generated by the rules file to the dm device, heres one of the disks

cat /etc/udev/rules.d/95-storage-asm.rules 
ACTION=="add|change", ENV{DM_UUID}=="mpath-360002ac000000000000067700001cdce", SYMLINK+="oracleafd/disks/vote1", OWNER="grid" GROUP="oinstall", MODE="0660"

# udevadm info --query=all --name=/dev/dm-9 | grep -i DM_UUID
E: DM_UUID=mpath-360002ac000000000000067700001cdce
# udevadm info --query=all --name=/dev/mapper/mpatha | grep -i DM_UUID
E: DM_UUID=mpath-360002ac000000000000067700001cdce

lrwxrwxrwx. 1 root root 10 Jun 13 12:44 vote1 -> ../../dm-9

root@odsdb-kn-u11 # ls -l ../../dm-9
brw-rw----. 1 grid oinstall 253, 9 Jun 13 12:44 ../../dm-9

What I'd say is you need to put to the /dev/mapper device not to the dm-* device directly. I believe that is why it is failing. Realistically though, the important part is that your disks have the correct ownership and permissions, as long as you can confirm that, I wouldn't worry to much about the check. Is this cluvfy or you doing the check within the installer? If it is cluvfy, I'd just go straight to the installer and make sure the installer doesn't see any errors.