Resizing database node VMs may be needed for performance or cost reasons. Resizing can be done for one node at a time without causing database downtime.
To resize database node VMs in a running cluster repeat the following steps on each database node, one node at a time
-
Update SGA and PGA sizing parameters for the databases according to the new VM memory size
-
If using HugePages then update the
vm.nr_hugepages
parameter in/etc/sysctl.conf
according to the new VM memory size -
Make sure there are no other nodes that are in offline or re-syncing state. All disk groups must have zero offline disks and Resync = No:
# flashgrid-cluster
-
Stop all local database instances running on the node.
-
Stop Oracle CRS on the node:
# crsctl stop crs
-
Stop the FlashGrid Storage Fabric services on the node:
# flashgrid-node stop
-
Stop the VM using GCP console
-
Resize the VM using GCP console
-
Start the VM using GCP console
-
Wait until all disks are back online and resyncing operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No.
# flashgrid-cluster
-
Start all database instances on the node
- Proceed to the next node