Manage Resource Availability with Compartment Quotas

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

Compartment quotas give tenant and compartment administrators greater control over resource consumption in Oracle Cloud Infrastructure. Administrators can use the Console to allocate resources to compartments. Along with compartment budgets, compartment quotas provide tools for managing spending in Oracle Cloud Infrastructure tenancies. You can start using compartment quotas from any compartment detail page in the Console.

In addition to administrator-controlled compartment quotas, Oracle sets tenancy service limits when a tenancy is created. For information about service limits and budgets, see:

• Limits by Service: Review limits for specific services in Oracle Cloud Infrastructure.
• Budgets: Set soft limits on Oracle Cloud Infrastructure spending and configure alerts when spending approaches the budget.
• Viewing a Tenancy’s Limits and Usage: View the limits and usage for a tenancy.
• Creating a Limit Increase Request: Request an increase to a service limit.

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

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

• Number of Autonomous AI Database for Developers databases.

• OCPUs available to Autonomous AI Lakehouse, Transaction Processing, JSON, or APEX databases.

• ECPUs available to Autonomous AI Lakehouse, Transaction Processing, JSON, or APEX databases.

• Total data storage available to Autonomous AI Lakehouse, Transaction Processing, JSON, or APEX databases.

Note

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 AI Database

The following table lists the quotas for Oracle Autonomous AI Database.

The family name associated with these quota names is: database

For example:

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