Oracle and Google have announced a partnership to deliver Oracle Database services on Oracle Cloud Infrastructure (OCI) managed by Oracle, running inside Google Cloud data centers. This new service allows you to accelerate innovation and cloud migration and quickly build and modernize applications using capabilities such as Oracle Database 23ai’s AI Vector Search and JSON Relational Duality and Google’s Vertex AI and Gemini foundation models. Leverage a frictionless end-to-end experience across purchasing, operations, and collaborative support.
Oracle Exadata Database Service, Oracle Autonomous Database Serverless, and Oracle Database Zero Data Loss Autonomous Recovery Service are available. We expect this portfolio to grow rapidly with additional products.
Part number | Description |
---|---|
B95701 | Oracle Autonomous Data Warehouse - ECPU - ECPU Per Hour |
B95703 | Oracle Autonomous Data Warehouse - ECPU - BYOL - ECPU Per Hour |
B99709 | Oracle APEX Application Development - ECPU - ECPU Per Hour |
B95702 | Oracle Autonomous Transaction Processing - ECPU - ECPU Per Hour |
B93382 | Exadata Cloud Infrastructure - Storage Server - X9M - Hosted Environment Per Hour |
B93380 | Exadata Cloud Infrastructure - Quarter Rack - X9M - Hosted Environment Per Hour |
B93381 | Exadata Cloud Infrastructure - Database Server - X9M - Hosted Environment Per Hour |
B95706 | Oracle Autonomous Database Storage for Transaction Processing - Gigabyte Storage Capacity Per Month |
B95704 | Oracle Autonomous Transaction Processing - ECPU - BYOL - ECPU Per Hour |
B88847 | Exadata Database OCPU - Dedicated Infrastructure - BYOL - OCPU Per Hour |
B88592 | Exadata Database OCPU - Dedicated Infrastructure - OCPU Per Hour |
B91628 | Oracle Cloud Infrastructure - Object Storage - Storage - Gigabyte Storage Capacity Per Month |
B88327 | Oracle Cloud Infrastructure - Outbound Data Transfer - Originating in North America, Europe, and UK - Gigabyte Outbound Data Transfer Per Month |
B99708 | Oracle Autonomous JSON Database - ECPU - ECPU Per Hour |
B93456 | Oracle Cloud Infrastructure - Outbound Data Transfer - Originating in Middle East and Africa - Gigabyte Outbound Data Transfer Per Month |
B95754 | Oracle Autonomous Database Storage - Gigabyte Storage Capacity Per Month |
B95240 | Oracle Database Autonomous Recovery Service - Virtualized GB Per Month |
B91627 | Oracle Cloud Infrastructure - Object Storage - Requests - 10,000 Requests Per Month |
B95241 | Oracle Database Zero Data Loss Autonomous Recovery Service - Virtualized GB Per Month |
B93455 | Oracle Cloud Infrastructure - Outbound Data Transfer - Originating in APAC, Japan, and South America - Gigabyte Outbound Data Transfer Per Month |
All other Oracle Cloud part numbers are available only in OCI.
Please refer to the Oracle Database@Google Cloud regions section for regional availability and the roadmap. We encourage you to share any requirements for additional regions with your Oracle or Google account team.
At present, Exadata X9M is supported.
There is feature and list price parity between the services offered in Oracle Database@Google Cloud and Oracle Cloud Infrastructure; therefore, any database version currently supported and available on OCI is visible and available on Oracle Database@Google Cloud.
Yes, Oracle Database@Google Cloud supports both single-tenant and multitenant environments. Oracle Exadata Database Service on Dedicated Infrastructure running inside Google Cloud provides you with dedicated Exadata compute and storage nodes, just as it does when running on OCI.
Yes, tenancies can be either new or existing. You’ll be given the choice during the onboarding process. As the Oracle Database@Google Cloud service is physically present in Google Cloud, existing Oracle Exadata Database Service on Dedicated Infrastructure environments will not be "moved," either physically or commercially. New Exadata infrastructures built within Google Cloud will be seen in the existing OCI tenancy.
No, the pay-as-you-go option available via a public offer requires a new OCI tenancy. Linking to an existing OCI tenancy is only available through a private offer.
Oracle Database@Google Cloud refers to Oracle Database services on OCI managed by Oracle, running inside Google Cloud data centers. For Google Cloud and OCI regions with multiple zones and availability domains (ADs), Oracle Database@Google Cloud is deployed in the zone with a 1:1 mapping to the OCI availability domain.
As the database is provisioned and managed in OCI, existing database tooling, such as backups and cloning, will be available.
Oracle Database Autonomous Recovery Service and Oracle Cloud Infrastructure Object Storage are the recommended backup services for automated database backup and will draw down on a customer’s Google Cloud commitments.
The Google Cloud Marketplace provides private and public offers for Oracle Database@Google Cloud.
You can purchase Oracle Autonomous Database Serverless, Oracle Exadata Database Service, and Oracle Database Autonomous Recovery Service via a private offer.
First, you work with Oracle Sales to negotiate the commercial terms, which are formalized in an ordering document that’s shared with you for you to review and accept. You must purchase the private offer in the Google Cloud Marketplace to provision the services.
You can purchase Oracle Database@Google Cloud with an Oracle Database license included or use your existing Oracle Database licenses, including unlimited license agreements (ULAs) and Oracle Bring Your Own License (BYOL).
You can also purchase Oracle Autonomous Database Serverless via a public offer directly in the Google Cloud Marketplace as a pay-as-you-go purchasing option.
A public offer customer must be an existing Google customer with an associated financial agreement with Google. Those customers can initiate the Oracle Database@Google Cloud transaction on their own without an Oracle sales representative. The request will then come to Oracle for booking and the provisioning of the environment.
No. Oracle Database Autonomous Recovery Service is an Oracle Exadata Database Service backup service. Both services are available via a private offer.
Yes. You can use existing Oracle Database licenses, including unlimited license agreements (ULAs) and Oracle Bring Your Own License (BYOL).
Yes. Using Oracle Database@Google Cloud will accrue the same Oracle Support Rewards as using OCI directly. Oracle Support Rewards apply to private offers only.
Yes. You can use your Google Cloud commitments for Oracle Database@Google Cloud. See the commitments and discounts documentation for more information.
No.
Any OCI cross-region traffic that normally incurs network bandwidth costs will draw down on a customer’s Google Cloud commitments (for example, a customer with cross-region disaster recovery using Oracle Database@Google Cloud in region one and region two would incur network traffic costs).
For each Exadata cloud infrastructure instance you provision, you’re billed for an initial 48 hours of infrastructure consumption, then by the second after that. Each OCPU you add to the system is billed by the second, with a minimum usage period of one minute. If you terminate the cloud VM cluster and don’t terminate the cloud Exadata infrastructure resource, billing continues for the infrastructure resource.
Autonomous Database Serverless usage is billed according to the values of two parameters: compute and storage. You select values for these parameters when you provision or scale an Autonomous Database instance. See Autonomous Database Billing Summary for more details.
The practical minimum for purchasing Exadata on Oracle Database@Google Cloud is as follows:
The minimum for purchasing Autonomous Database on Oracle Database@Google Cloud is two ECPUs.
As is standard with Oracle Exadata Database Service, each Oracle Database Exadata infrastructure shape/instance has a minimum service period of 48 hours.
For Autonomous Database services, partial ECPU hours consumed are billed per second, with a one-minute minimum.
Please refer to Oracle PaaS and IaaS Universal Credits Service Descriptions for more information.
At present, there is no Free Tier option.
The provisioning of Oracle Database on Oracle Database@Google Cloud is the same as on OCI, using the same UI flow, API calls, and so on.
Migrating to this offering is like migrating to OCI, as the database service runs on OCI. Oracle provides proven database migration strategies, including automated migration solutions such as Oracle Zero Downtime Migration and powerful tools such as Oracle Data Guard and Oracle Cloud Infrastructure GoldenGate.
Oracle Database@Google Cloud is a standard deployment, available within the Google Cloud VPC. Oracle Database management tools, such as Data Pump, can be used to import data into the database from Google database clients and Google Cloud Storage.
For Oracle Exadata Database Service, the Exadata infrastructure and Exadata VM cluster must be created from Google Cloud. The Oracle Database home, container databases, and pluggable databases must be created from the OCI Console. Oracle Autonomous Database Serverless instances are created entirely from Google Cloud.
The network between the Oracle Database@Google Cloud deployment in Google Cloud and its parent OCI site is dedicated, redundant, Oracle internally managed dark fiber, similar to OCI AD-to-AD network infrastructure. The connection between Oracle Database@Google Cloud and Google Cloud is achieved via local connectivity through redundant network hardware directly to Google Cloud network infrastructure.
Each Oracle Database@Google Cloud deployment is connected to an OCI parent site. This link is used for the following:
The network between the OCI parent and Oracle Database@Google Cloud infrastructure is considered an internal regional network; therefore, no traffic costs or throttling limits are in place. Any capacity and other limits imposed on Google Cloud virtual networking are still in effect.
No, Oracle Interconnect for Google Cloud is a standalone Oracle service available for customers to consume when deploying Oracle and Google Cloud services that require interconnectivity. Oracle Database@Google Cloud doesn’t use this network link.
Both the OCI-Google interconnect and Oracle Database@Google Cloud take advantage of the proximity between clouds; therefore, there may be significant overlap in future region rollouts.
If you wish to use other OCI services with Google Cloud services, Oracle Interconnect for Google Cloud will need to be configured.
No. Oracle owns the link, the management, and the traffic flowing between the Google Cloud data center and the OCI parent data center. Google Cloud and OCI management networks don’t intersect. Google Cloud has no visibility past the termination point in the partner transfer equipment within the data center to which Oracle connects. And vice versa, Oracle can’t see past this same point. The network link is treated as internal to Oracle.
Oracle Data Guard redo logs are shipped from the primary database to the standby database via the client subnet across customer-managed networks on OCI infrastructure.
* Incurs outbound data transfer costs.
Existing Exadata Database Service and Autonomous Database deployments will still be operational; however, you won't be able to create, update, or delete resources. Any process or procedure relying on OCI-based services (for example, OCI Vault key lookup, database backups, and so on) will fail.
Metrics and logging shipped from OCI to Google Cloud Monitoring will be delayed, even though the Exadata Database Service and Autonomous Database deployments are functional.
It is expected that all control plane functionality will become unavailable.
The dynamic routing gateway (DRG) used to provide the link between OCI and Google Cloud network resources is housed within a tightly controlled service virtual cloud network (VCN) and can’t be updated. When provisioned, the Exadata VM cluster resources are attached to this DRG. If you have specific routing requirements, you can use local peering groups to connect to another VCN. This locally peered VCN can then be attached to a DRG you control. This DRG can be used for cross-region replication (see the question about data replication for disaster recovery).
Oracle Database@Google Cloud is focused on high performance and low-latency workloads running in Google Cloud. If the workload that requires low latency is in OCI, we recommend deploying Oracle Exadata Database Service or Oracle Autonomous Database in OCI. Where available, we recommend using Oracle Interconnect for Google Cloud to connect the OCI service and Oracle Database@Google Cloud to meet low-latency needs.
All traffic between sites, including Oracle Database@Google Cloud infrastructure, is encrypted.
As the database is created via OCI, Oracle Cloud Infrastructure Vault is used to house the system-generated or customer-generated key.
Oracle Database@Google Cloud is launched in multiple Google Cloud regions. You can use Oracle Data Guard to deploy cross-region DR solutions.
The Oracle Database@Google Cloud infrastructure is identical to that in OCI; therefore, standard Exadata and Oracle Database sizing tools, such as Oracle Cloud Capacity Analytics, can be used.
Oracle Database@Google Cloud will initially be available in a single zone within each Google Cloud region.
Yes, for consulting services. Please note that Oracle Database@Google Cloud is sold to customers directly via the Google Cloud Marketplace and isn’t available for purchase through any other company or channel.
If you're interested in becoming an Oracle consulting services partner as well as qualifying for a Service Expertise designation, you can find the latest information on the Oracle Partner Network website. Service providers can purchase the offering directly, but not on behalf of customers.
Oracle and Google have developed a joint support model to provide rapid response and resolution for mission-critical workloads. Customers will create all technical support requests directly with Oracle. Oracle will engage Google support if needed.
Oracle and Google have partnered to provide you with a well-integrated Google Cloud experience for deploying, managing, and using Oracle Database instances in Google Cloud. For most day-to-day operations, you’ll be able to use native Google Cloud tooling.
Oracle Database@Google Cloud management is the same as Oracle Exadata Database Service on OCI; therefore, Operator Access Control isn’t applicable.
Oracle Database@Google Cloud resources that are provisioned and managed via the Oracle Database resource provider in Azure can be operated and managed from the Google Cloud console, API, SDK, or CLI.
Expansion of the resources and features managed by the Oracle resource provider is on the roadmap.