Upscaling/resizing an OEM13C–VM in Oracle Cloud

Upscaling/resizing an OEM13C–VM in Oracle Cloud

Published on: Category: Oracle

Scaling is one of the great benefits of the Cloud: scale up when there’s a peak in workload, scale down when it’s quiet. And scaling the PaaS databases, like the autonomous database in Oracle Cloud, is just one click away, and very easy to perform. But vertical scaling (more CPU/memory on 1 VM) in IaaS, without breaking the application, needs more attention. As I understand, this will be the main new feature in Q1 2020.

Till then, you need to perform a few steps. In this post, I will describe an upscale of a VM with OEM13c in it. WebLogic and database are included in the VM.

In a former post, I created an OEM13c through the marketplace app.

In the real world, it’s more than likely that you need more CPUs or more memory. In other words, you need a change of the instance-size. To understand how this change works in Oracle cloud, you need to know what elements are involved. In a picture:

- The marketplace app created an instance of a certain size, and gave it a private IP address and name.
- A boot volume and blockvolume was also created and attached to this instance.
- I created a reserved public IP-address and also attached this to the instance.

The following steps should be taken for a scale-operation. It looks like a lot, but when you get the hang of it, it’s relatively easy to do.
1. Memorize the private IP address and name of the instance
2. Stop all software
3. Stop the instance
4. Detach blockstorage
5. Terminate the instance (!) without deleting the boot volume
6. Create instance with the old boot volume, and with the old IP and name
7. Attach blockstorage
8. Mount the blockstorage
9. Attach public IP address
10. Start the instance

1. Private IP address and name

When checking this in Linux, it looks like this:

  1. [opc@emcc ~]$ cat /etc/hosts
  2. localhost localhost.localdomain localhost4 localhost4.localdomain4
  3. ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
  4. oem13c6
  5. emcc

Although not necessary, I want to know some information about the disks (just in case…).

  1. [root@oem13c6 opc]# lsblk
  3. sdb 8:16 0 400G 0 disk
  4. └─sdb1 8:17 0 400G 0 part /u01
  5. sda 8:0 0 46.6G 0 disk
  6. ├─sda2 8:2 0 8G 0 part [SWAP]
  7. ├─sda3 8:3 0 38.4G 0 part /
  8. └─sda1 8:1 0 200M 0 part /boot/efi
  10. [root@oem13c6 opc]# blkid
  11. /dev/sdb1: UUID="0eb2f372-ee1d-47e4-bf56-5ce8110a0f21" TYPE="xfs" PARTUUID="57e88af4-f877-4757-b05b-6c25a2df7b8d"
  12. /dev/sda1: SEC_TYPE="msdos" UUID="4EAE-E92C" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="4c374dd7-f879-407c-ac2e-0154e586c082"
  13. /dev/sda2: UUID="ec49f02f-cbd9-4890-88d3-fee99c70e661" TYPE="swap" PARTUUID="d023a973-8ef5-4526-b793-f6756fa6a3c6"
  14. /dev/sda3: UUID="915fbdd1-9aba-4b6d-8714-5c28f1c31d77" TYPE="xfs" PARTUUID="e0fedb5c-f09f-4a3f-9d75-c68f6b86e30a"
  16. [root@oem13c6 opc]# cat /etc/fstab
  17. #
  18. # /etc/fstab
  19. # Created by anaconda on Thu Aug 15 02:35:23 2019
  20. #
  21. # Accessible filesystems, by reference, are maintained under '/dev/disk'
  22. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
  23. #
  24. UUID=915fbdd1-9aba-4b6d-8714-5c28f1c31d77 / xfs defaults,_netdev,_netdev 0 0
  25. UUID=4EAE-E92C /boot/efi vfat defaults,uid=0,gid=0,umask=0077,shortname=winnt,_netdev,_netdev,x-initrd.mount 0 0
  26. UUID=ec49f02f-cbd9-4890-88d3-fee99c70e661 swap swap defaults,_netdev,x-initrd.mount 0 0
  27. ######################################
  29. ##
  30. ## If you are adding an iSCSI remote block volume to this file you MUST
  31. ## include the '_netdev' mount option or your instance will become
  32. ## unavailable after the next reboot.
  33. ## SCSI device names are not stable across reboots; please use the device UUID instead of /dev path.
  34. ##
  35. ## Example:
  36. ## UUID="94c5aade-8bb1-4d55-ad0c-388bb8aa716a" /data1 xfs defaults,noatime,_netdev 0 2
  37. ##
  38. ## More information:
  39. ##
  40. UUID=0eb2f372-ee1d-47e4-bf56-5ce8110a0f21 /u01 xfs defaults,_netdev,nofail 0 2

