Note:

• This tutorial requires access to Oracle Cloud. To sign up for a free account, see Get started with Oracle Cloud Infrastructure Free Tier.
• It uses example values for Oracle Cloud Infrastructure credentials, tenancy, and compartments. When completing your lab, substitute these values with ones specific to your cloud environment.

Provision Oracle Exadata Database Service at Oracle Database@Google Cloud

Introduction

Oracle Database@Google Cloud provides you with all the performance, scale, and availability advantages of using Oracle Exadata Database Service in Oracle Cloud Infrastructure (OCI) while running applications and other services in Google Cloud. This joint solution enables developers to deploy creative applications that combine Oracle Database innovations such as AI Vector Search with best-in-class Google Cloud services like Vertex AI and Gemini foundational models.

Exadata Infrastructure is co-located in the Google Cloud Data Center, as show in the network diagram. The Exadata Infrastructure is assigned to a Google Cloud project which is the basis for creating, enabling, and using all Google Cloud services such as managing user permissions and billing. You will create a virtual private cloud (VPC), that will connect to the Exadata VM and databases using the Oracle-managed network.

Objectives

• Provision Exadata Infrastructure, Exadata VM Cluster and Oracle Database 23ai.

Task 1: Provision Exadata Infrastructure

1. Log in to the Google Cloud Console, click Exadata Database, Exadata Infrastructure, and Create.

   Note: Assume that your OCI tenancy has been linked through the private offer and the VPC has already been provisioned.

   

2. In Exadata Infrastructure Instance details, enter the Infrastructure display name, Infrastructure ID, and select the region the Exadata Infrastructure will be provisioned in.

   Note: The Infrastructure ID must be unique across all of the Exadata Infrastructures in Google Cloud. The infrastructure display name may be updated.

   

3. In Machine configuration, select Exadata Infrastructure shape. The minimum configuration is already filled in for you. With two Database servers and three Storage servers you have access to 252 OCPUs and 189 TB of useable storage to use with your database workloads.

   

4. Oracle Exadata Database Service is a co-managed service in which Oracle provides infrastructure maintenance. As part of the provisioning process, you can specify the Maintenance method and schedule. Click Change and enter the following information.

   

   • The Maintenance method Preference can be Rolling or Non-rolling. By default, Exadata Infrastructure is updated in a rolling fashion, one server at a time with no downtime. The non-rolling maintenance method minimizes maintenance time but incurs full system downtime.

   • Enable custom action only if you want to perform additional actions outside of Oracle’s purview. Custom action timeout is available to perform custom actions before starting maintenance on the database (DB) servers.

   • In Maintenance Schedule, the default setting No preference to allow the system to assign a date and start time for infrastructure maintenance. You can customize the schedule by selecting Specify a Schedule.

   • Provide up to 10 unique Maintenance contacts email addresses to receive notifications of when maintenance is scheduled.

   

5. Click Save to save your maintenance updates.

6. Click Create to proceed with the Exadata Infrastructure provisioning.

   

Task 2: Provision Exadata VM Cluster

Each Oracle Exadata database server contains one or more virtual machine (VM) guests. With support for multiple virtual machine clusters (MultiVM), you can support up to eight VMs per database server and host a total of eight VM clusters per Exadata database system. When you provision the VM cluster, you specify system resources allocated to the VM clusters that will support your Oracle database workloads.

1. To create an Exadata VM cluster, click CREATE to associate the VM cluster to the Exadata Infrastructure. The VM cluster configuration is based on the databases that will be provisioned inside the VM. This includes number of OCPUs, memory, database storage, client and backup networking, and database licensing.

   In the Exadata Database page, click EXADATA VM CLUSTERS and CREATE.

   

2. In the Basic details page, enter the following information.

   • Display name: Enter a user-friendly display name for the VM cluster. The name does not need to be unique.

   • VM Cluster ID: The VM cluster ID must be unique within your tenancy.

   • Oracle Grid Infrastructure version: Select the Oracle Grid Infrastructure version of release (19c and 23ai) that you want to install on the VM cluster.

   Note: The Oracle Grid Infrastructure release determines the Oracle Database releases that can be supported on the VM cluster. For example, you cannot run an Oracle Database release that is newer than the Oracle Grid Infrastructure software release.

   

