Describes how to scale your Autonomous Database on demand by removing CPU cores or storage. Also describes how to disable auto scaling.
Perform the following prerequisite steps as necessary:
Open the Oracle Cloud Infrastructure Console by clicking the next to Oracle Cloud.
- From the Oracle Cloud Infrastructure left navigation menu click Oracle Database and then, depending on your workload click one of: Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
On the Autonomous Databases page select an Autonomous Database from the links under the Display Name column.
- On the Details page, click Manage Scaling.
- In the Manage scaling area, select the change in
resources for your scale request:
- Enter a value or click the down arrow to select a value for OCPU count. The default is no change.
- Enter a value or click the down arrow to select a value for Storage (TB). The default is no change.
- When OCPU auto scaling is enabled, deselect OCPU auto
scaling to disable OCPU auto scaling.
If OCPU auto scaling is disabled while more OCPUs are in use than the specified OCPU count, then Autonomous Database scales the number of OCPU cores in use down to the OCPU count number.
See Use Auto Scaling for more information.
- When Storage auto scaling is enabled, deselect Storage auto
scaling to disable storage auto scaling.
If you disable Storage auto scaling and the used storage is greater than the reserved base storage, as specified by the storage shown in the Storage field on the Oracle Cloud Infrastructure Console, Autonomous Database shows a warning on the disable storage auto scaling confirmation dialog. The warning lets you know that the reserved base storage value will be increased to the nearest TB greater than the actual storage usage, and shows the new reserved base storage value.
See Use Auto Scaling for more information.Note
Clicking Shrink initiates the Shrink storage operation. See Shrink Storage for more information.
- Click Apply to change your resources.
When you click Apply with a resource change, the Lifecycle State changes to Scaling in Progress.... After the Lifecycle State changes to Available the changes apply immediately.
Note the following restrictions for scaling down storage:
Scaling down storage is not allowed if the Autonomous Database instance contains either of the following:
Advanced Queuing tables
If you have columns with the
ROWIDdata type, the
ROWIDs that these column values point to may change during the scale down storage operation.
Tables that contain the following may be moved offline during a scale down operation. DML operations on these tables may be blocked for the duration of the move and the table indexes for these tables may become unusable until the scale down operation completes:
Tables with bitmap join indexes
Partitioned tables with domain indexes