Overview:
- With multiple VMs per Exadata Infrastructure feature release, you can scale up or down the following resources on the VM cluster:
- Local storage /u02. Scaling memory requires a rolling restart of the cluster nodes to take effect
- Memory. Scaling memory requires a rolling restart of the cluster nodes to take effect
- OCPU. Scaling OPCU is Online
- Exadata storage. Scaling OPCU is Online
- You specify how much space is provisioned from local storage to each VM
- This space is mounted at location /u02, and is used primarily for Oracle Database homes
- The minimum supported size of /u02 is 60 GB per VM
- The maximum supported size of /u02 is 900 GB per VM. Depending on the number of other VMs in the system and the space consumed by those VMs
- A rolling restart of each VM is required to resize /u02
In this blog, I’ll demonstrate the steps to scale up local file system size using the OCI console.
Steps to Scale Up VM Cluster Local File System Size
1. Sign in to your OCI tenancy where your Exadata Database Service on Cloud @ Customer system is deployed
2. Navigate to “Oracle Database” > “Oracle Exadata Database Service on Cloud@Customer” > “Exadata VM Clusters“
3. Click on your VM cluster name.
4. On the VM cluster details home page, click the “Scale VM Resources” button
5. On the “Scale VM Cluster” screen, under the “Resource allocation per VM” section, enter the local file system size per VM then click the “Save Changes” button
You can track scaling progress and activities from the “Work Requests” page under the Resources section on the VM cluster details home page.
Once scaling is completed, the cluster’s state will be changed back to “AVAILABLE”. Under the “Resource allocation” section, Local Storage (GB) will show the new total size for the cluster.
Also, you can confirm the new size from the VM node by running the df -h command.
Want to find out more about how you can get the best out of Oracle?
Get in touch with DSP-Eclipsys today to explore better solutions for your business.
