Oracle DB/RAC 19c OVM Templates Oracle Linux X86 64bit

9m ago
55 Views
1 Downloads
2.21 MB
41 Pages
Last View : 5d ago
Last Download : 8m ago
Upload by : Madison Stoltz
Transcription

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19cLast Modified: 21-Apr-2021Oracle VM templates for Oracle Database – Single Instance and RealApplication Clusters 19c (19.11.0.0.210420)Oracle Linux X86 64bit (OneCommand)Table of Contents:Overview: .2Shared Disks Implementation Choices: .2Naming Convention: .2Minimum Hardware Requirements: .3Certification & Support Information .3WHAT’S NEW: .4Previous What’s New: .4Templates Description: .4Feedback: .5Deployment in an Oracle VM 3 environment.6Main steps for a Single Instance deployment, using Oracle VM Manager 2 .6Main steps for an Oracle RAC deployment, using Oracle VM Manager 2 .61) Load the template into the /OVS/seed pool directory, on DOM-0:.62.1) Create 5 shared Physical disks to hold the Database .72.2) Create 5 shared Virtual disks to hold the Database .73) Import the template (from step 1) using Oracle VM manager 2 .94) Create Virtual Machines using the imported template .125.1) Add the shared Physical disks to both VMs. .145.2) Add the shared Virtual disks to both VMs. .146.1) When complete, inspect the VM’s vm.cfg configuration files – Physical disks .176.2) Inspect the VM’s vm.cfg configuration files (Optional) – Virtual disks.177) Power ON both virtual machines.188) Complete the First Boot interview: .19Preparing for a Single Instance build .19Preparing for an Oracle RAC build .19Install Single Instance or Grid Infrastructure with Oracle RAC.22Standard Single Instance Build: .22Standard RAC Build: .22Monitoring the Build: .22APPENDIX A: Build Options .23APPENDIX B: Using More (or less) Disks .25Before the Build: .25After the build: .25APPENDIX C: Frequently Asked Questions / Troubleshooting .26Copyright Oracle Corporation 2009-20211 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19cOverview:This document introduces the Oracle VM Templates for Oracle Database. It explains the basic concepts ofthe templates and how to use the templates to deploy Single Instance, Oracle Restart (formerly known as:Single Instance/High Availability [SIHA]), or a fully functional N-node Oracle Real Application Clusters(RAC).Templates are provided in 64-bit mode only: Oracle Linux 7 Update 9 64bitFor the latest version of this document and more information on the benefits of Oracle VM and Templates,see OTN at: m-db-templates.html and Note# 1185244.1on My Oracle Support.NOTE: Oracle VM 3 users should use the deploycluster tool and documentation at the above URL toactually deploy this template. The rest of this document describes the features and options of thetemplate as well as FAQ section.Shared Disks Implementation Choices:The shared disks holding the Oracle RAC database files may be configured as ‘Physical’ or ‘Virtual’ disks.Recently Oracle RAC Support policies allow Production deployments to use Virtual disks with somecautionary provisions (See Whitepaper below for details).For more details carefully review the updated Oracle RAC on Oracle VM environments whitepaper .pdfIn Single Instance deployments Virtual Disks are a lot safer to use from a performance standpoint.Naming Convention:This document describes the x86-64 (64bit) DB/RAC OVM Templates 19c Release Update. Template file& directory names are as follows:OVM OL7U9 X86 64 19110DBRAC PVHVM: Oracle Linux 7 U9, Oracle Database 19c EnterpriseEdition as well as Standard Edition 2 (same template files support both editions).NOTE: The Oracle OneCommand DB/RAC build scripts inside the template (under /u01/racovm directory)are only supported inside the Oracle VM DB/RAC Templates. Do not modify or run them in otherenvironments.Copyright Oracle Corporation 2009-20212 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19cMinimum Hardware Requirements:The physical resources required for Single Instance and Oracle RAC 1deployments are as follows:Minimum Storage RequirementsFilesystem space consumption depends on SPARSE FILES2 support for the repository (/OVS) as well ascloning method 3in OVM3 and deployment mode4. Below are some approximations on space requirements:Under /OVS (repository):Template StorageEach node of running VMTemporary unzip Template5No Sparse file support64bitSparse file support (approx)64bit75GB75GB 13GB 13GB28GB28GB 13GB 13GBAdditional local/shared disk to hold database, minimum 5GB.Minimum CPU RequirementsEach VM requires a minimum of 1 physical core, recommended to run with 2 or more physical cores for thehosting server.Minimum Memory RequirementsDefault template memory is set to 4GB. Please follow the Oracle Database and Grid Infrastructuredocumentation for minimum memory requirements. At the time of writing minimum configurations thatwork in test environments: Single Instance: 1GB RAM, RAC: 4GB RAM.Minimum Network RequirementsNetwork Adapters: For RAC: Each guest VM requires 2 network devices, which are ‘virtualized’ from physicalcards in the hosting server, therefore a minimum of 2 physical NICS are required for the hostingserver. In the test configuration it is possible to use the templates with only 1 NIC, by assigningall guests’ NICs to the single bridge (e.g. xenbr0) OR creating a second bridge (e.g. xenbr1) on afake Dom0 NIC (eth1), also known as ‘Host-Only networking’ which would disable the livemigration option. Single Instance: One NIC is needed for the public network. Second NIC is optional.IP addresses: For RAC: 5 public and 2 private (for a 2 node cluster). If a DNS Server is used, 2 additional IPaddresses should be used to provide additional IPs for the SCAN name. Single Instance: 1 public IPCertification & Support InformationSee Note# 464754.1 on My Oracle Support for information on Certified Software on Oracle VM.1When running Oracle RAC in a production environment, none of the Oracle RAC VM guest machines can run on the sameOracle VM Server.2Oracle VM Server 3 (with OCFS2 v1.4.4) have sparse file support. Ext3/ext4 filesystem have sparse file support. NFS depends ifserver filesystem supports sparse files or not. Space consumed by sparse files varries by filesystem’s minimum allocation unitoften referred to as cluster size.3If OVM3 "thin-clone" is used, space consumed will greatly reduce since VMs are "reflinked" (OCFS2 v1.8 feature) to themaster template file and sections in the file are copied only when modified.4Post deployment it is possible to remove unused Oracle homes in Single Instance or Clusterware only deployments5Template stored in a tar.gz file inside a ZIP file hence size is listed twiceCopyright Oracle Corporation 2009-20213 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19cWHAT’S NEW: Installed latest Release Update (RU) 19c – Supports Enterprise Edition & Standard Edition 2(Oracle disk increased to 60GB)Upgraded OS to Oracle Linux 7 Update 9 with OVMAPI supportDefault kernel boot upgraded to Unbreakable Enterprise Kernel (UEK R6) 5.4.17Boots on Virtual Box with IDE or SATA disk adapters (for testing only)Support for ASM on NAS/NFS (ASM diskgroups created on top of NFS files)Support UseOMF (Oracle Managed Files) in DBCAPrevious What’s New: Automation support for 12c features:o Oracle Flex Cluster and/or Flex ASM (including add/remove N-number of Hub/Leaf nodes)o Creation/deletion of Container Database with optional N-number of Pluggable Databaseso DB Express configuration for databaseo Dedicated ASM Network Interface (1st NIC: Public, 2nd NIC: Private, 3rd NIC: ASM)o Database can be created inside an ACFS FilesystemAutomation support for Single Instance & Oracle Restart (Formerly known as Single Instance/HA)Automation support for databases on local & shared filesystemsAutomation support for Admin Managed or Policy Managed database creationo Including basic Server Pool creation (for Policy Managed)Allow multiple DNS IPs (see netconfig.txt)Add OSRevert utility: making switching rpm footprints easier ‘basic’ & ‘db-minimum' predefinedDeploycluster for OVM3 environments fully supports Single Instance modeSupport for [email protected], add or update rpms at deploy time! (see netconfig.txt)Mutli diskgroup support for ASM (see FAQ & params.ini)Support for multiplexed Controlfile & Redo logfilesTemplates are btrfs-ready (simple command to convert ext4 to btrfs filesystem, see FAQ)Templates Description:The Oracle VM Templates for Oracle Database allow building a Single Instance, Oracle Restart(Single Instance/HA), or RAC clusters of any number of nodes. The Oracle RAC 19c software includesOracle Clusterware and ASM 19c and Oracle Database 19c. In a Single Instance deployment the RACfeature is not linked into the binary and the Grid Infrastructure home may be removed for space savings.Note: The Templates include the latest OS & Oracle/RDBMS patches at time of the release. It isstrongly recommended to update to latest patches (at time of deployment or placement intoproduction usage) using standard OS/Oracle patching practices. OS updates may be obtainedfrom Unbreakable Linux Network (ULN) and RDBMS patches from Critical Patch Updates(CPU) page on OTN. Templates released since 2014 offer [email protected], see FAQ for details.The entire install is automated, with the user only providing the required input parameters (node names,IP addresses, etc.) when guests are booted. Oracle VM3 users should use the powerful Deployclustertool (downloadable from OTN with separate documentation) for fully automated deployments of eitherSingle Instance, Oracle Restart (Single Instance/HA) or Oracle RAC.Copyright Oracle Corporation 2009-20214 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c The OS image contains a minimal install of Oracle Linux. Only basic RPM packages are installed withan option to reduce the footprint further using a tool called OSRevert (see FAQ).The default root password is 'ovsroot', oracle password is ‘Ora DB4U’ and sys/system password is‘Ora DB4U’, all can be changed during the build. It is strongly advised to modify these passwords postinstall. See section deploying the templates securely for further details.The install is performed using root access. With ssh passwordless login temporarily enabled for root user.At the completion of the install (on all nodes), ssh for root will be disabled.Optionally, the entire install could be done as the Oracle user, provided that 'sudo' access is configuredon the current node only.During the installation process an Oracle Single Instance or RAC database is created. It is possible toskip this database creation and do a clusterware only install, see params.ini for various options.The OS and Oracle image disks inside the template are sparse files (non allocated space is not countedagainst filesystem), meaning the size displayed via 'ls -l' is not the actual space consumed on-disk. To seeactual space consumed use 'ls -ls'. If /OVS filesystem has no sparse-file support then both sizes will bethe same (all space is allocated upfront).Each template is delivered as 4 ZIP files ( 13GB in total size), inside each ZIP is a tar.gz (tar gzip file),with very similar sizes, hence you will need 26GB of temporary storage to fully expand each template.Feedback:Feel free to post feedback at the Oracle VM or Oracle RAC Forums on the Oracle Technology Network:Oracle tegories/oracle-vmOracle ategories/rac asm %26 clusterware installationOr contact Oracle Support.Note: When contacting Oracle Support, please supply the following log files: deploycluster*.log,buildsingle*.log, buildcluster*.log and the netconfig.ini & params.init used.NOTE: The Oracle OneCommand DB/RAC build scripts inside the template (under /u01/racovm directory)are only supported inside the Oracle VM DB/RAC Templates. Do not modify or run them in otherenvironments.Copyright Oracle Corporation 2009-20215 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19cDeployment OverviewAs mentioned above, by default, for an Oracle RAC deployment, each VM requires 2 (or more) networkadapters (NICs) as well as 5 (or more) common shared disks (using fewer disks is supported).A VM for Single Instance deployment does not need any shared disks or second NIC, simply clone a VMfrom the base template and deploy using deploycluster. You may also follow normal Oracle VMdocumentation to create the VMs for Single Instance or RAC deployment.Deployment in an Oracle VM 3 environmentOracle VM 3 users should use the deploycluster tool along with its documentation available on OTN. Thetool provides for fully automated Single Instance, Oracle Restart or Oracle RAC deployments without everlogging into any of the VMs. See the template’s README or Deploycluster documentation on how toimport this template.Main steps for a Single Instance deployment, using Oracle VM Manager 2Oracle Database Release 19c is not certified on Oracle VM 2, followings are provided foreducational/informative purposes only.A Single Instance deployment only needs a single VM, no shared disks or second interface. As such, followonly steps 1, 3, 4 (only create 1 VM), 7 and 8 in the RAC section below.Main steps for an Oracle RAC deployment, using Oracle VM Manager 2These steps are using Oracle VM Manager; however all of them could be done from the command line,using Oracle VM Command Line Interface (CLI).1) Load the template into the /OVS/seed pool directory, on DOM-0:# cd /tmp# unzip -q /tmp/p31000094 10 Linux-x86-64 1of4.zip# unzip -q /tmp/p31000094 10 Linux-x86-64 2of4.zip# unzip -q /tmp/p31000094 10 Linux-x86-64 3of4.zip# unzip -q /tmp/p31000094 10 Linux-x86-64 4of4.zip# wait# cd /OVS/seed pool# tar xzf /tmp/OVM OL7U9 X86 64 19110DBRAC PVHVM-1of2.tar.gz &# Note below 'cat' command should be all on one line# cat /tmp/OVM OL7U9 X86 64 19110DBRAC PVHVM-2of2-partA.tar.gz/tmp/OVM OL7U9 X86 64 19110DBRAC PVHVM-2of2-partB.tar.gz tar xz &# wait(When the above commands complete, the ZIP & TAR.GZ files may be deleted from /tmp)This will create the following:/OVS/seed pool/OVM OL7U9 X86 64 19110DBRAC PVHVMCopyright Oracle Corporation 2009-20216 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c - System.img (OS image file) - Oracle19110DBRAC x86 64-xvdb.img (database software image file) - vm.cfg (VM configuration file) - README.txt - These PDF documents - utils (files to help with automated network setup and build)2.1) Create 5 shared Physical disks to hold the DatabaseShared disks must be configured on DOM-0 of both OVM Servers, these should be persistently namedphysical devices (multi-pathed or not) accessible from both nodes, e.g.:lrwxrwxrwx 1 root root 4 Dec 28 01:28 /dev/racdevc1 - sdc1lrwxrwxrwx 1 root root 4 Dec 28 01:28 /dev/racdevd2 - sdd2lrwxrwxrwx 1 root root 4 Dec 28 01:28 /dev/racdeve2 - sde2lrwxrwxrwx 1 root root 4 Dec 28 01:28 /dev/racdevf4 - sdf4lrwxrwxrwx 1 root root 4 Dec 28 01:28 /dev/racdevg1 - sdg1The following symlinked devices were created with udev rules similar to this one below, on Dom0, in/etc/udev/rules.d/55-oracle-devices.rules file:KERNEL "sd*", BUS "scsi", PROGRAM "/sbin/scsi id -g -u -s %p",RESULT "360a98000686f61506434386f65663577", SYMLINK "racdevc%n", OWNER "root",GROUP "root", MODE "0640"Using SYMLINK (instead of NAME in udev rules) keeps the original kernel device names, e.g./dev/sd*. Using udev rules ensures persistent device naming across reboots. The OneCommand RAC installrequires 5 such devices, minimum size of 1024MB each (See APPENDIX C: Using More (or less) Disks).These will hold your database, size them appropriately2.2) Create 5 shared Virtual disks to hold the DatabaseUsing Oracle VM manager (or any other method) in our example they are named: ASM1, ASM2, ASM3,ASM4, ASM5, you may choose any name you wish. As this is a test environment you can use files visiblein the Dom-0 environment to represent the shared disks. Select Resources- Shared Virtual DisksClick the Create button:Copyright Oracle Corporation 2009-20217 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c Complete the fields on the form Click Next and Confirm on the following page.Repeat this step to create a total of 5 shared disks (Minimum size for each disk is 1024 MB) When done creating all devices will have an Active status:Copyright Oracle Corporation 2009-20218 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c3) Import the template (from step 1) using Oracle VM manager 2Make sure all unzipping/untarring operations completed before proceeding with these steps. Click Resources - Virtual Machine TemplatesClick Import buttonThis Oracle VM manager already knows about 2 existing templates. We are going to add a 3rdtemplate. Select “Select from Server Pool (Discover and register)”, click NextCopyright Oracle Corporation 2009-20219 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c Pull-down the correct “Server Pool Name”Choose the newly untarred template from pull-down “Virtual Machine Template Name”.Select “Oracle Enterprise Linux 5” or “Oracle Enterprise Linux 5 64-bit” for “Operating System”.Optionally enter Description or change username/passwordsClick Next and Confirm on the following page. Template name might be different in screenshot based on release usedWait for VM template to change from “Importing” to “Pending” then proceedSelect Pending VM template from radio box, and Click Approve buttonCopyright Oracle Corporation 2009-202110 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c Template name might be different in screenshot based on release used Click Approve Template name might be different in screenshot based on release usedThe VM Template is now imported and ready to be deployed as many times as needed.Copyright Oracle Corporation 2009-202111 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c4) Create Virtual Machines using the imported templateIn our example we name the VMs racnode1 & racnode2, you may choose any name you wish. For SingleInstance or Oracle Restart (SIHA) deployment a single VM is needed.IMPORTANT – The only non-default item you will need is to change the second NIC to xenbr1 (thefirst NIIC on xenbr0 will automatically be configured, see following page) Select Virtual machinesClick on the Create Virtual Machine button Select the “Create virtual machine based on template” radio buttonClick Next, and select the correct Server Pool on the following page.Copyright Oracle Corporation 2009-202112 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c Select the newly imported template (32bit or 64bit)Click NextNote: Template name might be different in screenshot based on release used IMPORTANT: Assign the second network adapter to xenbr1Enter the Virtual Machine Name: racnode1 (or racnode2 for second node)Enter the password twice – this will be the VNC password for the consoleClick Next and Confirm on the following page.The VM will be built – This will take some time. Repeat this step for the second node.* Do not power up the VMs yetCopyright Oracle Corporation 2009-202113 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c5.1) Add the shared Physical disks to both VMs.Edit the vm.cfg for both VM’s. These can be found on the Oracle VM Server in/OVS/running pool/*racnode1/vm.cfg and /OVS/running pool/*racnode2/vm.cfg, cdevf4,xvdf,w!','phy:/dev/racdevg1,xvdg,w!',to the ‘disk’ section, see below for sample vm.cfg.The OneCommand for Oracle VM build engine, Clusterware, Oracle RAC or ASM do not require that diskshave identical names or ordering on all nodes, however, it might be easier for humans to deal with identicalnames and ordering. Therefore it is recommended to add disks in same order with same disk names to allVMs.5.2) Add the shared Virtual disks to both VMs. Select the Virtual machines tabSelect the radio button for the first guest & Click the Configure button Select the Storage tabClick the Attach/Detach Shared Virtual Disk buttonCopyright Oracle Corporation 2009-202114 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19cThe OneCommand for Oracle VM build engine, Oracle RAC or ASM do not require that disks haveidentical names or ordering on all nodes, however, it might be easier for humans to deal with identicalnames and ordering. Therefore it is recommended to add disks in same order with same disk names toall VMs, e.g.; ASM1, ASM2, ASM3, ASM4, ASM5. Move at least 5 shared disks to the guest VM by clicking the appropriate Move buttons Click the OK buttonCopyright Oracle Corporation 2009-202115 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c Notice disk names: xvdc, xvdd, xvde, xvdf, xvdg. The automated Oracle RAC installprocess inside the templates depends on these exact device names. It is possible to use anydisk names, see Appendix C: Using More Disks. Repeat the attach steps for the second virtual machine in the clusterCopyright Oracle Corporation 2009-202116 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c6.1) When complete, inspect the VM’s vm.cfg configuration files – Physical disksThese can be found on the Oracle VM Server in /OVS/running pool/*racnode1/vm.cfg and/OVS/running pool/*racnode2/vm.cfg. You should see the 5 shared disks which will be presented to theguests as /dev/xvdc /dev/xvdd /dev/xvde /dev/xvdf /dev/xvdg. They can be in any order on both nodes asdescribed in the previous section. You should also be able to spot the 2 NICs, xenbr0 and xenbr1. This is asample vm.cfg file:bootloader '/usr/bin/pygrub'disk ['file:/OVS/running pool/3 racnode1/System.img,xvda,w','file:/OVS/running pool/3 racnode1/Oracle12102RAC x86 ,xvdg,w!',]memory '2048'name '3 racnode1'on crash 'restart'on reboot 'restart'uuid 'd98efba4-7445-8459-9326-adae28249200'vcpus 2vfb ['type vnc,vncunused 1,vnclisten 0.0.0.0,vncpasswd oracle']vif ['bridge xenbr0,mac 00:16:3E:5C:AE:24,type netfront','bridge xenbr1,mac 00:16:3E:24:D3:34,type netfront',]vif other config []If anything needs to change, use Oracle VM Manager to do so. Editing the file manually may put the repository out of sync.6.2) Inspect the VM’s vm.cfg configuration files (Optional) – Virtual disksThese can be found on the Oracle VM Server in /OVS/running pool/*racnode1/vm.cfg and/OVS/running pool/*racnode2/vm.cfg. You should see the 5 shared disks which will be presented to theguests as /dev/xvdc /dev/xvdd /dev/xvde /dev/xvdf /dev/xvdg. They can be in any order on both nodes asdescribed in the previous section. You should also be able to spot the 2 NICs, xenbr0 and xenbr1. This is asample vm.cfg file:bootloader '/usr/bin/pygrub'disk ['file:/OVS/running pool/3 racnode1/System.img,xvda,w','file:/OVS/running pool/3 racnode1/Oracle12102RAC x86 k/ASM5.img,xvdg,w!',]memory '2048'name '3 racnode1'on crash 'restart'on reboot 'restart'uuid 'd98efba4-7445-8459-9326-adae28249200'vcpus 2vfb ['type vnc,vncunused 1,vnclisten 0.0.0.0,vncpasswd oracle']vif ['bridge xenbr0,mac 00:16:3E:5C:AE:24,type netfront',Copyright Oracle Corporation 2009-202117 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19c'bridge xenbr1,mac 00:16:3E:24:D3:34,type netfront',]vif other config []If anything needs to change, use Oracle VM Manager to do so. Editing the file manually may put the repository out of sync7) Power ON both virtual machines Select the Virtual Machines tabSelect the radio button for the first nodeClick the Power On button, repeat for second node (Single Instance just start the single VM) If the VNC plugin has been configured for Oracle VM manager you can connect to the console byselecting the radio button next to the node and clicking the Console button. Open both consoles.Copyright Oracle Corporation 2009-202118 of 41