2. Stop all software

  1. # Sudo su oracle
  2. [oracle@emcc opc]$ cd /home/oracle
  3. [oracle@emcc ~]$ ls
  4. oradiag_oracle
  6. [oracle@emcc ~]$ ./
  7. Stopping EM: Oracle Management Server, Oracle Management Agent and Oracle Database .........
  8. The command completed successfully

3. Stop de instance

Go to the instance and stop it.

4. Detach the blockstorage

It’s probably preferable to unmount the storage first. However, because the software and instance have been stopped, and the UUID of the boot and blockstorage won’t change, it should be safe to detach the blockstorage right away.

When you want to detach the block volume, you will get the commands to unmount the disks first.

5. Terminate the instance without deleting the boot volume

Important: Don’t delete the attached boot volume!

In this phase, we have no instance, but all kinds of loose stuff:

6. Create instance with the old boot volume and the old IP and name

Choose ‘create instance’. In ‘choose operating system or image source’, choose the boot volume you wish to attach to the instance.

Pick the new size:

Do not assign a public IP address.

And the most import part, in the ‘Advanced options’, the private IP address and emcc (without the addition of

Create the instance.

When created, the status is ‘running’.

At that moment, we have the following situation: An instance with a few loose ends.

7. Attach the block-storage

Now we have to mount the block-storage.

8. Mount the block-storage

Choose the three dots, and get the mount option-commands to run.

Copy and paste the commands, run as root:

  1. [opc@emcc ~]$ sudo -s
  3. [root@emcc opc]# sudo iscsiadm -m node -o new -T -p
  5. o iscsiadm -m node -o uNew iSCSI node [tcp:[hw=,ip=,net_if=,iscsi_if=default],3260,-1] added
  7. [root@emcc opc]# sudo iscsiadm -m node -o update -T -n node.startup -v automatic
  9. -p[root@emcc opc]# sudo iscsiadm -m node -T iqn.201:3260 -l.oracleiaas:a13f913b-38aa-4350-90f3-6f4185ef283c -p
  11. Logging in to [iface: default, target:, portal:,3260] (multiple)
  13. Login to [iface: default, target:, portal:,3260] successful.

9. Attach the public IP address

No more loose ends.

10. Start the software as Oracle

  1. [oracle@emcc ~]$ ./
  3. Starting EM: Oracle Database, Oracle Management Server and Oracle Management Agent .....
  5. Starting the Oracle Database and network listener
  6. …….
  7. Starting the Oracle Management Server .....
  9. Oracle Enterprise Manager Cloud Control 13c Release 3
  11. Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved.
  13. Starting Oracle Management Server...
  15. WebTier Successfully Started
  17. Oracle Management Server Successfully Started
  19. Oracle Management Server is Up
  21. JVMD Engine is Up
  23. Starting BI Publisher Server ...
  25. BI Publisher Server Successfully Started
  27. BI Publisher Server is Up
  29. Starting the Oracle Management Agent .....
  31. Oracle Enterprise Manager Cloud Control 13c Release 3
  33. Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved.
  35. Starting agent ................................................. started.

Is it working again? Yes, it is!

On the server:

  1. [oracle@emcc bin]$ ./emctl status oms
  3. Oracle Enterprise Manager Cloud Control 13c Release 3
  5. Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved.
  7. WebTier is Up
  9. Oracle Management Server is Up
  11. JVMD Engine is Up
  13. BI Publisher Server is Down


Job Oprel
About the author Job Oprel

Job Oprel is a Solution Architect working for Qualogy with special interest in HA, hybrid cloud environments and Oracle software costs. In 2020, Job was appointed Oracle ACE Associate for his contributions to the Oracle community.

More posts by Job Oprel