Create databases

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

Create an Autonomous Database

Console

  1. Go to the Autonomous Database Service page in the Google Cloud console.

    Go to Autonomous Database Service

  2. Click Create.

  3. In the Instance details section, complete the following:

    1. Enter an Instance ID for your database. This field is permanent and can't be modified once created.

    2. Enter a Database name for 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

    3. Enter a Database display name to help identify your database.

    4. Select a Region for your database from the drop-down. The region choice is permanent and can't be changed later.

    5. 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.

  4. In the Workload configuration section, 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.

  5. In the Database configuration section, complete the following:

    1. Select your License type from the drop-down. If you choose Bring Your Own License (BYOL), then select the edition from the Oracle Database Edition drop-down.

    2. Select a database version in the Choose database version drop-down.

    3. In the ECPU count field, enter your preferred count. The EPCU count can range from 2 to 512.

      Select the Enable compute autoscaling checkbox to let the system to expand the specific ECPU count up to three times if the demand increases. This is an optional field.

    4. 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 autoscaling checkbox to let the system to expand the reserved storage up to three times. This is an optional field.

  6. In the Backup retention section, enter the retention period for backups in the Backup retention period in days field. 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.

  7. In the Administrator credentials section, confirm the administrator username and enter your password in the Password field. Re-enter your password in the Confirm password field to confirm.

  8. In the Networking section, define the network configuration for the Autonomous Database by completing the following:

    1. In the Associated network drop-down, select the network you want to use. You can only choose one network from the list.

    2. In the Configure networking for your database section, enter the IPv4 subnet range for your Autonomous Database. The database subnet range can't overlap with the subnet range of the VPC network project you're using. IPv6 addresses aren't supported.

      Address ranges must use a valid CIDR notation (for example, 10.10.10.0/24). For more information on how to select client IP ranges, see Requirements for IP Address space.

    3. In the Advanced network settings section, you can optionally provide a Private IP address or a Hostname prefix.

      Check the Require mutual TLS (mTLS) authentication box if you want to require mTLS to authenticate connections to your Autonomous Database.

  9. In the Operational notifications and announcements contact section, enter the email addresses for all contacts you want to receive notifications about this database.

  10. In the Advanced settings section, you can optionally modify the following settings:

    1. Maintenance: this setting is set to Regular by default, which patches your database on a regular schedule. You can modify this setting to Early which patches your database one week before the regular scheduled patch maintenance.

    2. Management: this setting sets AL32UTF8 as the default for the Character set and AL16UTF16 as the default for National character set. Use the drop-downs to modify these settings as necessary.

      Note that the AL32UTF8 value is recommended by default for Character set.

  11. Click Create to 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
--location=REGION_ID
--display-name=DISPLAY_NAME
--network=NETWORK_PROJECT_NAME
--database=DATABASE_NAME
--admin-password=ADMIN_PASSWORD
--cidr=CIDR_RANGE
--properties-compute-count=COMPUTE_COUNT
--properties-db-version=DATABASE_VERSION
--properties-license-type=LICENSE_TYPE
--properties-db-workload=WORKLOAD_TYPE

Replace the following:

  • DATABASE_ID: a permanent identifier for your instance. The database ID can't be changed once set.
  • REGION_ID: 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.

  • NETWORK_PROJECT_NAME: the name of the network from your network VPC project that you'd like to use for your cluster. The name must use following format:

    projects/PROJECT_ID/locations/global/NETWORK_NAME

    To create a VPC network project, see Configure VPC network.

  • DATABASE: the name of your Autonomous Database. The name must be unique within your project, must begin with a letter, and can only contain a maximum of 30 alphanumeric characters.

  • ADMIN_PASSWORD: the password for the default administrator user for your Autonomous Database.

  • CIDR_RANGE: the subnet range for your Autonomous Database. The subnet range must use CIDR notation, be IPv4 only, and not overlap with the subnet range of your Google Cloud network project.

  • COMPUTE_COUNT: the compute capacity for your database.

  • DATABASE_VERSION: the Oracle database version for your database.

  • 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

What's next