This page provides information about the Oracle Database@Google Cloud quotas and limits. Quotas are applied at a project level, and limits are applied to the instance or to the project, depending on the limit.
Required permissions to check and edit quotas
To view your quotas, you must have the serviceusage.quotas.get
Identity and Access Management (IAM) permission.
To change your quotas, you must have the
serviceusage.quotas.update
IAM permission. This permission is included by default for the
following predefined roles: Owner, Editor, and
Quota Administrator.
Both these permissions are included by default in the basic IAM roles Owner and Editor, and in the predefined Quota Administrator role.
Check your quotas
You can check the current quotas for resources in your project using the Google Cloud console. To check your quotas, complete the following steps:
In the filter section, in the Enter property name or value field, enter the product name: Oracle Database@Google Cloud, then press enter to filter.
The quotas are shown in the Results pane. These quotas only apply to API calls.
Increase your quotas
As your use of Oracle Database@Google Cloud resources expands over time, your quotas can increase accordingly. If you expect a notable upcoming increase in usage, then make your request a few days in advance to ensure that your quotas are adequately sized.
There's no charge for requesting a quota increase. Your costs increase only if you use more resources.
To increase your quotas, follow these steps:
Go to the Quotas page.
Select the checkboxes next to the quotas that you want to change, and then click Edit quotas.
In the Quota changes window, for each quota that you selected, in the New limit field, enter the value for the new limit.
Click Done, then Submit Request.
Quota requirements
Based on the Oracle Database@Google Cloud resource you're using, there are minimum requirements for quotas.
Exadata Database Service
The following table show the minimum requirements for a VM Cluster:
| Value | Minimum requirement |
|---|---|
| Interconnect attachments | 4 per VPC per region |
| Cloud Router | 1 per VPC per region |
| Internal CIDR range | 2 per VPC per region (1 for the client subnet CIDR per VPC 1 for the backup subnet CIDR per VPC) |
| DNS zone | 1 per client subnet CIDR and 1 per backup subnet |
Autonomous Database Service
The following table show the minimum requirements for an Autonomous Database:
| Value | Minimum requirement |
|---|---|
| Interconnect attachments | 4 per VPC per region |
| Cloud Router | 1 per VPC per region |
| Internal CIDR range | 1 per client subnet CIDR per region |
| DNS zone | 2 per Autonomous Database |
Oracle Database@Google Cloud quotas
The following table shows the default resource quotas required for provisioning resources in Oracle Database@Google Cloud:
| Value | Default limit |
|---|---|
interconnect_attachments_per_region The number of Interconnect attachments required per project, per VPC, per region. |
16 |
routers-per-project The number of Cloud Routers required per project, per VPC, per region. |
10 |
PerProjectInternalRanges The internal CIDR range required per project, per VPC, per region. |
1500 |
managed-zones-per-project The number of DNS zones required per project. |
10000 |
managed-zones-per-network The number of DNS zones required per VPC. |
10000 |
target-nameservers-per-managed-zones The number of servers required per project, per VPC, per region. |
50 |