Creating an Autonomous Database on Shared Exadata Infrastructure

This topic describes how to provision a new Autonomous Database on Shared Exadata infrastructure using the Oracle Cloud Infrastructure Console or the API. Autonomous Databases can be provisioned on Dedicated Exadata infrastructure or Shared Exadata infrastructure. Your database can by optimized for either data warehouse, JSON, transaction processing, or APEX service workloads.

To provision an Always Free Autonomous Database, see To create an Always Free Autonomous Database. For more information on the Free Tier, see Oracle Cloud Infrastructure Free Tier.

For Oracle By Example tutorials on provisioning Autonomous Databases, see Provisioning Autonomous Transaction Processing and Provisioning Autonomous Data Warehouse Cloud.

Prerequisites

  • To create an Autonomous Database, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in. See Authentication and Authorization for more information on user authorizations for the Oracle Cloud Infrastructure Database service.

    Tip

    See Let database and fleet admins manage Autonomous Databases for sample Autonomous Database policies. See Details for the Database Service for detailed information on policy syntax.
  • For information on additional prerequisites for provisioning an Autonomous Transaction Processing database, see What Do You Need? Likewise, for information on additional prerequisites for provisioning an Autonomous Data Warehouse, see What Do You Need?
  • To create an Autonomous Transaction Processing database on Dedicated Exadata infrastructure, you must first provision the infrastructure and at least one Autonomous Container Database. For more information, see Creating an Autonomous Exadata Infrastructure Resource and Creating an Autonomous Container Database.

Using the Oracle Cloud Infrastructure Console

To create an Autonomous Database on shared Exadata infrastructure
Tip

