Skip to main content
NetApp database solutions

Learn about Google Cloud NetApp Volumes deployment options for Oracle Database 26ai

Contributors netapp-jsnyder
PDFs

Google Cloud NetApp Volumes supports Oracle Database 26ai across multiple deployment tiers, from dev/test environments to production high availability configurations with Data Guard and Fast-Start Failover. Review deployment requirements, compare HA tiers, and identify the task sequence for your chosen architecture on Google Cloud NetApp Volumes.

Deployment requirements

Ensure that you have the following items in place before provisioning Google Cloud NetApp Volumes for Oracle Database 26ai high availability:

  • A Google Cloud project with permissions for Compute Engine, VPC networking, firewall configuration, IAM, and NetApp Volumes

    Task Required access

    Create Compute Engine VMs

    Compute Instance Admin (or equivalent)

    Firewall / Firewall Policies

    Network Admin or delegated policy admin

    Create GCNV pools and volumes

    NetApp Volumes Admin

    Configure PSA

    Network admin in host project

    SSH via IAP

    IAP-secured Tunnel User + OS Login (if used)

  • The NetApp Volumes API enabled

  • A VPC and subnet configured for the target region

  • Private Services Access (PSA) configured for Google Cloud NetApp Volumes

  • Oracle Linux 10 for all required virtual machines

  • DNS and hostname resolution is configured for the database hosts and Observer host

  • Oracle installation media and patch files available for Oracle Database 26ai and Grid Infrastructure

  • Familiarity with Oracle Data Guard, Oracle Restart, and iSCSI storage concepts

  • Time synchronization is configured for all virtual machines.

    You can use the following commands:

    gcloud services enable netapp.googleapis.com
chronyc tracking
timedatectl

Example deployment configuration

This solution uses the following deployment configuration:

  • Three Google Compute Engine virtual machines:

    • oracdb1 for the primary database

    • oracdb2 for the standby database

    • oradg-obs for the Fast-Start Failover Observer

  • One GCNV Flex Unified storage pool per database zone

  • Five GCNV iSCSI volumes per database host

  • Oracle Data Guard Broker and Fast-Start Failover for automatic failover

  • Dedicated storage per database host; primary and standby hosts do not share iSCSI volumes

Replace all example values in the commands with values from your environment, including host names, IP addresses, zones, project names, portal IPs, passwords, and Oracle media file names.

Deployment options

The following table compares HA and DR deployment patterns and highlights where automation provides the most operational benefit.

Environment Requirement Recommended architecture HA DR Automation Key benefit

Dev/Test

Lowest cost

Single instance

No

Yes

No

Snapshot clone

Prod Basic (Restart)

Reduce downtime from crashes

+ Oracle Restart

No

Yes

Local only

Auto-restart

Prod HA (no DG)

Manual DR acceptable

+ Snapshots / RMAN

Partial

Yes

Partial

GCNV clone recovery

Prod HA (DG + FSFO)

True HA (no DBA)

Data Guard + FSFO

Yes

Yes

Full

True HA + fast failover
HA/DR/Automation

  • Yes = meets tier goal

  • No = not in scope

  • Partial = storage-level or manual steps only

Deployment tasks by HA tier

The deployment workflow provides a numbered step sequence for all deployment tiers. All tiers complete the base deployment tasks shown below, then add tier-specific tasks for production high availability:

Base deployment (all tiers):

  1. Review the solution architecture

  2. Review deployment options and requirements (this page)

  3. Verify access and APIs

  4. Provision Google Compute Engine instances

  5. Provision GCNV iSCSI storage

  6. Install Oracle Grid Infrastructure and Oracle Database 26ai

  7. Create the primary database

  8. Create the standby database

Tier-specific tasks (Prod HA only):

Tier Deployment steps

Dev/Test and Prod Basic (Restart) tiers

Complete base deployment Step 1 through Step 7 only. No standby database is required.

Prod HA (no Data Guard)

Complete base deployment Step 1 through Step 8.

Prod HA (Data Guard + FSFO)

Complete all base deployment steps, then add:
Step 9: Finalize standby database for Data Guard
Step 10: Configure Data Guard Broker and Fast-Start Failover

What's next?

To prepare your environment before deployment, continue with Access and APIs for Oracle Database 26ai on Google Cloud NetApp Volumes.