ORACLE ON NUTANIX
Business-critical programs, such as Oracle databases, need us to believe beyond vanilla provisioning of their operating system(OS).
Virtualization addresses these demands well but occasionally we must still utilize physical Oracle
Database Servers due to licensing or company requirements.
Nutanix supports a number of situations, bringing web-scale advantages to both virtualized and bare-metal deployments(Physical) of all Oracle databases.
1) Minimum required 3 ESXi Nutanix nodes which is scale out with Nutanix AOS software.
2) Cluster size can be 3 to 48 VMware ESXi hosts.
3) Recommended clusters per vCenter is 2 VC * 24 or 4 VC* 12 host clusters.
4) Nutanix recommend 1 Datastore with inline compression of 60 min delay.
5) For oracle VMS Nutanix use VMXNet3 Network adaptor in VMware ESXi Server.
6) Storage adaptor required Minimum of 3 PVSCSI (OS + DB + redo), 4 for larger.
7) App or operating system disk configuration should be Thin provisioned, select disk mode as dependent
8) Database disk for standalone system thin provisioned, select disk mode as independent persistent
9) For Oracle RAC(Real Application clusters) use thick provisioned eager zeroed, select disk mode as independent persistent.
10) VMware tool must be latest.
11) Nutanix Recommend to use Nutanix Volume as the iSCSI in-guest initiator instead of Multwrier cluster configuration for Oracle RAC.
12) Use Network VLANs to separate Oracle RAC interconnect traffic. For Linux environments, use persistent file system or device naming identifiers to ensure that applications reference storage devices correctly across system reboots.
13) Disable Nutanix Shadow Clones for Oracle RAC database.
We made the Nutanix enterprise cloud applications to conduct almost any program along with converged storage and calculate at precisely the exact same appliance(Software), eliminating the complexity of distinct standalone storage options.
Use multiple disks rather than a single large disk for an application.
Consider using a minimum of one disk per Nutanix node to distribute the workload across all nodes in a cluster. Multiple disks per Nutanix node may also improve an application’s performance.
Use the Data Services IP method for external host connectivity to VGs.
Nutanix Volumes may export iSCSI volumes(ABS) into one case of Oracle or into Oracle RAC
Servers operating directly on servers that are physical.
Utilizing our volume group (VG) SAN based technology, Volumes may also export volumes straight to VMs running on precisely the exact same Nutanix cluster.
Typical Oracle database installation jobs –like backup, disaster recovery, snapshots, and clones–are still accessible which is traditional and, in Actuality, work much better from the Nutanix bunch with DR and ERA.
| Sr.No | Mount Point | Min Size | Max Size | Disk Type | Disk Mode |
| 1 | / | 10 | 20 | Thin provision | Dependent |
| 2 | /usr | 12 | 20+ | Thin provision | Dependent |
| 3 | /tmp | 12 | 12+ | Thin provision | Dependent |
| 4 | /home | 10 | 12+ | Thin provision | Dependent |
| 5 | /opt | 30 | 60+ | Thin provision | Dependent |
| 6 | /var or /var/log | 10 | 40+ | Thin provision | Dependent |
| 7 | Swap | 16 | 16 | Thin provision | Dependent |
Running Oracle on Nutanix provides many Benefits over conventional:
And linearly scale both the functionality and capacity non-disruptively as demands increase (Scale-out).
• Capability to handle a wide Selection of database workload kinds, such as transactional, analytical, Or a mixture of both on precisely the exact same platform.
• Datacenter infrastructure deployments in only hours, leading to shorter time to manufacturing .
Software to keep up and running even when the underlying hardware has problems or network problem.
*Use dedicated network interfaces for iSCSI traffic in your hosts.
• Integrated snapshots, remote replication(DR), and metro-level accessibility (SYNC Replication) to guard the database along with Oracle’s native information security capacities.
• Simplified management that eliminates multi-pathing, fiber channel zoning, and Lun assignment from the workflows.
Change the max_sector_kb to 1024 (the default is 512). With newer Linux distributions, the
default may already be set to 1024.
For UDEV rules, you can create a file with the below content under the /etc/
udev/rules.d directory.
ACTION==”add”, SUBSYSTEMS==”scsi”, ATTRS{vendor}==”NUTANIX “, ATTRS{model}==”VDISK”, RUN+=”/
bin/sh -c ‘echo 1024 >/sys$DEVPATH/queue/max_sectors_kb'”
ACTION==”add”, SUBSYSTEMS==”scsi”, ATTRS{vendor}==”NUTANIX “, ATTRS{model}==”VDISK”, RUN+=”/
bin/sh -c ‘echo 60 >/sys$DEVPATH/device/timeout'”
Reference :- Oracle RAC