This page describes how to create an Autonomous Database in Google Cloud.
In Oracle Database@Google Cloud, you can create an Autonomous Database in the Google Cloud using Google Cloud console or the Oracle Database@Google Cloud API. To see which regions you can create Autonomous Database resources in, see Available configurations .
Before you begin
-
Confirm you have an active marketplace order for Oracle Database@Google Cloud.
-
Enable the Oracle Database@Google Cloud API for the project.
-
Create an ODB Network and ODB Subnets . An Autonomous Database requires at least a client subnet.
-
Confirm that you have the required roles necessary to create an instance:
autonomousDatabaseAdmin
.For more information on how to assign roles, see Apply IAM roles .
Create an Autonomous Database
To create a Autonomous Database, do the following:
Console
-
Go to the Autonomous Database Servicepage in the Google Cloud console.
-
Click Create.
-
In the Instance detailssection, complete the following:
-
Enter an Instance IDfor your database. This field is permanent and can't be modified once created.
-
Enter a Database namefor your database. The database name must meet the following criteria:
- Only contain letters and numbers
- Must start with a letter
- Can't exceed the maximum limit of 30 characters
-
Enter a Database display nameto help identify your database.
-
Select a Regionfor your database from the drop-down. The region choice is permanent and can't be changed later.
-
Confirm your Oracle Cloud account. If the account name doesn't match your Oracle Cloud account, confirm that you're in the correct project for your database.
-
-
In the Workload configurationsection, choose one of the following workload types for your database:
-
Data Warehouse: select the data warehouse if you're looking for fast queries over large volumes of data. This is built for data warehouse workloads.
-
Transaction Processing: select transaction processing if you're looking for high concurrency for short-running queries and transactions. This is built for transactional workloads.
-
JSON: select JSON if you're looking for JSON-centric application development that has built-in JSON storage.
-
APEX: select APEX if you're looking for a warehouse built for Oracle APEX application development with creation and deployment of low-code application.
-
-
In the Database configurationsection, complete the following:
-
Select your License typefrom the drop-down. If you choose Bring Your Own License (BYOL), then select the edition from the Oracle Database Editiondrop-down.
-
Select a database version in the Choose database versiondrop-down.
-
In the ECPU countfield, enter your preferred count. The ECPU count can range from 2 to 512.
Select the Enable compute autoscalingcheckbox to let the system to expand the specific ECPU count up to three times if the demand increases. This is an optional field.
-
In the Storage (TB)field, enter your preferred storage count. Storage can range from .02 TB to 384 TB and is measured in gigabyte (GB) increments.
For Data Warehouse workloads only, storage is measured in terabyte (TB) increments and must range from 1 TB to 384 TB.
Select the Enable storage autoscalingcheckbox to let the system to expand the reserved storage up to three times. This is an optional field.
-
-
In the Backup retentionsection, enter the retention period for backups in the Backup retention period in daysfield. This number can range from 1 to 60 days.
Backups beyond the set retention period are automatically deleted. Automatic backups are managed by Oracle and billed separately , in addition to database storage.
-
In the Administrator credentialssection, confirm the administrator usernameand enter your password in the Passwordfield. Re-enter your password in the Confirm passwordfield to confirm.
-
In the Networkingsection, choose an access type to connect to the Autonomous Database:
-
Secure access from everywhere: Selecting this access type allows public network access using database credentials and a connection wallet.
When you select this access type, the mTLS authentication is automatically enabled as it is required for public network access.
-
Secure access from allowed IPs only: Selecting this access type restricts access to the specified IP addresses and CIDR blocks.
To set up this access type, do the following:
-
Create access endpoints.
You can set up multiple access endpoints, but you must define at least one. To set up an access endpoint, do the following:
- Click Add a network access.
- Select the IP notationtype. You can specify either an IP address or a CIDR block.
- Depending on the notation you selected, enter the IP address or the CIDR block for endpoints that you want to set up.
- Click Done.
Repeat these steps to set up more access endpoints.
-
(Optional) Select the Require mutual TLS (mTLS) authenticationcheckbox.
-
-
Private endpoint access only: Selecting this access type restricts access to a private endpoint within a VPC network.
To set up this access type, do the following:
-
From the Network projectlist, select the project that contains your ODB Network.
-
Select the ODB Network.
-
Select a Client subnet.
-
(Optional) In the Advanced network settingssection, you can provide a Private IP addressand a Hostname prefix.
-
(Optional) To enable public access, select the Allow public accesscheckbox and create access endpoints.
You can set up multiple access endpoints, but you must define at least one. To set up an access endpoint, do the following:
- Click Add a network access.
- Select the IP notationtype. You can specify either an IP address or a CIDR block.
- Depending on the notation you selected, enter the IP address or the CIDR block for endpoints that you want to set up.
- Click Done.
Repeat these steps to set up more access endpoints.
-
(Optional) Select the Require mutual TLS (mTLS) authenticationcheckbox.
-
-
-
In the Operational notifications and announcements contactsection, enter the email addresses for all contacts you want to receive notifications about this database.
-
In the Advanced settingssection, you can optionally modify the following settings:
-
Maintenance: this setting is set to Regularby default, which patches your database on a regular schedule. You can modify this setting to Earlywhich patches your database one week before the regular scheduled patch maintenance.
-
Management: this setting sets
AL32UTF8
as the default for the Character setandAL16UTF16
as the default for National character set. Use the drop-downs to modify these settings as necessary.
-
-
Click Createto create your database.
gcloud
Use the gcloud oracle-database autonomous-databases create
command to create a database.
gcloud
oracle
-
database
autonomous
-
databases
create
DATABASE_ID
\
--
project
=
PROJECT_ID
\
--
location
=
REGION
\
--
display
-
name
=
DISPLAY_NAME
\
--
database
=
DATABASE_NAME
\
--
admin
-
password
=
ADMIN_PASSWORD
\
--
odb
-
subnet
=
projects
/
ODB_NETWORK_PROJECT_ID
/
locations
/
REGION
/
odbNetworks
/
ODB_NETWORK_ID
/
odbSubnets
/
ODB_SUBNET_ID
\
--
properties
-
compute
-
count
=
COMPUTE_COUNT
\
--
properties
-
db
-
version
=
DATABASE_VERSION
\
--
properties
-
license
-
type
=
LICENSE_TYPE
\
--
properties
-
db
-
workload
=
WORKLOAD_TYPE
\
--
properties
-
data
-
storage
-
size
-
gb
=
STORAGE_SIZE
Replace the following:
- DATABASE_ID : a permanent identifier for your instance. The database ID can't be changed once set.
- PROJECT_ID : the ID of your Google Cloud project which contains the Autonomous Database.
- REGION : the region for your database. The region is permanent and can't be changed later. For a list of available regions, see Available configurations .
- DISPLAY_NAME : a name to identify your database. This name is displayed in the Google Cloud console. The name must be unique within your Google Cloud project.
-
DATABASE_NAME : a name for the database. Consider the following guidelines:
- Must begin with an alphabetic character.
- Contain up to 30 alphanumeric characters.
- Must not include special characters.
- Must be unique in your Oracle Cloud Infrastructure (OCI) tenancy.
- Not required if you're creating a cross-region disaster recovery standby instance or cross-region Autonomous Data Guard standby instance.
-
ADMIN_PASSWORD : the password for the default administrator user for your Autonomous Database.
-
For
odb-subnet
property, replace the following:- ODB_NETWORK_PROJECT_ID : the ID of your Google Cloud project which contains your ODB Network. If you're using a Shared VPC, then this is the ID of your host project.
- REGION : the region of your ODB Network.
- ODB_NETWORK_ID : the ID of your ODB Network.
- ODB_SUBNET_ID : the ID of your ODB Subnet.
-
COMPUTE_COUNT : the compute capacity for your database.
-
DATABASE_VERSION : the Oracle database version for your database.
-
LICENSE_TYPE : the license type associated with your Oracle Database@Google Cloud order. Only accepted values are
bring-your-own-license
orlicense-included
. -
WORKLOAD_TYPE : the workload type for your Autonomous Database that must be one of the following:
-
ajd
: Autonomous JSON Database -
apex
: Autonomous Database with Oracle APEX Application Development workload type -
dw
: Autonomous Data Warehouse database -
oltp
: Autonomous Transaction Processing database
-
-
STORAGE_SIZE : your preferred storage count. Storage can range from .02 TB to 384 TB and is measured in gigabyte (GB) increments.
For Data Warehouse workloads only, storage is measured in terabyte (TB) increments and must range from 1 TB to 384 TB.
API
To create an Autonomous Database, run the following curl
command:
curl -X POST \ -H "Authorization: Bearer $(gcloud auth print-access-token)" \ -H "Content-Type: application/json" \ "https://oracledatabase.googleapis.com/v1/projects/ PROJECT_ID /locations/ REGION /autonomousDatabases/ DATABASE_ID " -d \ '{ "database": " DATABASE_NAME ", "displayName": " DISPLAY_NAME ", "admin_password": " PASSWORD ", "odb_subnet": "projects/ ODB_NETWORK_PROJECT_ID /locations/ REGION /odbNetworks/ ODB_NETWORK_ID /odbSubnets/ ODB_SUBNET_ID ", "properties": { "licenseType": " LICENSE_TYPE ", "computeCount": COMPUTE_COUNT , "dbVersion": " DATABASE_VERSION ", "dbWorkload": " WORKLOAD_TYPE ", "dataStorageSizeTb": STORAGE_SIZE } }'
Replace the following:
- PROJECT_ID : the ID of your Google Cloud project in which to create the database.
- REGION : the region in which to create the database.
- DATABASE_ID : a unique identifier for your database.
-
DATABASE_NAME : a name for the database. Consider the following guidelines:
- Must begin with an alphabetic character.
- Contain up to 30 alphanumeric characters.
- Must not include special characters.
- Must be unique in your Oracle Cloud Infrastructure (OCI) tenancy.
- Not required if you're creating a cross-region disaster recovery standby instance or cross-region Autonomous Data Guard standby instance.
-
DISPLAY_NAME : a name for your database to be displayed in the Google Cloud console.
-
PASSWORD : the password for the default administrator user for your database.
-
For
odbSubnet
property, replace the following:- ODB_NETWORK_PROJECT_ID : the ID of your Google Cloud project which contains your ODB Network. If you're using a Shared VPC, then this is the ID of your host project.
- REGION : the region of your ODB Network.
- ODB_NETWORK_ID : the ID of your ODB Network.
- ODB_SUBNET_ID : the ID of your ODB Subnet.
-
LICENSE_TYPE : the license type associated with your Oracle Database@Google Cloud order. Only accepted values are
bring-your-own-license
orlicense-included
. -
COMPUTE_COUNT : the compute capacity for your database.
-
DATABASE_VERSION : the Oracle database version for your database.
-
WORKLOAD_TYPE : the workload type for your database. Following are the accepted values:
-
ajd
: Autonomous JSON Database -
apex
: Autonomous Database with Oracle APEX Application Development workload type -
dw
: Autonomous Data Warehouse database -
oltp
: Autonomous Transaction Processing database
-
-
STORAGE_SIZE : your preferred storage count. Storage can range from .02 TB to 384 TB and is measured in gigabyte (GB) increments.
For Data Warehouse workloads only, storage is measured in terabyte (TB) increments and must range from 1 TB to 384 TB.
C#
Go
Java
Node.js
PHP
Python
Ruby
What's next
- Learn how to manage or delete an Autonomous Database.
- Configure Identity and Access Management roles for an instance.
- Use monitoring metrics to monitor your instances.