Database Quotas
Database quota details.
Family name: database
|
Name |
Scope |
Description |
|---|---|---|
| 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 (Autonomous Database for Transaction Processing and Mixed Workloads or Autonomous Database for Analytics and Data Warehousing). |
| adw-dedicated-ocpu-count | Availability domain | Number of Autonomous Database for Analytics and Data Warehousing 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 Database for Analytics and Data Warehousing 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 Database for Analytics and Data Warehousing 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 Database for Transaction Processing and Mixed Workloads 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 Database for Transaction Processing and Mixed Workloads ECPUs for databases using dedicated Exadata infrastructure. (See note 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 Database for Transaction Processing and Mixed Workloads databases using dedicated Exadata infrastructure. (See note following this table about "n/a" values on the Limits, Quotas and Usage page of the Console.) |
| adw-ocpu-count | Regional | Number of Autonomous Database for Analytics and Data Warehousing OCPUs for databases using Autonomous Database Serverless. |
| adw-ecpu-count | Regional | Number of Autonomous Database for Analytics and Data Warehousing ECPUs 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. |
| atp-ocpu-count | Regional | Number of Autonomous Database for Transaction Processing and Mixed Workloads OCPUs for databases using Autonomous Database Serverless. |
| atp-ecpu-count | Regional | Number of Autonomous Database for Transaction Processing and Mixed Workloads ECPUs for databases using Autonomous Database Serverless. |
| atp-total-storage-tb | Regional | Amount of storage (in TB) for Autonomous Database for Transaction Processing and Mixed Workloads databases using Autonomous Database Serverless. |
| bm-dense-io1-36-count | Availability domain |
Number of BM.DenseIO1.36 DB systems |
| bm-dense-io2-52-count | Availability domain | Number of BM.DenseIO2.52 DB systems |
| exadata-base-48-count | Availability domain | Number of Exadata.Base.48 DB systems |
| exadata-full1-336-x6-count | Availability domain | Number of Exadata.Full1.336 - X6 DB systems |
| exadata-full2-368-x7-count | Availability domain |
Number of Exadata.Full2.368 - X7 DB systems and Autonomous Exadata Infrastructure |
| exadata-half1-168-x6-count | Availability domain | Number of Exadata.Half1.168 - X6 DB systems |
| exadata-half2-184-x7-count | Availability domain |
Number of Exadata.Half2.184 - X7 DB systems and Autonomous Exadata Infrastructure |
| exadata-quarter1-84-x6-count | Availability domain | Number of Exadata.Quarter1.84 - X6 DB systems |
| exadata-quarter2-92-x7-count | Availability domain |
Number of Exadata.Quarter2.92 - X7 DB systems and Autonomous Exadata Infrastructure |
| vm-block-storage-gb | Availability domain | Total size of block storage attachments across all virtual machine DB systems, in GB |
| vm-standard1-ocpu-count | Availability domain | Number of VM.Standard1.x OCPUs for the Intel X7 processor (fixed shape) based DB systems in the Oracle Base Database Service |
| vm-standard2-ocpu-count | Availability domain | Number of VM.Standard2.x OCPUs for the Intel X7 processor (fixed shape) based DB systems in the Oracle Base Database Service |
| vm-standard3-ocpu-count | Availability domain | Number of VM.Standard3.Flex OCPUs for the Intel X9 processor (flexible shape) based DB systems in the Oracle Base Database Service |
| vm-standard-a1-ocpu-count | Availability domain | Number of VM.Standard.A1.Flex OCPUs for the Arm-based Ampere A1 processor (flexible shape) based DB systems in the Oracle Base Database Service |
| vm-standard-e4-ocpu-count | Availability domain | Number of VM.Standard.E4.flex OCPUs for the AMD processor (flexible shape) based DB systems in the Oracle Base Database Service |
When viewing the Limits, Quotas and Usage page of the Console, you will see the value "n/a" in the Service Limit column for storage and OCPU resources related to Autonomous Database for Transaction Processing and Mixed Workloads and Autonomous Database for Analytics and Data Warehousing with dedicated Exadata infrastructure. You might also see this value in the Available column for these resources. This is because limits for these resources are based on the capacity of your provisioned Exadata hardware, and are not service limits controlled by Oracle Cloud Infrastructure. If you define compartment quota policies for either of these resources, the Available column will display a value for the amount that is available to be allocated, based on your existing usage in the Exadata hardware.
For information about shapes that are not listed, including non-metered shapes, contact Oracle Support.
Examples
The following example shows how to limit the number of Autonomous Data Warehouse resources in a compartment:
#Limits the Autonomous Data Warehouse CPU core count to 2 in the MyCompartment compartment
set database quota adw-ocpu-count to 2 in compartment MyCompartment
This example shows how to set a quota for OCPU cores in an Autonomous Database for Analytics and Data Warehousing with dedicated Exadata infrastructure:
#Limits the number of Autonomous Data Warehouse dedicated Exadata infrastructure OCPUs to 20 in the MyCompartment compartment
set database quota adw-dedicated-ocpu-count to 20 in compartment MyCompartment
This example shows how to set a quota for Autonomous Exadata Infrastructure quarter rack resources in a compartment:
#Limits the usage of Exadata.Quarter2.92 X7 shapes to 1 in the MyCompartment compartment
set database quota exadata-quarter2-92-x7-count to 1 in compartment MyCompartment
To limit the number of virtual machine DB systems in a compartment, you must set a quota for the number of CPU cores and a separate quota for the block storage:
#Sets a quota for virtual machine Standard Edition OCPUs to 2 in the MyCompartment compartment
set database quota vm-standard1-ocpu-count to 2 in compartment MyCompartment
#Sets the virtual machine DB system block storage quota to 1024 GB in the same compartment
set database quota vm-block-storage-gb to 1024 in compartment MyCompartmentThe following example shows how to prevent the usage of all database resources in the tenancy except for two Exadata full rack X7 resources in a specified compartment:
zero database quotas in tenancy
set database quota exadata-full2-368-x7-count to 2 in compartment MyCompartmentThis example of nested quotas shows how to distribute limits for a resource type in a compartment among its subcompartments:
#Allows usage of 3 Autonomous Data Warehouse OCPUs in parent compartment Compartment1
set database quota adw-ocpu-count to 3 in compartment Compartment1
#Allows usage of 1 Autonomous Data Warehouse OCPU in child compartment Compartment1.1
set database quota adw-ocpu-count to 1 in compartment Compartment1.1
#Allows usage of 2 Autonomous Data Warehouse OCPUs in child compartment Compartment1.2
set database quota adw-ocpu-count to 2 in compartment Compartment1.2