For Autonomous Databases with shared Exadata infrastructure, Oracle Cloud Infrastructure uses per-second billing. This means that CPU and storage usage is billed by the second, with a minimum usage period of one minute.
  1. Open the navigation menu. Click Oracle Database. Under Autonomous Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Provide the following information for the Autonomous Database:

    • Compartment: Select the compartment of the Autonomous Database.
    • Display name: A user-friendly description or other information that helps you easily identify the resource. The display name does not have to be unique. Avoid entering confidential information.
    • Database name: The database name must consist of letters and numbers only, starting with a letter. The maximum length is 14 characters.

    Note

    You cannot use the same database name concurrently for an Autonomous Data Warehouse, an Autonomous JSON, or an Autonomous Transaction Processing database for databases using shared Exadata infrastructure. Names associated with databases terminated within the last 60 days cannot be used when creating a database.
  3. Choose the Shared Infrastructure deployment type.
    Note

    If you choose JSON or APEX as your workload type, then Shared Infrastructure is the only available deployment type.
  4. Configure the database:

    • Always Free: Use this selector to show only Always Free configuration options if you are provisioning an Always Free Autonomous Database. See Overview of the Always Free Autonomous Database for more information.
      Note

      This option is not available for either JSON or APEX workload types.
    • Choose database version: Select a database version from the available versions.
    • OCPU count: Specify the number of cores for your Autonomous Database. The actual number of available cores is subject to your tenancy's service limits.

      Auto scaling: allows Autonomous Database to automatically increase the number of CPU cores by up to three times the assigned CPU core count value, depending on demand for processing. The auto scaling feature reduces the number of CPU cores when additional cores are not needed. For databases with up to 42 assigned cores, you can increase the maximum number of cores available through auto scaling by increasing the CPU core count value. See CPU Scaling for more information.

      Note

      The maximum number of cores that are available to any Autonomous Database database not using dedicated Exadata infrastructure is 128, regardless of whether auto scaling is enabled or not. This means that database with a CPU core count of 64 could auto scale up to two times the assigned number of cores (2 x 64 = 128). A database with 42 cores (or fewer) could auto scale up to three times the assigned number (3 x 42 = 126). For billing purposes, the database service determines the average number of CPUs used per hour.
    • Storage (TB): Specify the storage you wish to make available to your Autonomous Database, in terabytes.
    • Enable preview version: (This option only displays during periods when a preview version of Autonomous Database is available) Select this option to provision the database with an Autonomous Database preview version. Preview versions of Autonomous Database are made available for limited periods for testing purposes. Do not select this option if you are provisioning a database for production purposes or if you will need the database to persist beyond the limited availability period of the preview version.

  5. Create administrator credentials: Set the password for the Autonomous Database ADMIN user by entering a password that meets the following criteria. You use this password when accessing the Autonomous Database service console and when using a SQL client tool.

    Password criteria:

    • Contains from 12 to 30 characters and includes at least one uppercase letter, one lowercase letter, and one numeric character.
    • Does not contain the string "admin", regardless of case
    • Is not one of the last four passwords used for the ADMIN user
    • Does not contain the double quotation mark (")
    • Cannot be the same password that was set less than 24 hours ago
  6. Choose the type of network access.

  7. Choose a license type. Your choice affects metering for billing. You have the following options:

    • Bring Your Own License (BYOL):  Bring my existing database software licenses to the database cloud service.
    • License Included: Subscribe to new database software licenses and the Database cloud service.
      Note

      If you choose either JSON or APEX as your workload type, then License Included is the only available license type.
  8. Enter the valid email addresses of contacts to receive notifications of updates that occur in Oracle Cloud Infrastructure, including database updates. Click the Add Contact button to add up to 10 email addresses.
  9. Click Show Advanced Options to configure the following:

    • Tags: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
    • Patch level: By default the patch level is Regular. Select Early to configure the instance with the early patch level. Note: You cannot change the patching cycle after you provision an instance. See Setting the Patch Level for more information.
    • Encryption Keys:
      1. Click the Encryption Key tab.
      2. Select Encrypt using customer-managed keys. You must have a valid encryption key in Oracle Cloud Infrastructure Vault service. See Let security admins manage vaults, keys, and secrets.
        Note

        Oracle only supports AES-256 encryption keys.
      3. Choose a vault from the Vault in compartment drop-down. You can change the compartment by clicking the CHANGE COMPARTMENT link.
      4. Select an encryption key from the Master encryption key in compartment drop-down. You can change the compartment containing the encryption key you want to use by clicking the CHANGE COMPARTMENT link.
  10. Click Create Autonomous Database.

WHAT NEXT?

To create an Always Free Autonomous Database
Note

An Always Free Autonomous Database cannot be created in a security zone compartment. See the Security Zone Policies topic for a full list of policies that affect Database service resources.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous Transaction Processing, or Autonomous JSON Database. To provision APEX Application Development, you can click and of the previously mentioned workload types, or navigate to Developer Services, and then click APEX Application Development.
  2. Provide the following information for the Autonomous Database:

    • Compartment: Select the compartment of the Autonomous Database.
    • Display name: A user-friendly description or other information that helps you easily identify the resource. The display name does not have to be unique. Avoid entering confidential information.
    • Database name: The database name must consist of letters and numbers only, starting with a letter. The maximum length is 14 characters.

  3. Choose the Shared Infrastructure deployment type.
  4. Configure the database:

    • Always Free: Move this selector to the right so that the provisioning workflow shows only the Always Free configuration options. Note that the Core CPU count and Storage configuration fields are disabled when provisioning an Always Free Autonomous Database. Your database will have 1 OCPU, 8 GB of memory, and 20 GB of storage.
    • Choose database version: Select a database version from the available versions.
      Note

      You can select only the current database version or a newer one. You cannot downgrade to an older database version.
  5. Create administrator credentials: Set the password for the Autonomous Database ADMIN user by entering a password that meets the following criteria. You use this password when accessing the Autonomous Database service console and when using a SQL client tool.

    Password criteria:

    • Contains from 12 to 30 characters and includes at least one uppercase letter, one lowercase letter, and one numeric character.
    • Does not contain the string "admin", regardless of case
    • Is not one of the last four passwords used for the ADMIN user
    • Does not contain the double quotation mark (")
    • Cannot be the same password that was set less than 24 hours ago
  6. Network access for Always Free Autonomous Database is Allow secure access from anywhere. This option provides access using a public endpoint that you secure with an access control list (ACL). Use this option if you need to access your database from the internet or your on-premises network. See Adding an Access Control List (ACL) to an Autonomous Database with a Public Endpoint for more information on creating an ACL.

  7. Click Show Advanced Options to configure the following:

    • Tags: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
    • Patch level: By default the patch level is Regular. Select Early to configure the instance with the early patch level. Note: You cannot change the patching cycle after you provision an instance. See Setting the Patch Level for more information.
    • Encryption Keys:
      1. Click the Encryption Key tab.
      2. Select Encrypt using customer-managed keys. You must have a valid encryption key in Oracle Cloud Infrastructure Vault service. See Let security admins manage vaults, keys, and secrets.
        Note

        Oracle only supports AES-256 encryption keys.
      3. Choose a vault from the Vault in compartment drop-down. You can change the compartment by clicking the CHANGE COMPARTMENT link.
      4. Select an encryption key from the Master encryption key in compartment drop-down. You can change the compartment containing the encryption key you want to use by clicking the CHANGE COMPARTMENT link.
  8. Click Create Autonomous Database.
Note

The following naming restrictions apply to Autonomous Transaction Processing and Autonomous Data Warehouse databases using Shared Exadata Infrastructure:

  • Names associated with databases terminated within the last 60 days cannot be used when creating a new database.
  • A database name cannot be used concurrently for two Autonomous Databases, regardless of workload type.

WHAT NEXT?

For More Information

Autonomous Database: Autonomous Transaction Processing and Autonomous Data Warehouse

Autonomous JSON Database

Oracle APEX Application Development