Database Reference
In-Depth Information
Partition number (1-4): 1
First cylinder (1-13054, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-13054, default 13054):
Using default value 13054
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
[root@s1 ~]#
mkfs.ext3 /dev/xvdd1
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
[root@s1 ~]#
e2label /dev/xvdd1 /u02
[root@s1 ~]#
mkdir /u02
[root@s1 ~]#
mount LABEL=/u02 /u02
A different approach needs to be taken to increase the available space in the bare metal configuration of ODA. It
utilizes Linux Logical Volume Manager (LVM) to manage the disks. The steps to adjust the configuration are outlined
in My Oracle Support note “How to customize available disk space for installing your Application on the Oracle
Database Appliance (ODA) (Doc ID 1457717.1).”
Create a Virtual Machine for the Application Tier
Before starting the installation of the e-Business Suite, you have to create one of the planned application tier
machines. The second VM will be cloned from the first one after the installation is completed. Alternatively, you may
also choose to create two VMs (once on each ODA node) and use R12.2 Rapid Install to deploy the environment using
a shared application tier file system. The example described here does not cover this scenario.
The easiest way to create the VM is to download the templates from Oracle Software Delivery Cloud.
7
I'm
using the latest available Oracle Linux 6 update 4 x86_64 templates
8
to build the VMs. Make sure to download
the paravirtualized template because it allows full use of Xen features to reduce the amount of needed hardware
virtualization.
Once the template is downloaded and uncompressed, the Oracle virtual assembly file (in my case, it's
OVM_
OL6U4_x86_64_PVM.ova
) needs to be placed in
/OVS
directory on Dom0 on the first node of the ODA, from where it
will be loaded into the OVS repository. Listing 11-7 shows the commands to import the VM template into the OVS
repository, after which the new VM is cloned from the template and sized to your needs. In the end, the new VM is
started.
Listing 11-7.
Creating the VM from Template
[root@s1 ~]#
oakcli import vmtemplate oel6u4 -assembly /OVS/OVM_OL6U4_x86_64_PVM.ova -repo odarepo1
Imported VM Template
[root@s1 ~]#
oakcli clone vm oevm1 -vmtemplate oel6u4 -repo odarepo1
Cloned VM : oevm1
8
Oracle Linux 6 Update 4 template (OVF) - Paravirtualized x86_64 (64 bit), part number V38315-01.
7
