I have seen more Oracle customer adopting virtualized platform in Oracle Exadata. At the same time, I hear concerns regarding virtualization on Exa would be new and it could be buggy, could not be well documented and well tested compare with Bate-Metal install. All these provide me a motivation to publish some posts regarding real experience in this platform.
Here is the first post :
If you are one of the Oracle customer with a virtualized Exadata, you may notice that the available local space in each DomU may not be sufficient to for various things which you may do such as Grid software, multiple Oracle software, 3rd party monitoring, backup agents and etc.
Also you may notice that there is no full step by step document on how to add more space to local space in DomU.
This post is to share my experience with performing this task and walk you through step by step :
Step 1 : List existing disks and find out available disk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 25G 0 disk
xvdb 202:16 0 50G 0 disk /u01/app/18.104.22.168/grid
xvdc 202:32 0 50G 0 disk /u01/app/oracle/product/22.214.171.124/dbhome_1
xvdd 202:48 0 58G 0 disk
sda 8:0 0 128M 0 disk
sdb 8:16 0 128M 0 disk
sdc 8:32 0 128M 0 disk
I will use xvde (the next available) as new disk
Step 2 : Prepare new 20GB file
All VM guest physical files are in Dom0 under /EXAVMIMAGES/GuestImages. The new file is named db126.96.36.199.160719-3-2ndHome.img
b0c2dd2ee4b14f6cabe0b546b930b6e8 is uuid for VM and 666a1ab9604e4e3d95bbdfce30d0b739 is uuid for the new disk. These two uuids establish the new disk location. In my example, it would be such as below :