Oracle Cloud Infrastructure Documentation

Manage Resource Availability with Compartment Quotas

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

Using this feature you can restrict, on a compartment by compartment basis, the availability of the following dedicated infrastructure resources in your tenancy:

  • OCPUs available to dedicated deployments of Autonomous Data Warehouse databases.

  • ECPUs available to dedicated deployments of Autonomous Data Warehouse databases.

  • Total data storage available to dedicated deployments of Autonomous Data Warehouse databases.

  • OCPUs available to dedicated deployments of Autonomous Transaction Processing databases.

  • ECPUs available to dedicated deployments of Autonomous Transaction Processing databases.

  • Total data storage available to dedicated deployments of Autonomous Transaction Processing databases.

Note

Quotas are enforced only for provisioning databases and manually scaling their allocated CPUs 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-dedicated-ocpu-count quota to 3 OCPUs in the compartment MyCompartment : 
    set database quota atp-dedicated-ocpu-count to 3 in compartment MyCompartment
  • unset: Resets quotas back to the default service limits.
    For example, the following statement resets the quota for atp-dedicated-ocpu-count in the entire tenancy: 
    unset database quota atp-dedicated-ocpu-count in tenancy
  • zero: Removes access to a cloud resource for a compartment.
    For example, the following statement disallows use of outbound email or notifications in the compartment MyCompartment:
    Zero email-delivery quotas in compartment MyCompartment
Zero notifications quotas in compartment MyCompartment

See Sample Quotas for more such examples and Quota Policy Syntax for an explanation of the anatomy of quota statements.

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

Quotas for Autonomous Database on Oracle Public Cloud

Family name: database

Name Scope Description

adw-dedicated-ocpu-count

Availability domain

Number of Autonomous Data Warehouse OCPUs for databases using dedicated Exadata infrastructure. (See note about "n/a" values on the Limits, Quotas and Usage page of the Console.)

adw-dedicated-ecpu-count

Availability domain

Number of Autonomous Data Warehouse ECPUs for databases using dedicated Exadata infrastructure. (See note about "n/a" values on the Limits, Quotas and Usage page of the Console.)

adw-dedicated-total-storage-tb

Availability domain

Amount of storage (in TB) for Autonomous Data Warehouse databases using dedicated Exadata infrastructure. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)

atp-dedicated-ocpu-count

Availability domain

Number of Autonomous Transaction Processing OCPUs for databases using dedicated Exadata infrastructure. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)

atp-dedicated-ecpu-count

Availability domain

Number of Autonomous Transaction Processing ECPUs for databases using dedicated Exadata infrastructure. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)

atp-dedicated-total-storage-tb

Availability domain

Amount of storage (in TB) for Autonomous Transaction Processing databases using dedicated Exadata infrastructure. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)

Quotas for Autonomous Database on Exadata Cloud@Customer

Family name: database

Name Scope Description
adw-exacc-ocpu-count Availability domain Number of Autonomous Data Warehouse OCPUs for databases using Exadata Cloud@Customer. (See note about "n/a" values on the Limits, Quotas and Usage page of the Console.)
adw-exacc-ecpu-count Availability domain Number of Autonomous Data Warehouse ECPUs for databases using Exadata Cloud@Customer. (See note about "n/a" values on the Limits, Quotas and Usage page of the Console.)
adw-exacc-total-storage-tb Availability domain Amount of storage (in TB) for Autonomous Data Warehouse databases using Exadata Cloud@Customer. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)
atp-exacc-ocpu-count Availability domain Number of Autonomous Transaction Processing OCPUs for databases using Exadata Cloud@Customer. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)
atp-exacc-ecpu-count Availability domain Number of Autonomous Transaction Processing ECPUs for databases using Exadata Cloud@Customer. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)
atp-exacc-total-storage-tb Availability domain Amount of storage (in TB) for Autonomous Transaction Processing databases using Exadata Cloud@Customer. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.)