3. The VM cluster configuration allows you to allocate resources to your VM. Enter the following information.

   • OCPU count per VM: Enter OCPU count per VM to allocate that number of OCPUs to each of the VM clusters’ virtual machine compute nodes. Minimum is two OCPUs per VM. Total Requested OCPU count is the total number of OCPU cores you are allocating across the VM cluster.

   • Memory per VM: Enter the memory per VM to allocate to each VM. The minimum per VM is 30 GB.

   • Local Storage per VM: Enter the local storage per VM to allocate local storage to each VM. The minimum per VM is 60 GB.

   Note: Each time you create a new VM cluster, the space remaining out of the database server local space is utilized for the new VM cluster.

   

4. Enter the usable Exadata storage configuration in multiples of 1 TB. The minimum is 2 TB.

   • Allocate storage for Exadata sparse snapshots: Select if you intend to use snapshot functionality within your VM cluster. The storage configuration option for sparse snapshots cannot be changed after VM cluster creation.

   • Allocate storage for local backups: Select if you intend to perform database backups to the local Exadata storage within your Oracle Exadata Cloud Infrastructure instance. The storage configuration option for local backups cannot be changed after VM cluster creation.

   

5. Define the Networking that is authorized to connect to the Exadata VM cluster by selecting the Network project and Associated network and enter the following information.

   • Client IP Range: The client IP range to which the VM cluster should attach.

   • Backup IP Range: The backup IP range is used for the backup network to transport backup information to and from the backup destination, and for Oracle Data Guard replication.

     Note: Do not use a subnet that overlaps with 192.168.16.16/28, which is used by the Oracle Clusterware private interconnect on the database instance.

   • Hostname prefix: It must begin with an alphabetic character and can contain only alphanumeric characters and hyphens (-). The maximum number of characters allowed for an Exadata DB system is 12.

     Note: The hostname must be unique within the subnet.

   

6. Enter the SSH keys to access the services of your system’s databases by using SSH tunneling. Enter the SSH public key(s) that you want to use to access the VM cluster compute nodes.

   

7. Select the License type you want to use for the VM cluster.

   • License Included: Select if the cost of the cloud service includes a license for the database service.

   • Bring Your Own License (BYOL): Select if you are an Oracle Database customer with an Unlimited License Agreement or Non-Unlimited License Agreement and want to use your license with Oracle Cloud Infrastructure.

   

8. By enabling Diagnostics collection, Oracle Cloud operations and you will be able to identify, investigate, track, and resolve guest VM issues quickly and effectively. Subscribe to events to get notified about resource state changes.

   Note: You can opt out of this feature at any time.

   

9. In the Advanced fields section, enter the following information.

   • Timezone: Indicate the time zone for the VM cluster.

   • SCAN Listener Port (TCP/IP) Enter the SCAN listener port (TCP/IP). You cannot change this after the VM cluster has been provisioned.

   

10. Click Create to proceed with the Exadata VM cluster provisioning.

    

Task 3: Create Oracle Database

1. Oracle Database creation is managed from the OCI Console. With the tight integration between OCI and Google Cloud, a direct link is available from the Google Console. Click MANAGE IN OCI.

   

2. Oracle Database is a VM cluster resource. In the Exadata VM Cluster detail page, scroll down.

   

   Under Resources, click Databases and Create database.

   

3. In the Basic information for the database section, enter the following information.

   • Provide the database name: Enter the database name.

     Note: You need to meet the following requirements.

     • Maximum of eight characters.
     • Contain only alphanumeric characters.
     • Begin with an alphabetic character.
     • Cannot be part of the first eight characters of a DB_UNIQUE_NAME on the VM cluster.

   • Provide a unique name for the database (Optional): If not specified, the system automatically generates a unique name value, as <db_name>\_<3_chars_unique_string>\_\<region-name\>.

     Note: If you enter a unique name, you need to meet the following requirements.

     • Maximum of 30 characters.
     • Contain only alphanumeric or underscore (_) characters.
     • Begin with an alphabetic character.
     • Unique across the VM cluster. Recommended to be unique across the tenancy.

   • Select a Database version: Select a database version.

   • Provide a PDB name (Optional):. If not specified, the system automatically generates a name value.

     Note: You need to meet the following requirements.

     • Maximum of eight characters.
     • Contain only alphanumeric or underscore (_) characters.
     • Begin with an alphabetic character.
     • To avoid potential service name collisions when using Oracle Net Services to connect to the PDB, ensure that the PDB name is unique across the entire VM cluster.

     

