Oracle Database @Google Cloud - Multi Cloud

 

👉 What this diagram is about (view)

This picture shows how Oracle Cloud and Google Cloud are directly connected by a fast private road.

• Oracle Cloud = one city

• Google Cloud = another city

• Interconnect = a private highway between the two cities

• No public internet involved

🔹 Simple story

Your application is in Google Cloud
Your database is in Oracle Cloud

Instead of sending data over the public internet (slow + risky),
Oracle and Google built a dedicated private connection just for customers.

🔵 Diagram 2: Oracle Database @ Google Cloud (September 2024)

👉 What this diagram is about (Layman view)

This picture shows Oracle Database running inside Google Cloud itself.

Not connected from outside — it is already there.

🔹 Simple story

Your application is in Google Cloud
Your Oracle database is ALSO in Google Cloud

Oracle installs and manages its database inside Google’s data center, but:

• Oracle still controls the database

• Google still controls the cloud

🔹 What happens here

• No cross-cloud traffic

• No interconnect needed

• App and DB talk like neighbors

• Extremely low latency

• Oracle handles DB operations

• Google handles infrastructure

Oracle Database@Google Cloud runs Oracle-managed OCI database infrastructure colocated within Google Cloud regions. 

Applications use native GCP services, while databases run on OCI Exadata with OCI networking constructs such as VCN and subnets. 

Connectivity between GCP VPCs and OCI networks is privately managed by Oracle, eliminating the need for interconnects or public networking. 

The OCI control plane remains in Oracle Cloud, while the data plane resides inside Google Cloud, providing low latency, high availability, and full Oracle-managed database operations.

Inside Google data center, Oracle does this:

• Oracle installs multiple independent racks

• Each rack group has:

  • Independent power feeds

  • Independent network paths

  • Independent storage

• Oracle labels these internally as:

  • AD-1

  • AD-2

  • FD-1 / FD-2 / FD-3

⚠️ These AD/FD are OCI logical constructs,
not Google’s zones.

Who manages what (VERY IMPORTANT)

Layer	Who manages it
Building, power, cooling	Google
Physical servers, storage	Oracle
Network between Oracle racks	Oracle
Oracle Exadata / ADB	Oracle
AD / FD logic	Oracle
Patching, backups, RAC	Oracle
App (VMs, GKE, Cloud Run)	You / Google

So Oracle is running OCI inside GCP, not OCI on top of GCP.

Multi-AD / HA in Oracle DB @ GCP

Example: Autonomous Database

• Oracle deploys:

  • Primary DB in one Oracle AD

  • Standby DB in another Oracle AD

• Both ADs are inside same GCP region

• Failover handled by Oracle

👉 From DB point of view:
Same HA behavior as OCI region

=========================================================================

This diagram is not about architecture — it is about how easy Oracle Database@Google Cloud is to buy, operate, and use.
Think of it as customer journey + operations flow.

I’ll explain it step by step, in plain technical language, then summarize it in one clean mental model.

---

1️⃣ What this diagram represents (big picture)

Goal of the diagram:
👉 “Oracle Database behaves like a native Google Cloud service, even though Oracle manages it underneath.”

So this diagram answers:

• How do you buy it?

• How do you deploy & manage it?

• How do you use it with other GCP services?

---

2️⃣ Step 1: Purchase in Google Cloud Marketplace

What happens technically

• Oracle publishes Oracle Database@Google Cloud as a Marketplace offering

• You subscribe using:

  • Your Google Cloud account

  • Your Google billing

• No separate Oracle contract process

Key technical implication

• Billing appears in GCP Billing

• IAM access tied to GCP project

• Subscription links your GCP project ↔ Oracle tenancy

📌 Under the hood:
Google forwards subscription metadata to Oracle → Oracle activates OCI resources.

---

3️⃣ Step 2: Deploy, manage, and monitor from Google Cloud Console

This is the most important part of the diagram.

What you see

• Oracle Database appears as a service inside GCP Console

• You can:

  • Create Exadata / Autonomous DB

  • Scale CPU / storage

  • View metrics

  • Monitor health

What happens under the hood

Action in GCP Console	Actual execution
Create DB	Oracle Control Plane
Scale DB	OCI automation
Patch DB	Oracle SRE
Monitor DB	OCI metrics bridged to GCP Monitoring

📌 UI = Google
📌 Brain = Oracle

---

4️⃣ Instance creation screen (middle image)

This screen shows:

• DB shape selection

• Storage sizing

• CPU configuration

• Region mapping

Important technical detail

You are not choosing GCP machine types.

You are choosing:

• Oracle Exadata shape

• Oracle storage layout

• Oracle HA configuration

Oracle maps this to its OCI hardware inside GCP DC.

---

5️⃣ Monitoring & metrics (graph screen)

• Metrics appear in Google Cloud Monitoring

• Data source is Oracle DB telemetry

• Metrics include:

  • CPU utilization

  • Storage usage

  • I/O behavior

📌 Monitoring is integrated, not duplicated
📌 No need to log into OCI console separately (unless deep DBA ops)

---

6️⃣ Step 3: Combine with your choice of Google Cloud services

This right-most part shows native GCP services:

• Compute Engine

• GKE

• Cloud Run

• BigQuery

• Vertex AI

• VPC Network

• Cloud Storage

Technical meaning

• Apps connect to Oracle DB over private OCI-managed network

• Latency is intra-datacenter

• No VPN, no Interconnect, no public IP

Result

• Google apps feel like they are talking to a native database

• Oracle DB keeps OCI-grade reliability

=========================================================================

Google runs the application, Oracle runs the database — both inside the same Google Cloud zone, but with separate ownership.

---

🔁 Concept Mapping (Google ↔ Oracle)

🟦 Google Cloud side

• Project (Google) → Your billing + IAM + resources container

• VPC (Google) → Network for your applications

• Zone (Google) → Physical location where your app VM/GKE runs

• Application Subnet → App lives here

---

🟥 Oracle Cloud side (inside Google DC)

• Tenancy (Oracle) → Oracle’s account that owns the DB

• VCN (Oracle) → Oracle’s private network for DB

• AD (Oracle) → Oracle’s fault-isolated deployment unit

• Client / DB / Backup Subnets → Oracle DB traffic separation

---

🔌 How they connect

• App in GCP VPC talks to DB in OCI VCN

• Connection is via OCI-managed private network

• No public IP, no VPN, no interconnect

---

🧠 One-line memory trick

Project ↔ Tenancy
VPC ↔ VCN
Zone ↔ AD
App ↔ DB (private, Oracle-managed)

---

Onboarding:-

Note:-

Patching - As DBA we need to do it (GRID + Oracle) - ExaCC / ExaCS / DBCS 

Creating Autonomous Database :-

Create Exadata@GCP