Oracle Cloud Infrastructure Documentation

Getting Started

Learn the basic concepts for Oracle Database@Google Cloud onboarding.

Oracle Database@Google Cloud is an Oracle database service running on Oracle Cloud Infrastructure (OCI), colocated in Google data centers. This ensures that the Oracle Database@Google Cloud service has the fastest possible access to Google Cloud resources and applications.

Oracle Database@Google Cloud runs on infrastructure managed by Oracle's expert Cloud Infrastructure operations team. The operations team performs software patching, infrastructure updates, and other operations through a connection to OCI. While the service requires that customers have an OCI tenancy, most service activities take place in the Google environment.

Purchase and Setup Steps

Because OCI multicloud products deliver hardware and software in two cloud environments, the process for configuring the service idiffers from most OCI cloud services.

We refer to this part of the process as onboarding, and it consists of the steps described below. The steps detail the organizational roles, responsibilities, permissions, and other information needed to complete them. After you’ve successfully onboarded, you can start provisioning Exadata and Autonomous Database resources in your Google Cloud environment.

Purchase Offer Options

Oracle has two options for purchasing Oracle Database@Google Cloud:

  • Private offer: With this option, you first contact Oracle's sales team to negotiate a contract for Oracle Database@Google Cloud. To use Oracle Exadata Database Service, you must purchase Oracle Database@Google Cloud using a private offer. You can also provision Autonomous Database after purchasing a private offer.
  • Pay As You Go offer: You can purchase this offer in the Google Cloud Marketplace without contacting Oracle Sales. Oracle offers Autonomous Database for customers purchasing the Pay As You Go offer. Pay as You Go offers the most flexibility, letting you start and stop using the service at any time.

Billing and payment for the service is done through Google Cloud. Payment for Oracle Database@Google Cloud counts toward your Google Cloud Commitments. Existing Oracle Database software customers can use the Bring Your Own License (BYOL) option or Unlimited License Agreements (ULAs). On your regular Google Cloud invoices, you'll see charges for Oracle Database@Google Cloud alongside charges for your other Google Cloud Marketplace services.

Roles and Responsibilities

Each Onboarding step requires one or more customer teams to be involved. Depending on the size of your Google Cloud investment and your organization, some members of your organization could be on more than one of the teams described in the following section.

The following table summarizes the teams involved in each step of the process. Sometimes, more than one team might need to collaborate on the work of an onboarding step, or a second team might need to review the work of the team primarily responsible for the work of the onboarding step.

Customer team Onboarding steps performed
Business owner

This is the persona that wants to purchase the service (or receives internal requests for it), and who starts working with the Legal and Purchasing teams on the purchase.

  • Selects either the public or private offer
  • Places a private offer request (if applicable)
  • Reviews and approves the private offer (if applicable)
Purchasing
  • Selects public or private offer
  • Places a private offer request (if applicable)
  • Reviews and approves the private offer (if applicable)
Legal
  • Selects public or private offer
  • Reviews and approves the private offer (if applicable)
Cloud administrator
  • All onboarding steps (see also "security specialist" and "identity" teams for steps involving role based access control and identity)
Networking specialist
  • Checks tenancy networking limits
Security specialist and Identity teams
Database administrator
  • Checks tenancy limits for Oracle Database@Google Cloud database resources

Onboarding Overview

During onboarding, you configure your Google Cloud environment to use the Oracle Database@Google Cloud service, which consists of the following steps:

Business Relationship and Offer Selection

OCI offers customers two Google Cloud Marketplace offers: private and public. The selection you make here sets your company's business relationship with Oracle for Oracle Database@Google Cloud.

The public offer is for customers testing the service or for customers that have short-term needs for an Oracle Database in Google Cloud. Google charges you list price for consumed resources, and you pay for service resources using regular Google Cloud billing. To use this offer type, search the Marketplace for "Oracle Database" and select Oracle Database@Google Cloud from the list of options.

The private offer is for customers that need a lot of database resources or do not want to pay list price. For this option, your organization contacts the Oracle Sales team and negotiates a service price based on parameters such as length of contract, spend commitment, and number of Exadata hardware deployments. After you successfully negotiate and sign a contract with Oracle, OCI creates a private offer for your organization in Google Cloud Marketplace for you to accept. After your organization signs the purchase agreements, OCI creates an order in the Google Cloud Marketplace, then sends you an email confirming the offer.

Note that public offers for the Oracle Database@Google Cloud service only support provisioning Oracle Autonomous Database Serverless (ADB-S) on the Google Cloud. If your organization requires Exadata database resources, you will need a private offer from Oracle Sales. If your organization is required to use the public offer option, contact Oracle Sales for assistance.

Offer Activation

