Organizations are continuously looking for ways to modernize their database platforms to improve agility, reduce operational overhead, and take advantage of cloud-native capabilities. Oracle offers multiple pathways to modernize your database estate, and one of the latest innovations is Oracle Autonomous Database Serverless (ADB-S)@Google Cloud.
By bringing Oracle Autonomous Database closer to Google Cloud workloads, organizations can leverage the power of Oracle’s self-managing, self-securing, and self-repairing database while benefiting from the scalability and ecosystem of Google Cloud.
In this blog series, we will explore a practical approach to performing a manual database migration to Autonomous Database Serverless (ADB-S)@Google Cloud. We’ll walk through the key steps involved in provisioning the target environment, configuring a custom NFS server, and migrating the database using Oracle Data Pump.
This is part 1 of the blog series which deals with ADB-S creation.
I have divided the blog into below sections.
Prerequisites
Step 1 – Create a VPC
Step 2 – Create an ODB network
Step 3 – Create an Autonomous Database
Prerequisites
It is important to have the required roles for Autonomous Database on Google Cloud and also on Oracle Cloud Infrastructure.
Please grant the necessary roles as per documentation.
Step 1 – Create a VPC
We need a VPC to start with which will be required in later steps.
We can create a new VPC or use an existing VPC based on our requirement.
I have created a VPC called ap-vpc.
Step 2 – Create an ODB network
Let’s navigate to Oracle Database@Google service as mentioned below.
Search Oracle Database on Google Cloud console to bring up the Oracle Database@Google Cloud service.
Select Oracle Database@Google Cloud from the search result to bring up Oracle Database@Google Cloud Page as shown below.
Select Create under Create an ODB network .
Enter below details.
Associated network – Select the VPC created earlier.
Region – Recommend to select the same region as our VPC.
ODB network name – Provide name of our choice.
Select the Create button to complete the ODB network creation.
Let’s now proceed with creating a subnet under ODB network.
Navigate to ODB network from Oracle Database@Google Cloud page .
select our ODB network to bring up ODB page.
Select Create against Subnets and enter below details.
Subnet name – Specify a name of our choice
Subnet range – Specify a CIDR range not overlapping with any other subnet in VPC.
Subnet Type – Select client for Autonomous database.
Select Create to complete the subnet creation.
Step 3 – Create an Autonomous Database
From the Oracle Database@Google Cloud page , select Autonomous AI database under Autonomous AI Database services.
Select Create to get started with ADB-S creation.
In the Instance details section, enter the following information.
Instance ID – Enter an Instance ID for your database.
Database name – Enter Database Name.
Database display name – Enter Database display name.
Region – Ensure to select the same region as ODB.
Select your workload type based on your requirement.
Select the license type , database version , ECPU and storage required .
We can also enable auto scaling for compute and storage if required.
Specify the Backup retention as per requirement and also specify the ADMIN user password.
Select network access type based on our requirement.
I have selected private endpoint access which would requires below inputs.
Network Project – Same as the project selected for VPC and ODB.
ODB network – Select the ODB network created in step 2.
Client Subnet – Select the subnet created in step 2.
It is recommended to specify the email IDs to be notified for any operational notification.
Select database character set and national characterset same as your source database.
Select Create to initiate the ADB-S provisioning.
That’s it , we have successfully deployed an ADB-S@Google Cloud.
Continue with Part 2 and Part 3 of the Blog series for completing the database migration.
Leave a Reply