Database Reference
In-Depth Information
many limitations in the virtualization options that you have to be aware of before deciding to use ODA for application
tier VMs. These are the limitations that make the deployment of e-Business Suite on ODA more complicated:
Virtual disk images can be stored on the ODA server nodes' system disks only, because the
built-in Oracle VM Server (OVS) Repository is located there. The problem is that it's based
on two RAID 1 hot swappable disks that provide 250G of space on the original ODA and
300G of space on X3-2. It might be possible to move the virtual disk images to NFS storage by
customizing the VM configuration files to get a better performance from the external NFS;
however, your goal here is to deploy e-Business Suite fully on ODA. Therefore, you're leaving
the system disks in the original OVS repository location and you're mounting the ACFS
volumes on the Application tier VMs to provide a shared storage file system for
e-Business Suite.
Virtual machines can be created from VM templates only. Oracle Appliance Kit Command
Line Interface ( oakcli ) does not provide a way to install a VM from an installation media (DVD
or CD, or their images). This means you have to use the available VM templates or assemblies
from Oracle Software Delivery Cloud. Alternatively, it's also possible to build and use your
own VM templates using the Oracle VM Template Builder in case you have access to Oracle
virtualization platform elsewhere.
There is no native load balancing solution available for virtual machines on ODA. And it's
not possible to migrate VMs from one ODA node to another, which introduces additional
availability constraints that need to be worked around. You'll use two application tier VMs
configured with Linux keepalived to add an additional virtual IP address with a failover
functionality for user connections to the e-Business Suite front-end services.
Configure the Local File System on the Database Server
The fresh installation process of R12.2 does not support installation to the ODA's ASM disk groups because of their
database compatibility settings, so there's no other choice but installing the database on a file system. The e-Business
Database tier requires 90G of disk space. The installation media downloaded from Oracle Software Delivery Cloud
requires 25G 6 and the unpacked staging area for R12.2 installation requires another 25G. All summed up, it's 140G.
Listing 11-2 shows a typical sizing of ODA Base file systems. It's clear there's not enough free space for a fresh
installation.
Listing 11-2. Sizing of ODA Base File Systems
[root@s1 ~]# df -hP
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 55G 17G 36G 32% /
/dev/xvda1 91M 40M 47M 46% /boot
/dev/xvdb1 92G 26G 62G 30% /u01
tmpfs 40G 606M 39G 2% /dev/shm
/dev/asm/acfsvol-352 50G 166M 50G 1% /cloudfs
Additional free space is available on the /OVS file system on the management domain (Dom0) of the
virtualized ODA. It's been reserved here for future use by VMs, as displayed in Listing 11-3. Note the available 202G of
disk space in /OVS .
6 The figures are calculated by downloading only the files needed for fresh installation. Files required for installation of the Vision
database are not included.
 
Search WWH ::




Custom Search