Oracle VM Templates for Oracle Database - Single Instance and Real Application Clusters 19cAlternatively, use vncviewer from any PC; First get the ports from Dom0:Dom0 # xm listName3 racnode14 (s)72.468.1Dom0 # xm list -l VM-full name or ID grep locationUse the port that appears on line as “location 0.0.0.0:5901” e.g.: vncviewer ovm server host :5901 (substitute your OVM Server node name)A third alternative, for advanced users is described inError! Reference source not found.8) Complete the First Boot interview:First Boot is the time when a newly instantiated Guest VM is started for the first time.At this point in time the guest machines are identical – they have no personality e.g. no hostname, no IPaddress etc. First boot adds this personality.The deploycluster tool available on OTN for Oracle VM 3 environments can easily send the completenetwork and build information to the VMs to quickly deploy a fully functional Single Instance or RACenvironment. Oracle VM 2 users may use the traditional 2-node interview shown below, simply type yes atthe only required key/question during first boot console n-console''Do you want to access the 2-node RAC interview on console ? [YES NO]Preparing for a Single Instance buildOracle VM 2 users deploying Single Instance, should type OUT (at the above question) and setup a simplefile called netconfig.ini based on the sample/provided netconfig-sample-si.ini to include only PublicName/IP of one VM, Public Adapter/Mask and optionally DNSIP, DOMAINNAME and PUBGW (PublicGateway). Set either CLONE SINGLEINSTANCE yes (for Single Instance) orCLONE SINGLEINSTANCE HA yes (for Oracle Restart, aka SIHA), if both are omitted then a RACdeplyoment is assumed. Once that file is ready, simply type:# /u01/racovm/netconfig.sh -n1Then skip to next section for running buildsingle.sh.Preparing for an Oracle RAC buildThe following is displayed on the console of both guests. You must identify which node is going to be themaster; the interactive interview will run o

Apr 21, 2021 · This document introduces the Oracle VM Templates for Oracle Database . It explains the basic concepts of the templates and how to use the templates to deploy Single Instance , Oracle Restart (formerly known as: Single Instance/High Availability [SIHA]), or a fully functional N-node Oracle Real Application Clusters (RAC).