Oracle Cloud Infrastructure Documentation

Manage Resource Availability with Compartment Quotas

Autonomous Database supports the compartment quotas feature of Oracle Cloud Infrastructure.

Compartment quotas give tenant and compartment administrators better control over how resources are consumed in Oracle Cloud Infrastructure, enabling administrators to easily allocate resources to compartments using the Console. Along with compartment budgets, compartment quotas create a powerful toolset to manage your spending in Oracle Cloud Infrastructure tenancies. You can start using compartment quotas from any compartment detail page in the Console.

Compartment quotas are similar to service limits. The biggest difference is that service limits are set by Oracle, and compartment quotas are set by administrators, using policies that allow them to allocate resources with a high level of flexibility.

Using compartment quotas, you can restrict, on a compartment by compartment basis, the availability of the following Autonomous Database resources in your tenancy:

  • Number of Always Free Autonomous Databases. Tenancies can have a total of two Always Free Autonomous Databases, and these resources must be provisioned in the home region.

  • Number of Autonomous Database for Developers databases.

  • OCPUs available to Data Warehouse, Transaction Processing, JSON, or APEX databases.

  • ECPUs available to Data Warehouse, Transaction Processing, JSON, or APEX databases.

  • Total data storage available to Data Warehouse, Transaction Processing, JSON, or APEX databases.

Note

Quotas are enforced only for provisioning databases and manually scaling their allocated ECPUs, OCPUs, or storage up or down.
You can manage the compartment quotas to limit the availability of a given resource in a given compartment using the set, unset and zero policy statements. These policy statements are written in a simple declarative language that is similar to the IAM policy language.
  • set: Sets the maximum number of cloud resources that can be used for a compartment.
    For example, the following statement sets atp-ecpu-count quota to 10 ECPUs in the compartment MyCompartment: 
    set database quota atp-ecpu-count to 10 in compartment MyCompartment
  • unset: Resets quotas back to the default service limits.
    For example, the following statement resets the quota for atp-ecpu-count in the entire tenancy: 
    unset database quota atp-ecpu-count in tenancy
  • zero: Removes access to a cloud resource for a compartment.
    For example, the following statement disallows use of ECPUs for APEX workload databases in the compartment MyCompartment:
    Zero apex-ecpu-count quotas in compartment MyCompartment

See Compartment Quotas for more information.

Compartment quotas are available on the OCI Console's Limits, Quotas and Usage page, which you can use to automatically generate quota statements. To access this page, on the Governance & Administration page, under Tenancy Management select Limits, Quotas and Usage. As a prerequisite, ensure you have the appropriate permissions to create quotas. See Policy Reference for the Quotas Service for more details.

Quotas for Oracle Autonomous Database

The following table lists the quotas for Oracle Autonomous Database

The family name associated with these quota names is: database

For example:

set database quota atp-ecpu-count to 10 in compartment MyCompartment
Name Scope Description

adb-developer-count

Regional

Number of Autonomous Database for Developers instances.

adb-free-count

Regional

Number of Always Free Autonomous Databases. Tenancies can have a total of two Always Free Autonomous Databases, and these resources must be provisioned in the home region. For each database, you can choose the workload type.

adw-ecpu-count

Regional

Number of Autonomous Databases for Analytics and Data Warehousing ECPUs for databases using Autonomous Database Serverless.
adw-ocpu-count

Regional

Number of Autonomous Databases for Analytics and Data Warehousing OCPUs for databases using Autonomous Database Serverless.

adw-total-storage-tb

Regional

Amount of storage (in TB) for Autonomous Database for Analytics and Data Warehousing databases using Autonomous Database Serverless.

ajd-ecpu-count

Regional

Number of JSON Database ECPUs with Autonomous Database Serverless.
atp-ocpu-count

Regional

Number of JSON Database OCPUs with Autonomous Database Serverless.

ajd-total-storage-tb

Regional

Total amount of storage (in TB) for JSON Database with Autonomous Database Serverless.

apex-ecpu-count

Regional

Number of APEX ECPUs with Autonomous Database Serverless.
apex-ocpu-count

Regional

Number of APEX OCPUs with Autonomous Database Serverless.

apex-total-storage-tb

Regional

Total amount of storage (in TB) for APEX with Autonomous Database Serverless.

atp-ecpu-count

Regional

Number of Autonomous Database for Autonomous Transaction Processing ECPUs for databases using Autonomous Database Serverless.
atp-ocpu-count

Regional

Number of Autonomous Database for Autonomous Transaction Processing OCPUs for databases using Autonomous Database Serverless.

atp-total-storage-tb

Regional

Amount of storage (in TB) for Autonomous Transaction Processing databases using Autonomous Database Serverless.

ex-cdb-count

Regional

External Container Database Count
ex-non-cdb-count

Regional

External Non Container Database Count
ex-pdb-count

Regional

External Pluggable Database Count

Parent topic: Manage the Service