Oracle Cloud Infrastructure Documentation

Remove CPU or Storage Resources or Disable Auto Scaling

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 navigation icon 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.

  1. On the Details page, click Manage resource allocation.
  2. In the Manage resource allocation area, select the change in resources for your scale request:
    • Enter a value or click the down arrow to select a value for the ECPU count (OCPU count if your database uses OCPUs). The default is no change.

    • Storage: Specify the storage you wish to make available to your database. Depending on your workload type and your compute model, you have these options:

      • Data Warehouse: Specify your storage in Terabytes (TB).

      • JSON: Specify your storage in Terabytes (TB).

      • Transaction Processing: Specify your storage in Gigabytes (GB) or Terabytes (TB). Enter the size in the Storage field. Select GB or TB for the Storage unit size. GB units are only available when the Workload type is Transaction Processing and the Compute model is ECPU.

      The default is no change.

    Description of adb_scale_dialog.png follows
  3. When compute auto scaling is enabled, deselect Compute auto scaling to disable compute auto scaling.

    If compute auto scaling is disabled while more CPUs are in use than the specified ECPU count (OCPU count if your database uses OCPUs), then Autonomous Database scales the number of CPUs in use down to the ECPU count (OCPU count if your database uses OCPUs).

    See Use Auto Scaling for more information.

  4. 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.
  5. 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 when you scale down storage or change the Storage auto scaling value:

  • Scaling down storage is not allowed if the Autonomous Database instance contains the following:

    • Advanced Queuing tables

    • MEMOPTIMIZE FOR WRITE tables

  • If you have columns with the ROWID data 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

    • Nested tables

    • Object tables

    • Partitioned tables with domain indexes

  • Autonomous Database uses Exadata Smart Flash Cache to automatically cache frequently accessed data, delivering the high I/O rates and fast response times of flash. The amount of flash cache for your database depends on the amount of storage you provision, or the amount of allocated storage if you enable storage auto scaling.

    With storage auto scaling disabled, the guaranteed minimum flash cache size is 10% of your database's provisioned storage size.

    With storage auto scaling enabled, the guaranteed minimum flash cache size is 10% of your database's provisioned base storage size or its allocated storage size, whichever is higher.