To activate an order, an authorized user with the required permissions signs in to the Google Cloud console and follows the steps based on the offer type selected:

  • Public Offer: Open the Google Cloud Marketplace in a browser window, then search for and select the "Oracle Database@Google Cloud" offering.
  • Private Offer: Click the link in the email you received from Oracle, or open the Google Cloud Marketplace Orders page, then click the link for your offer.

At this point, you connect your Google Cloud billing account with a new or existing OCI cloud account. Here's what happens during this process:

  • Google Cloud Marketplace prompts you to select an existing OCI cloud account (this option is only available for private offers), or create a new OCI cloud account to use with the Oracle Database@Google Cloud. An OCI account is required because, while the databases are deployed in your Google Cloud environment, some resource components like the Database control plane and metrics are deployed in OCI.
  • The Google Cloud and OCI accounts are linked. During this process, the service defines a connection between a Google Cloud billing account (selected by the user) and an Oracle Database Subscription for the service. This defines the mapping between Google Cloud and OCI that's used when provisioning resources in both environments, managing billing, delivering metrics, and more.

Required Permissions for Activation

To activate a Google Cloud Marketplace offer, you must have the following Identity and Access Management (IAM) roles assigned to your user account for the Google Cloud Billing account listed in the offer (see Accept a private offer from a vendor for more details).

If you don't have the required roles, request access from a Billing administrator or your organization's Google Cloud administrator. For details on assigning roles, see Access control.

The serviceusage.services.enable Google Cloud IAM permission is required to enable a service for a Google Cloud project. There are basic and predefined IAM roles that include this permission. See Access Control with IAM and Method:services.enable for more information..

Environment Preparation

At this point, the Oracle Database@Google Cloud service is enabled in your Google Cloud environment. The user who onboarded the service is ready to begin deploying Oracle Database resources in the environment, but it's important to verify your tenancy limits to ensure you can deploy the database resources you need.

OCI Service Limits

OCI uses service limits to control the number of certain resource types that you can deploy in OCI. Your ability to deploy Oracle Database resources in Google Cloud (and OCI) is affected by the service limits set in your OCI cloud account. When creating a new OCI tenancy, or connecting to an existing OCI tenancy, the linking process described in this topic automatically sets limits for Oracle Database products and associated resources in the OCI cloud account used for Oracle Database@Google Cloud.

Before you begin provisioning Oracle Database resources in Google Cloud, assess how many Oracle Database resources (Exadata Infrastructure, Exadata VM clusters, CDBs, and PDBs) you plan to deploy in your Google Cloud environment. Then review the current service limits in your OCI tenancy and determine if your existing limits will let you deploy the number of Oracle Database@Google Cloud resources you need.

If you need to increase your service limits, see Requesting a Service Limit Increase for information.

Role Based Access Control (RBAC)

To enable users to perform actions such as provisioning databases in the Oracle Database@Google Cloud service, you must grant permissions through role based access control (RBAC) in Google Cloud IAM. While you can manually assign roles to individual users, the use of groups simplifies the administration of your environment. You can create a set of groups for Oracle Database@Google Cloud, assign the required roles to the groups, and then add individual users to the groups to give them the permissions they need.

See Task 5: Set Up Role Based Access Control for more information.

Identity Federation

Identity federation is optional. We recommend configuring identity federation between OCI and Google Cloud, because some database management operations are not available in the Google Cloud Console. To perform these operations, users must sign in to the OCI Console.

With identity federation, Google Cloud users sign in to the OCI Console using authentication provided by Google Cloud IAM, and do not have to manage separate sign in credentials for each cloud. Without identity federation, the OCI IAM or security administrator must manually create user accounts in OCI IAM for each user who needs to work in the OCI Console, and users must manage separate sign in credentials for each cloud if they need access to both cloud consoles.

Register with My Oracle Support (MOS)

After completing the onboarding steps to configure the Oracle Database@Google Cloud service, the administrator who performed the onboarding tasks has authorization to create OCI support tickets, but others in their organization do not have unless they were already registered with My Oracle Support (MOS) before the Oracle Database@Google Cloud onboarding. To give users MOS access, you must register them with My Oracle Support. This includes users created through identity federation and users created directly in OCI IAM.

Oracle Database@Google Cloud Interfaces

You can provision Oracle Database@Google Cloud using the Google Cloud console and Google Cloud APIs, SDKs and Terraform. Management of Oracle database system infrastructure and VM cluster resources takes place in the Google Cloud console as well.

For Oracle Container Databases (CDB) and Oracle Pluggable Databases (PDB), some management tasks are completed using the OCI console.

Database and application developers work in the Google Cloud console or use Google Cloud tools (Google Cloud API, SDK, Terraform) to interact with Oracle Database@Google Cloud databases.