Tintri VMstore With Oracle RAC Best Practice Guide
TECHNICALWHITEPAPERTintri VMstore withOracle RACBest Practice GuideFor Deploying Oracle Database RAC 12c with VMwarevSphere 6.0 on a Tintri VMstoreChristopher Slater, Technical Marketing EngineerJanuary 2016www.tintri.com
ContentsExecutive Summary . 4Overview . 5Consolidated List of Practices . 5Intended Audience . 6Assumptions . 6Vendor Guidelines . 7Tintri VMstore Best Practice Guide for Oracle . 7Oracle RAC with RHEL 7 and VMware Deployment and Best Practices Guides . 7VMware vSphere 6.0 Best Practices Guides. 7Oracle RAC Deployment Architecture . 8Oracle RAC Production Deployment Architecture. 8Oracle RAC Dev/Test Deployment Architecture . 9VMware Multi-Writer Flag and Oracle ASM . 10Shared Hard Disk Architecture for ASM . 10VMware vSphere Limitations of the Multi-Writer Flag. 11Tintri VM Supports the Multi-Writer Flag . 11Oracle ASM and the Tintri VMstore . 12Storage – UDEV rules . 12Storage – ASMLib . 12Deploying ASM with UDEV Rules . 13Step 1: Create the first RAC node . 13Step 2: Create Additional RAC Nodes . 13Step 3: Create the Oracle ASM Disk Group and RAC database . 13Deploying ASM with ASMLib . 15Step 1: Create the first RAC Node . 15Step 2: Create Additional RAC Nodes . 15Step 3: Create the Oracle ASM Disk Group and RAC database . 15Oracle RAC and Tintri Data Management Tools. 16Oracle RAC and VMware vMotion . 16Oracle RAC and Tintri VM Management Tools .17Tintri SnapVM . 18Tintri CloneVM . 18Tintri ReplicateVM . 20Tintri SyncVM . 21www.tintri.com2
Tintri VMstore Performance Dashboard . 22Using Oracle RMAN for Database Backups . 24Conclusion . 24References . 25Appendix A – Oracle RAC Support Statements . 26Appendix B – Example udev Rules .27www.tintri.com3
Executive SummaryOracle Real Application Clusters (RAC) extends the performance of an Oracle database by running asingle database image across multiple servers. Physical deployments of Oracle RAC require multipleseparate servers to host the individual RAC nodes. But when Oracle RAC is deployed with VMware eachRAC node runs as a separate virtual machine (VM). Running Oracle RAC on VMware providesdeployment and manageability options that are not available in physical deployments of RAC. Move production Oracle RAC nodes between physical hosts – perform hardware upgrades andmaintenance tasks on physical hardware without incurring downtime to individual RAC nodes.Host multiple Oracle RAC VMs on one physical host - create test and development systems thatmirror the production Oracle RAC environment but use a single physical host.The power of Oracle RAC comes from multiple database servers (RAC nodes) sharing the samedatabase files. But the power of RAC is only realized when the RAC nodes use a foundation of highperformance shared storage. Oracle RAC deployments in VMware have the additional performancechallenge of requiring storage that is well suited for virtualized application workloads.The Tintri VMstore is purpose-built to handle the storage I/O requirements of high performance databaseworkloads. Tintri storage actively adapts to demanding workloads, enabling virtualization administratorsand DBAs to focus on running the database instead of managing the storage infrastructure. Predictable Performance – Tintri storage arrays combine flash storage with VM-awaretechnology to oversee the performance needs of individual VMs without requiring manual tuningor configuration. VMs achieve consistent high performance and fast response times.Eliminate VM Contention – Tintri provides VMs with dedicated performance queues to preventrogue VMs from suffocating performance. This prevents high pressure I/O tasks - such asbackups and full table scans - from affecting other applications that share the VMstore.Monitor Performance – detailed per-VM and per-vDisk analytics provide details on theperformance of individual RAC nodes and database files. Drill down into host, network andstorage latency metrics for each RAC node to quickly identify sources of performancebottlenecks that were heretofore hidden in the virtualization infrastructure.Simplify Deployment – Tintri designed the VMstore so that IT and VM administrators with aworking knowledge of VMware vSphere can deploy and use the system in 30 minutes or less.Oracle RAC is typically employed with mission critical databases. These databases must be providedwith manageability tools that support the uptime and recoverability requirements of the individual RACnodes. However, VMware places limitations on the vSphere manageability tools that can be used withOracle RAC. For example, there is no support for VMware clones, Storage vMotion, and limited supportfor VMware snapshots. The Tintri VMstore does not share this limitation and features powerful per-VMmanageability tools for creating snapshots, clones and replicas that are uniquely suited to Oracle RAC. SnapVM – create point-in-time snapshot copies of individual RAC nodes. Create a baseline, orreference copy, of the RAC node before applying OS upgrades or Oracle patches.CloneVM – clone existing RAC nodes to expand the Oracle RAC database cluster, or quicklyreplace a failed RAC node from a previously created snapshot.ReplicateVM – use VM-level replication to copy an entire RAC cluster to another location for DRpurposes. Create multiple RAC clusters for test, development and training purposes.With its flash-based performance, powerful VM management tools, and simple deployment model, theTintri VMstore is an ideal storage platform for running Oracle RAC databases on VMware.www.tintri.com4
OverviewOracle makes transactional database software that is deployed by thousands of companies to store,manage, and derive business value from structured data. Oracle can be deployed as a stand-alonedatabase or with multiple database servers in a Real Application Cluster (RAC).This best practices paper focuses on the installation of Oracle RAC with Tintri and VMware. It details thesteps necessary to add Tintri storage to an Oracle RAC node. Detailed instructions for installing OracleRAC with VMware are provided in the white papers listed in the appendix of this document.Tintri has published a best practices paper for deploying a single instance of the Oracle database withthe Tintri VMstore. That guide contains detailed deployment and performance tuning recommendationsfor running Oracle with VMware on a Tintri VMstore. The performance tuning recommendations in thatdocument also apply to individual Oracle RAC nodes.Consolidated List of PracticesThis section summarizes the recommended best practices for deploying a Tintri VMstore with OracleRAC. Click on a recommendation to jump to the section of the document that corresponds to thatspecific best practice.DO: Apply recommendations from vendor-specific best practice guides for RHEL 7, VMware, Oracle, andTintri.DO: Enable the “muti-writer” flag on vDisks used with Oracle ASM and Oracle RAC.DO: Use Tintri SnapVM, CloneVM, and ReplicateVM tools with Oracle RAC VMs.DO: Use either UDEV rules or ASMLib to identify disks used by Oracle ASM.DO: If you decide to employ ASMLib, refer to the RedHat support page for details on acquiring andinstalling ASMLib for RedHat Enterprise Linux 7.DO: Use VMware vMotion to move production Oracle RAC VMs between ESXi hosts.DO: Use Tintri SnapVM, CloneVM, and ReplicateVM technology with Oracle RAC VMsDO: Tintri SyncVM can not be used with Oracle RAC VMs as they contain externally shared vDisks. Thisis by design and ensures the safety of the data in the shared vDisks.DO: Use the VMstore Performance Dashboard to view the performance of the Oracle RAC nodes andtroubleshoot latency breakdown across the infrastrucuture at a virtual disk and VM level.DO: Use Oracle RMAN for Oracle RAC database backups and restores.www.tintri.com5
Intended AudienceThis Best Practice Guide assists individuals who want to architect and deploy production Oracle RACdatabases with VMware and Tintri VMstore storage systems. Prior knowledge of Oracle RAC, RedHatLinux, virtualization, networking, and storage technology will help in understanding the conceptscovered in this best practice paper.AssumptionsThis paper provides best practices for deploying Tintri VMstores with Oracle Database 12c RAC, Red HatEnterprise Linux (RHEL), and VMware vSphere. This document is not intended to replace the vendorspecific best practices provided by Oracle, RHEL and VMware for their respective platforms. Werecommend that you download and follow the best practice guides that have been provided by thosecompanies. A list of best practice guides for Oracle, RHEL and VMware is documented in the Referencessection of this document.The reference system for these best practices employed Oracle 12c RAC database, RHEL 7, VMwarevSphere 6, and Tintri OS 3.2.x. Cisco UCS blades ran the ESXi hosts, and the UCS blades wereconnected to the Tintri VMstore via 10GbE networking.The skills needed to install Oracle RAC on VMware are the same skills needed to install Oracle RAC onphysical hardware. Although no prior knowledge of Tintri is needed when installing or running Oracledatabase software, we recommend having familiarity with the installation and operation of OracleClusterware, ASM, and Oracle RAC when deploying Oracle RAC on VMware with Tintri.This document assumes you are working with a fully configured, highly-available VMware Infrastructure.The configuration of hosts, networking, storage, and virtual infrastructure components is out of the scopeof this document. Recommendations on the design, deployment, and management of virtualinfrastructures powered by Tintri VMstore storage appliances is provided in the Tintri VMstore withVMware Best Practice Guide .www.tintri.com6
Vendor GuidelinesThe following vendor guidelines were used in this deployment of Oracle RAC with VMware and Tintri.Every attempt should be made to follow the suggestions in these guides, while keeping in mind thatthese vendor-specific best practices were made without knowledge of your unique deploymentarchitecture and database requirements.DO: Apply recommendations from vendor-specific best practice guides for RHEL 7, VMware, Oracle, and Tintri.Tintri VMstore Best Practice Guide for OracleTintri has published a best practice guide for deploying a single instance of an Oracle database withTintri, VMware, and RHEL. The best practices in this guide also apply to deployments of Oracle RAC. Tintri VMstore with Oracle Best Practice GuideOracle RAC with RHEL 7 and VMware Deployment and Best Practices GuidesWhen deploying Oracle database as a virtual machine, care should be taken to adhere to best practiceguides for deploying Oracle RAC with RHEL and VMware. The exact same best practices apply to theoperating system whether the machine is running on physical hardware or virtualized in a VM. For thispaper, the recommendations in the Red Hat Best Practices for Deploying Oracle RAC Database 12c withRHEL 7 were followed. Deploying Oracle RAC Database 12c on RHEL 7 – Best PracticesOracle Databases on VMware RAC Deployment GuideVMware vSphere 6.0 Best Practices GuidesVMware settings can affect the performance and scalability of your Oracle database. There is a wealth ofinformation on VMware and Oracle performance in the VMware Best Practices guides. Performance Best Practices for vSphere 6.0Best Practices for Performance Tuning of Latency-Sensitive Workloads in vSphere VMswww.tintri.com7
Oracle RAC Deployment ArchitectureWhen an Oracle RAC database is deployed with physical servers the deployment will include multiplenodes (servers) connected to each other by a private network. The database files are located on ashared storage subsystem where they can be accessed by all of the nodes. However, when Oracle RACis deployed with VMware the RAC nodes are deployed as separate VMs instead of physical servers.There are two types of deployment architectures used with Oracle RAC with VMware: Production andDev/Test.Oracle RAC Production Deployment ArchitectureThe first type of deployment architecture is used with production Oracle RAC databases whereperformance and availability are the primary goals. In this case individual Oracle RAC nodes aredeployed as single VMs, each VM runs on a dedicated vSphere host. This deployment architectureensures that all of the physical host resources are available to the individual RAC node at all times.The production deployment architecture is shown in figure 1.Figure 1 – Deployment Architecture for a 3-Node Production Oracle RAC Databasewww.tintri.com8
Oracle RAC Dev/Test Deployment ArchitectureThe second type of Oracle RAC deployment architecture is used create Oracle RAC Clusters for training,test, development, and QA purposes where lower deployment costs is the primary goal. With thisdeployment of Oracle RAC the individual RAC nodes run as VMs but share the same vSphere host.Absolute performance is not the goal of this deployment so we can take advantage of VMware’svirtualization technology to run multiple VMs on a single ESXi host and minimize the deploymenthardware and thus costs.The Dev/Test deployment architecture is shown in figure 2.Figure 2 – Deployment Architecture for a 3-Node Test and Development Oracle RAC Databasewww.tintri.com9
VMware Multi-Writer Flag and Oracle ASMVMFS is a clustered file system that disables (by default) multiple virtual machines from opening andwriting to the same virtual disk (.vmdk file). This prevents more than one virtual machine frominadvertently accessing the same .vmdk file.However, Oracle RAC requires that multiple RAC nodes be able to access and update the same virtualdisk. To that end Oracle RAC uses Oracle ASM to manage and control access to shared database filesstored on the same virtual disks. When deploying Oracle RAC we must first disable the native VMFS filelocking technology before installing and running Oracle ASM.VMware has a KB article that describes how to use the “multi-writer” flag in vSphere to disable nativeVMFS file locking and allow individual vDisks to be shared by multiple virtual machines. Use the multiwriter flag with all disks that are used with Oracle ASM and Oracle RAC. The instructions for the use ofthe “multi-writer” flag are detailed in the VMware KB article 1034165.VMware KB article 1034165 - Enabling or disabling simultaneous write protection provided byVMFS using the multi-writer flagDO: Enable the “muti-writer” flag on vDisks used with Oracle ASM and Oracle RAC.Shared Hard Disk Architecture for ASMEach Oracle RAC node connects with a set of Hard Disks that are managed by Oracle ASM. These HardDisks are shared by all of the RAC nodes in the cluster. With VMware this is accomplished by creatingHard Disks in the first Oracle RAC node, setting the multi-writer flag on these disks, and then connectingthe Hard Disks with the other RAC nodes. Figure 3 shows a simple 2 node Oracle RAC cluster thatdemonstrates the shared Hard Disk architecture. Each RAC node uses local Hard Disks for OS files and for Oracle binaries.The first RAC node contains Hard Disks that are shared with other RAC nodes. The Hard Disksand their data are stored in the Datastore folder containing the VM files for the first RAC node.The Hard Disks in the second RAC node link to the Hard Disk files stored in the first RAC node.A third RAC node would also link to the Hard Disk files stored in the first RAC node. Etc.In this deployment architecture the location of the Hard Disk Files does not affect the capabilities of theother RAC nodes. The Hard Disk files can be accessed whether the first RAC node is powered on or not.The configuration of the Oracle RAC nodes and the location of the Hard Disk files should be consideredwhen the Tintri SnapVM, CloneVM, and ReplicateVM tools are used. Details on the use of these powerfuldata management tools with Oracle RAC is discussed in another section of this document.www.tintri.com10
Figure 3 –Oracle RAC Nodes with Shared ASM DisksVMware vSphere Limitations of the Multi-Writer FlagWhen the multi-writer flag is used with vDisks in a VM several vSphere functions are disabled. ReviewVMware KB article 1034165 for a complete list of Supported and Unsupported actions or features, but beaware that the following three major vSphere functions are disabled. vSphere Snapshots (limited functionality) vSphere CloningvSphere Storage vMotionTintri VM Supports the Multi-Writer FlagWhen the multi-writer flag is used with vDisks the following Tintri VMstore functions are fully supported. SnapVM CloneVMReplicateVMDO: Use Tintri SnapVM, CloneVM, and ReplicateVM tools with Oracle RAC VMs.www.tintri.com11
Oracle ASM and the Tintri VMstoreOracle Automatic Storage Management (ASM) is a volume manager and a file system that is used withunformatted disks. Oracle recommends the use of ASM with Oracle RAC as it provides specific volumemanagement and file system functions that simplify the deployment of Oracle RAC.Oracle ASM must be able to identify individual disk devices (vDisks) via persistent device names and itrequires specific ownership and file permissions. Providing persistent device names with Linux ischallenging as the names and the discovery order of Linux device files are dynamically assigned and canchange across reboots of the server. This challenge applies to both physical and virtualized Linux.There are two methods of providing persistent device names for Linux disks. This is accomplished viaeither udev rules or via the Oracle ASMLib library. Both of these methods of managing disk devices forASM are supported for use with the Tintri VMstore.DO: Use either UDEV rules or ASMLib to identify disks used by Oracle ASM.Storage – UDEV rulesRHEL 7 native udev rules provide a reliable method for ASM to uniquely identify shared disks byreferencing the SCSI ID of the disk.Testing with Oracle RAC, RedHat Linux and the Tintri VMstore confirmed that udev rules work reliablywith vDisks that are stored on the Tintri VMstore. A copy of the udev rules that were used to test thisfunctionality are documented in Appendix B of this document.Storage – ASMLibOracle ASMLib can be used as an alternative to udev rules when managing ASM disk devices. ASMLibuniquely identifies individual vDisks by adding a disk marker (tag) to the disk and by modifying the disklabel. Note that Oracle ASM does not require ASMLib to operate and all ASM features are available withor without ASMLib.ASMLib consists of the following components. An open source (GPL) kernel module package: kmod-oracleasm An open source (GPL) utilities package: oracleasm-supportA closed source (proprietary) library package: oracleasmlibDetails on how to acquire and install ASMLib for RedHat Enterprise Linux 7 are provided at the followingRedHat support page, dated March 6, 2015.Oracle ASMLib Availability and Support for RedHat Enterprise LinuxDO: If you decide to employ ASMLib, refer to the RedHat support page for details on acquiring and installingASMLib for RedHat Enterprise Linux 7.www.tintri.com12
Deploying ASM with UDEV RulesThis section describes the steps necessary to deploy Oracle RAC on VMware with the Tintri VMstore.Note: Appendix B includes examples of the udev rules file and scsi id commands.Step 1: Create the first RAC node1.2.3.4.5.6.7.8.9.10.Create the VM and configure the network. Reference the Oracle Databases on VMware RACDeployment Guide for specific recommendations for the VM, Network, and vDisks.Create multiple Hard Disks (vDisks) for use by ASM. Use the thin Disk Provisioning option.Edit the VM Options Advanced Normal Configuration Parameters to expose the SCSI ID forall vDisks by adding the VMware option “disk.EnableUUID TRUE”.Edit the VM Options Advanced Normal Configuration Parameters and add the multi-writerflag to each ASM disk with the VMware option “scsi sharing multi-writer”. Details on setting thisoption are shown in VMware KB article 1034165. See Figure 4 for an example of theConfiguration Parameters.Note: although you can add this option using the Virtual Machine Properties dialog box, reconfirming that the option is set can require reviewing the VMX file for the VM. See Figure 5 foran example of a VMX file.Load the RHEL 7 OS. Reference the Deploying Oracle RAC Database 12c on RHEL 7 for BestPractices related to RHEL 7 and Oracle RAC.Using Linux, create a single partition on each disk. This step is required by ASM.Use the Linux command “scsi id” to capture the SCSI id of the individual disks.Create Linux udev rules in the file te “udevadm test /sys/classblock/sdc1” to confirm ID SERIAL matches the SCSI ID.Step 2: Create Additional RAC Nodes1. Use the Tintri VMstore CloneVM tool to clone the first RAC node.2. Remove and delete the ASM vDisks from the cloned VM.3. Add the ASM disks from the first RAC node to the current VM with the “Use an existing virtualdisk” option. Browse the VMstore and select the appropriate vDisk from the folder containing thefirst RAC node.4. Confirm that the option “disk.EnableUUID TRUE” is set.5. Confirm that the multi-writer flag is set for each ASM disk. Open the VMX file for the VirtualMachine and look for the “scsi sharing multi-writer” option. See Figure 5 for an example of aVMX file and the “scsi sharing multi-writer” option.6. Execute the Linux command “udevadm test /sys/classblock/sdc1” and compare the ID SERIAL ofthe shared vDisks with the SCSI ID of the vDisks on the first RAC node. Each node should havethe identical SCSI ID and UDEV results for the ASM disks.7. Repeat these steps for each new node in the RAC cluster.Step 3: Create the Oracle ASM Disk Group and RAC database1. Download the Oracle binaries.2. Create an Oracle ASM disk group.3. Create the Oracle RAC database.www.tintri.com13
Figure 4 – Configuration Parameters Showing the “multi-writer” Flag for SCSI 1:0 to 1:6Figure 5 – A VMX File Showing that the “multi-writer” Flag is Set for SCSI 1:0 to 1:6www.tintri.com14
Deploying ASM with ASMLibStep 1: Create the first RAC Node1.2.3.4.5.6.Create the VM and configure the network. Reference the Oracle Databases on VMware RACDeployment Guide for specific recommendations for the VM, Network, and vDisks.Create multiple Hard Disks (vDisks) for use by ASM. Use the thin Disk Provisioning option.Edit the VM Options Advanced Normal Configuration Parameters and add the multi-writerflag to each ASM disk with the VMware option “scsi sharing multi-writer”. Details on setting thisoption are shown in VMware KB article 1034165. See Figure 4 for an example of theConfiguration Parameters.Note: although you can add this option using the Virtual Machine Properties dialog box, reconfirming that the option is set can require reviewing the VMX file for the VM. See Figure 5 foran example of a VMX file.Load the RHEL 7 OS. Reference the Deploying Oracle RAC Database 12c on RHEL 7 for BestPractices related to RHEL 7 and Oracle RAC.Using Linux, create a single partition on each disk. This step is required by ASM.Step 2: Create Additional RAC Nodes1. Use the Tintri VMstore CloneVM tool to clone the first RAC node.2. Remove and delete the ASM vDisks from the cloned VM.3. Add the ASM disks from the first RAC node to the current VM with the “Use an existing virtualdisk” option. Browse the VMstore and select the appropriate vDisk from the folder containing thefirst RAC node.4. Confirm that the multi-writer flag is set for each ASM disk. Open the VMX file for the VirtualMachine and look for the “scsi sharing multi-writer” option. See Figure 5 for an example of aVMX file and the “scsi sharing multi-writer” option.5. Repeat these steps for each new node in the RAC cluster.Step 3: Create the Oracle ASM Disk Group and RAC database1.2.3.4.5.Download the Oracle binaries.Download ASMLib for RedHat Enterprise Linux 7.Configure the Oracle ASMLib Library Driver.Create an Oracle ASM disk group.Create the Oracle RAC database.www.tintri.com15
Oracle RAC and Tintri Data Management ToolsOracle RAC and VMware vMotionVMware vMotion can be used to move a production Oracle RAC node from one ESXi host to anotherwith no downtime. Tintri testing confirmed that Oracle RAC VMs running with a Tintri VMstore can movesuccessfully from one ESXi host to another and back again. Furthermore, there were no false RAC nodeejections nor RAC cluster fencing errors during the testing. The system was entirely stable during thevMotion tests.NOTE: while we can use vMotion to move VMs from one vSphere host to another, vCenter will preventus from executing a storage vMotion. VMware vCenter does not support storage vMotion for VMs withvDisks that have the Multi-Writer flag set to true. However, Tintri ReplicateVM can be used to replicateVMs and their vDisks to additional Tintri VMstores. Details on ReplicateVM are included in the section ofthis document titled “Oracle RAC and Tintri VM Management Tools”.Figure 6 –vMotion an Oracle RAC Node to another vSphere HostDO: Use VMware vMotion to move production Oracle RAC VMs between ESXi hosts.www.tintri.com16
Oracle RAC and Tintri VM Management ToolsWhen the multi-writer flag is used with a VM several vSphere functions are disabled, including snapshots,cloning and Storage vMotion. The Tintri VMstore does not share this limitation and we can use theVMstore management tools to provide Snapshot, Cloning and Replication for Oracle RAC nodes.It is important to understand the contents of the Oracle RAC VM when using the S
Deploying Oracle RAC Database 12c on RHEL 7 - Best Practices Oracle Databases on VMware RAC Deployment Guide VMware vSphere 6.0 Best Practices Guides VMware settings can affect the performance and scalability of your Oracle database. There is a wealth of information on VMware and Oracle performance in the VMware Best Practices guides.
TECHNICAL WHITE PAPER Hyper-V Best Practices Guide Tintri VMstore and Microsoft Hyper-V Server 2012 R2 . www.tintri.com 2 Revision History . Tintri VMstore All Flash/Hybrid System Administration Manual SCVMM & Hyper-V Setup Guide Tintri VMstore T800 and T5000 Series Reference Guides Microsoft Hyper-V Server and SCVMM Guides
www.tintri.com 8 Networking Guidelines The standard VMware networking best practices apply to running Oracle databases on vSphere. It is recommended that the Tintri VMstore be attached to the ESX Host via a 10GbE Ethernet network.
1.12 Overview of Managing Oracle RAC Environments 1-36 1.12.1 About Designing and Deploying Oracle RAC Environments 1-37 1.12.2 About Administrative Tools for Oracle RAC Environments 1-37 1.12.3 About Monitoring Oracle RAC Environments 1-39 1.12.4 About Evaluating Performance in Oracle RAC Environments 1-40 2 Administering Storage in Oracle RAC
2.4 Installing Oracle RAC and Oracle RAC One Node Databases 2-3 2.4.1 Installing Oracle RAC and Oracle RAC One Node Database Software 2-4 2.5 Simplified Upgrade of TIMESTAMP WITH TIME ZONE Data 2-5 2.6 Overview of Installation Directories for Oracle RAC 2-6 2.6.1 Overview of Oracle Base Directories 2-6 2.6.2 Overview of Oracle Home Directories 2-7
IP Fabric B Management Data Replication VM Figure 3: A logical representation of a basic networking topology for a typical data center stack comprising top to bottom; Tintri VMstore platform and associated network functions; IP switching layer with example VLAN definitions; host layer comprising hypervisor managed compute, memory & virtual .
Oracle 19c : de-support of Oracle RAC in SE2 Introduction Oracle Real Application Clusters (Oracle RAC) is the only solution to build an active – active cluster using shared storage for your Oracle database. Up to Oracle 18c Oracle RAC is available as a feature within
Oracle Database using Oracle Real Application Clusters (Oracle RAC) and Oracle Resource Management provided the first consolidation platform optimized for Oracle Database and is the MAA best practice for Oracle Database 11g. Oracle RAC enables multiple Oracle databases to be easily consolidated onto a single Oracle RAC cluster.
Alison Sutherland 579 Alison Sutherland 1030 Alison Will 1084 Alison Haskins 1376 Alison Butt 1695 Alison Haskins 1750 Alison Haskins 1909 Alison Marr 2216 Alison Leiper 2422 Alistair McLeod 1425 Allan Diack 1011 Allan Holliday 1602 Allan Maclachlan 2010 Allan Maclachlan 2064 Allan PRYOR 2161 Alys Crompton 1770 Amanda Warren 120 Amanda Jones 387 Amanda Slack 729 Amanda Slack 1552 Amanda .
