Oracle Exadata VM Cluster compute resources can be scaled down to zero OCPUs when the objective is to suspend compute consumption without deleting the VM Cluster definition or its persistent database storage. Oracle explicitly notes that simply stopping VMs does not stop the relevant compute billing; to stop VM Cluster compute-related billing, the enabled OCPU—or ECPU on applicable generations—allocation must be reduced to zero.
At zero enabled compute, the guest VMs are shut down while the infrastructure configuration and persistent database storage remain available. The administrator can later restore service by scaling the enabled compute allocation back above zero. This makes the feature useful for development, testing, seasonal, or otherwise intermittent environments where deleting and recreating the database environment would be operationally undesirable.
Values of one, two, or four OCPUs still represent allocated active compute and therefore do not achieve the requested zero-compute billing state.
On Exascale Infrastructure, Oracle documents the equivalent ECPU behavior explicitly: enabled ECPUs can be scaled to zero, shutting down VM Cluster VMs and stopping enabled-ECPU usage billing.
Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — VM Cluster scaling, OCPU/ECPU allocation and cost control.
===============
Submit