4. In the Specify a database home section, enter the following information.

   • Database Home source: Select database home source.
     • Select an existing Database Home.
     • Create a new Database Home and enter Database Home display name.
   • Enable database Unified Auditing
   • Database Image (Optional): Database image to use a desired Oracle-published image or a custom database software image that you have created in advance.

   

5. In the Create administrator credentials section, create administrator credentials for sys password.

   • Password: Enter password.

     Note: You need to meet the following requirements.

     • Must be 9 to 30 characters.
     • Contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be (_), (#), or (-).
     • The password must not contain the username (SYS, SYSTEM, and so on) or the word Oracle either in forward or reversed order and regardless of casing.

   • Confirm password: Confirm password by re-entering the sys password you specified.

   • Selecting Use the administrator password for the TDE wallet password is optional.

   

6. In the Configure database backups section, configure database backups by specifying the settings for backing up the database to Oracle Database Autonomous Recovery Service or OCI Object Storage.

   • Enable automatic backup: Select to enable automatic backups for this database.
   • Backup Destination: Backup destination choices are Autonomous Recovery Service or Object Storage. After you select, review and enter the information requested for each service. For more information about backup destination, see Manage Database Backup and Recovery on Oracle Exadata Database Service on Dedicated Infrastructure.

   

7. Click Show advanced options.

   1. In the Management section, enter the following information.

      • Oracle SID prefix (Optional): Oracle SID prefix is the Oracle Database instance number and is automatically added to the SID prefix to create the INSTANCE_NAME database parameter. The INSTANCE_NAME parameter is also known as the SID. The SID is unique across the cloud VM cluster. If not specified, SID prefix defaults to the db_name.

        Note: You need to meet the following requirements.

        • Maximum of 12 characters.
        • Contain only alphanumeric or underscore (_) characters.
        • Begin with an alphabetic character.
        • Unique in the VM cluster.

      • Character set: Character set for the database. The default is AL32UTF8.

      • National character set (Optional): National character set is the national character set for the database. The default is AL16UTF16.

      

   2. In the Encryption section, to manage your database keys select Use Oracle-managed keys or Use customer-managed keys. For more information about the options to manage your database keys, see Security Guide for Oracle Exadata Database Service on Dedicated Infrastructure.

      

   3. In the Tags section, select Tag namespace. Tagging allows you to define Tag key(s) and Tag value(s) and associate them with resources. You can then use the tags to help you organize and list resources based on your business needs. For more information about tags, see Tagging Oracle Exadata Database Service on Dedicated Infrastructure Resources.

      

8. Click Create Database to proceed with the Oracle Database provisioning.

   

Next Steps

You are now ready to migrate your data to your new Oracle Database. Take a look at Oracle Zero Downtime Migration (ZDM) to help you with your migration needs.

Related Links

• Oracle Exadata Database Service on Dedicated Infrastructure

• Oracle Exadata Database Service on Dedicated Infrastructure How To’s Video Playlist

• Oracle LiveLabs Workshop: Get Started with Oracle Exadata Database Service on Dedicated Infrastructure

• Tagging Oracle Exadata Database Service on Dedicated Infrastructure Resources

• Oracle Zero Downtime Migration

Acknowledgments

• Authors - Tammy Bednar, Leo Alvarado (Product Management)

More Learning Resources

Explore other labs on docs.oracle.com/learn or access more free learning content on the Oracle Learning YouTube channel. Additionally, visit education.oracle.com/learning-explorer to become an Oracle Learning Explorer.

For product documentation, visit Oracle Help Center.

---

Title and Copyright Information

Provision Oracle Exadata Database Service at Oracle Database@Google Cloud

G14193-01

September 2024

Copyright ©2024,

Oracle and/or its affiliates.