Managing Autonomous Databases

An Autonomous Database resource is a user database. When you create an Autonomous Database, you choose the Autonomous Container Database for it and you specify "Data Warehouse" or "Transaction Processing" as its workload type to create an Autonomous Data Warehouse database or an Autonomous Transaction Processing database.

You can create hundreds of Autonomous Databases on an Exadata Infrastructure. As described in Available Exadata Infrastructure Hardware Shapes, the maximum is determined by the capacity of your Exadata Infrastructure hardware.

Create an Autonomous Database

Follow these steps to create an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. Click Create Autonomous Database.
  4. In the Create Autonomous Database dialog, enter the following:

    Basic Database Information

    • 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. Avoid entering confidential information.

    Workload Type

    Select the desired workload type.
    • Data Warehouse
    • Transaction Processing
    See About Autonomous Database for information about each workload type.

    Autonomous Container Database: Select an Autonomous Container Database.

    Compartment: Specify the compartment containing the Autonomous Container Database you wish to use.

    Configure the database

    • OCPU Count: Specify the number of OCPU for your database. The total number of cores available to all databases within the Autonomous Exadata Infrastructure depends on the infrastructure shape and what is already allocated to other Autonomous Databases.

      Create Autonomous Databases with less than 1 OCPU count using fractional units. Fractional OCPU supports up to 10 Autonomous Databases per core with the smallest OCPU count being 0.1 and up to 0.9 fractional OCPU with an increment of 0.1. Fractional OCPU is for less than one OCPU only. For OCPU equal to or greater than one, the increment must be in integer.

      • Default: 1
      • Minimum: 0.1
      • Maximum: Set by quota
      • Increment between 0.1 and 0.9: 0.1
      • Increment between 1 and maximum: 1

      Auto scaling: Deselect Auto Scaling to disable auto scaling. By default auto scaling is enabled to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand.

      Fractional OCPU auto-scaling behaves the same way as integer OCPU auto-scaling. However, there is a subtle difference between fractional OCPU auto-scaling and integer OCPU auto-scaling behaviors. Fractional OCPU auto-scaling will scale three times the base OCPU and then round it off to a whole number.

      For example, 0.1 OCPU can auto-scale up to 1 OCPU, 0.5 OCPU can auto-scale up to 2 OCPU, 0.7 OCPU can auto-scale up to 3 OCPU, and so on.

    • Storage (GB): Specify the storage you wish to make available to your Autonomous Database, in GB. The available storage depends on the infrastructure shape and what is already consumed by other Autonomous Databases.
      • Default: 1024 GB
      • Minimum: 32 GB
      • Increment: 1 GB

    Administrator Credentials

    Set the password for the Autonomous Database Admin user by entering a password that meets the following criteria. Use this password when accessing the Autonomous Database service console and when using an SQL client tool.

    • Contains from 12 to 30 characters
    • Contains at least one lowercase letter
    • Contains at least one uppercase letter
    • Contains at least one number
    • Does not contain the double quotation mark (")
    • Does not contain the string "admin", regardless of casing
    Configure network access You can optionally create an ACL during database provisioning, or at any time thereafter.
    • Select the Enable database level access control checkbox.
    • Click Access Control Rule.
      Note

      The database-level access control will be enabled without any IP addresses in the access control list. Enabling an access control list with an empty list of IP addresses makes the database inaccessible to all clients

    • Specify the following types of addresses in your list by using the IP notation type drop-down selector:
      • IP Address allows you to specify one or more individual public IP addresses. Use commas to separate your addresses in the input field.
      • CIDR Block allows you to specify one or more ranges of public IP addresses using CIDR notation. Use commas to separate your CIDR block entries in the input field.

    Advanced Options:

    • Encryption Key: ADB inherits encryption settings from the parent ACD. If the parent ACD is configured for customer-managed OKV-based encryption, then the child ADB will also have a TDE Master Key generated and managed in the same OKV wallet used to store ACD master keys. Additionally, any backups taken on the Autonomous Database will have the OKV based key associated with it.

    • Management: Choose a Character Set and National Character from the drop-down list.

    • Tags: Optionally, you can apply tags. If you have permission to create a resource, you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator. Avoid entering confidential information.

  5. Click Create Autonomous Database.
    Note

    The following naming restrictions apply to Autonomous Transaction Processing and Autonomous Data Warehouse databases:

    • 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 both an Autonomous Data Warehouse and an Autonomous Transaction Processing database.

Manage Access Control List of an Autonomous Database

Enabling an access control list with an empty list of IP addresses makes the database inaccessible.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Under Network in the database details, find the Access Control List field and click Edit to enable or disable your database-level access control and make changes to the ACL rules.
    Note

    Autonomous Data Guard enabled Automonous databases:
    • You can only view ACLs for standby databases.
    • You can reset ACL for both the primary and standby databases from the primary database details page. You cannot configure ACL from the standby database details page.
  5. In the Access Control List dialog, add or modify entries, as applicable.

    If you are editing an ACL, the ACL's existing entries display in the Access Control List dialog. Do not overwrite the existing values unless you intend to replace one or more entries. To add new ACL entries, click + Access Control Rule.

    You can specify the following types of addresses in your list by using the IP notation type drop-down selector:

    • IP Address allows you to specify one or more individual public IP addresses. Use commas to separate your addresses in the input field.
    • CIDR Block allows you to specify one or more ranges of public IP addresses using CIDR notation. Use commas to separate your CIDR block entries in the input field.

    Click + Access Control Rule to add additional access rules to your list.

    To remove an access control rule, simply delete the entry from the list. Deleting all access control rules from the ACL will render the database inaccessible because the allow list is empty.

    To disable the database-level access control configuration, clear the Enable database level access control checkbox. Once ACL is disabled and the configuration is saved, all the access control rules are removed from the ACL and no longer applicable.

  6. Click Save Changes.

    If the Lifecycle State is Available when you click Save, the Lifecycle State changes to Updating until the ACL update is complete. The database is still up and accessible, there is no downtime. When the update is complete the Lifecycle State returns to Available and the network ACL rules from the access control list are in effect.

View a List of Autonomous Databases

Follow these steps to view a list of autonomous databases on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.

View Details of an Autonomous Database

Follow these steps to view detailed information about an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to view details.

    On the Autonomous Container Database Details page encryption details are displayed under Encryption.

    If you have chosen customer-managed keys while creating the database, then you will see a link to the Encryption Key Store and OKV Wallet Name. Click the Key Store link to view details.

    If you have chosen Oracle-managed keys while creating the database, then you will not see the link to Encryption Key Store and OKV Wallet Name.

Rotate ADB Encryption Key

Follow these steps to rotate the TDE Master key. On key rotation, the ADB life cycle goes through the regular updating state and returns to available.

You can rotate the TDE Master key as many times as you want. The new TDE Master Key is stored in the same wallet in which the previous key was stored. Rotating the TDE Master Key leads to the new key being generated in OKV and assigned to this database. You can view all of the keys in OKV.

Note

You can rotate both Oracle-managed and customer-managed encryption keys.

  1. Open the navigation menu. Under Oracle Database, click Exadata Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to view details.
  4. On the Autonomous Database Details page, from the More Actions drop-down list, select Rotate Encryption Key.
  5. On the Rotate Encryption Key dialog, click Rotate Encryption Key.

Set the Password of an Autonomous Database's ADMIN User

Follow these steps to set the ADMIN database user's password for an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to administer.
  4. From the More Actions drop-down list, select Admin Password.
    The Admin Password dialog opens.
  5. Enter a password for the Autonomous Database.

    The password must meet the following criteria:

    • Contains from 12 to 30 characters
    • Contains at least one lowercase letter
    • Contains at least one uppercase letter
    • Contains at least one number
    • Does not contain the double quotation mark (")
    • Does not contain the string "admin", regardless of case
    • Is not one of the last four passwords used for the database
    • Is not a password you previously set within the last 24 hours
  6. Enter the password again in the Confirm Password field.
  7. Click Update.

Scale the CPU Core Count or Storage of an Autonomous Database

Follow these steps to scale the CPU core count or storage an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system up or down.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to view details.
  4. Click Scale Up/Down.
  5. Enter a new value for CPU Core Count or Storage.
    • OCPU Count: Specify the number of OCPU for your database. The total number of cores available to all databases within the Autonomous Exadata Infrastructure depends on the infrastructure shape and what is already allocated to other Autonomous Databases.

      The selected OCPU count is validated against a list of provisionable OCPUs, and if the database can not be scaled up to the chosen OCPU count, you will be provided with the two nearest provisionable OCPU values.

      Based on the resource utilization on each node; not all the values of the available OCPUs can be used to provision or scale Autonomous Databases. For example, suppose you have 20 OCPUs available at the AVMC level, not all the values from 1 to 20 OCPUs can be used to provision or scale Autonomous Databases depending on the resource availability at the node level. The list of OCPU values that can be used to provision or scale an Autonomous Database is called Provisionable OCPUs.

      On the console, when you try to provision or scale an Autonomous Database, the OCPU count will be validated against the list of provisionable OCPUs, and if the value is not provisionable, you will be provided with the two nearest provisionable OCPU values. Alternatively, if you want to see the complete list of provisionable OCPU values for an Autonomous Exadata VM Cluster, you can use the following API:

      GetAutonomousDatabase returns a list of provisionable OCPU values that can be used for scaling a given Autonomous Database. See GetAutonomousDatabase for more details.

      The default is no change. For databases that do not need a full core, you can increment the OCPU value from 0.1 to 0.9 (in increments of 0.1). For databases using 1 or more OCPU cores, you must increment the number of assigned OCPU by one or more full cores. For example, you cannot assign 3.5 OCPU to a database. The next available number of OCPU above 3 is 4.

      • Default: Current value
      • Minimum: 0.1
      • Maximum: Set by quota
      • Increment between 0.1 and 0.9: 0.1
      • Increment between 1 and maximum: 1
    • Auto scaling: Deselect Auto Scaling to disable auto-scaling. By default, auto-scaling is enabled to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand.

      Fractional OCPU auto-scaling behaves the same way as integer OCPU auto-scaling. However, there is a subtle difference between fractional OCPU auto-scaling and integer OCPU auto-scaling behaviors. Fractional OCPU auto-scaling will scale three times the base OCPU and then round it off to a whole number.

      For example, 0.1 OCPU can auto-scale up to 1 OCPU, 0.5 OCPU can auto-scale up to 2 OCPU, 0.7 OCPU can auto-scale up to 3 OCPU, and so on.

    • Storage (GB): Specify the storage you wish to make available to your Autonomous Database, in GB. The available storage depends on the infrastructure shape and what is already consumed by other Autonomous Databases.
      • Default: Current value
      • Minimum: 32 GB
      • Increment: 1 GB
  6. Click Update.

Enable or Disable Auto Scaling for an Autonomous Database

Oracle Autonomous Database on Oracle Exadata Database Service on Cloud@Customer systems provides an auto scaling feature that automatically increases the number of cores an automonomous database during periods of increased demand and, as demand returns to normal, automatically decreases the number of cores down to the databases's base number.

Note the following points regarding the auto scaling feature:

  • With auto scaling enabled, the database can use up to three times more CPU and IO resources than specified by the number of OCPUs currently shown in the Scale Up/Down dialog.
  • If auto scaling is disabled while more CPU cores are in use than the database's currently assigned number of cores, then Autonomous Database scales the number of CPU cores in use down to the assigned number.
  • Enabling auto scaling does not change the concurrency and parallelism settings for the predefined services.

Follow these steps to enable or disable auto scaling for an autonomous database.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to view details.
  4. Click Scale Up/Down.
  5. Check Auto Scaling to enable the auto scaling feature, or uncheck Auto Scaling to disable the feature.
  6. Click Update.

Move an Autonomous Database to Another Compartment

Follow these steps to move an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system from one compartment to another compartment.

Note

  • To move an autonomous database you must have the right to manage it in its current compartment and in the compartment you are moving it to.
  • As soon as you move an autonomous database to a different compartment, the policies that govern the new compartment apply immediately and affect access to the autonomous database. Therefore, both your and other Oracle Cloud users' access to it may change, depending on the policies governing the user account's access to resources. For example, a user may lose the ability to manage the autonomous databae, given its new compartment.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to move.
  4. From the More Actions drop-down list, select Move Resource.
  5. Select the new compartment.
  6. Click Move Resource.

Stop or Start an Autonomous Database

Follow these steps to stop or start an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to view details.
  4. Click Stop (or Start).

    When you stop your Autonomous Database, billing stops for CPU usage. Billing for storage continues when the database is stopped.

  5. Confirm that you want to stop or start your Autonomous Database in the confirmation dialog.
Note

Stopping your database has the following consequences:

  • On-going transactions are rolled back.
  • You will not be able to connect to your database using database clients or tools.

Restart an Autonomous Database

To resolve some autonomous database issues with minimal downtime on Exadata Database Service on Cloud@Customer systems, you can restart the database.

Restarting an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system is equivalent to manually stopping and then starting the database. Using restart allows you to minimize downtime and requires only a single action.

Follow these steps to restart an autonomous database.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to restart.
  4. Click Restart.
  5. Confirm that you want to restart your Autonomous Database in the confirmation dialog.
    The system stops and then immediately starts your database.

Back Up an Autonomous Database Manually

Oracle Autonomous Database automatically backs up autonomous databases on an Oracle Exadata Database Service on Cloud@Customer system. In addition, you can manually back up an autonomous database should the need arise.
Note

During the backup operation, your autonomous database remains available. However, lifecycle management operations such as stopping it, scaling it, or terminating it are disabled.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to back up.
  4. On the Details page, under Resources, click Backups.
  5. Click Create Manual Backup.
  6. In the Create Manual Backup dialog, enter a name for your backup. Avoid entering confidential information.
  7. Click Update.
    The backup operation begins. This operation may take several hours to complete, depending on the size of the database.
Optionally, you can check the state of your backup in the list of backups on the database details page. For some states, an information icon is displayed to provide additional details regarding the state or ongoing operations like deletions. The backup has one of the following states:
  • Creating
  • Active
  • Deleting
  • Deleted
  • Failed

Restore an Autonomous Database

You can use any existing manual or automatic backup to restore and recover an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system, or you can restore and recover the database to any point in time during the retention period of its automatic backups.

Note

Restoring an autonomous database puts the database in the unavailable state during the restore operation. You cannot connect to a database in this state. The only lifecycle management operation supported in the unavailable state is terminate.

Restore from a Backup

Follow these steps to restore an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system from a specific backup.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you want to clone.
  4. From the More Actions drop-down list, select Restore.
  5. Specify the date range for a list of backups to display.
  6. Select the backup.
  7. Click Restore.

Restore to a Point in Time

Follow these steps to restore an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system to a specific point in time.
  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you want to restore.
  4. From the More Actions drop-down list, select Restore.
  5. Click Specify Timestamp.
  6. Enter a timestamp.
    Your Autonomous Database decides which backup to use for faster recovery. The timestamp input allows you to specify precision to the seconds level (YYYY-MM-DD HH:MM:SS GMT).
  7. Click Restore.

Clone an Autonomous Database

Follow these steps to clone an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.

You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics. To clone only the database schema of your source database, choose the metadata clone option.

Clone Types

The clone feature offers the following two types of Autonomous Database clones:
  • The full-clone option creates a database that includes the metadata and data from the source database.
  • The metadata-clone option creates a database that includes only the metadata from the source database.

Steps

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you want to clone.
  4. From the More Actions drop-down list, select Create Clone.
  5. On the Create Autonomous Database Clone page, provide the following information:

    In the Clone Type section, select the type of clone you want to create. Choose either Full Clone or Metadata Clone.

    Clone Source: The clone source selection allows you to specify whether the clone is created from a running database or from a database backup. Select one of the following options:
    • Clone from a database instance: Creates a clone of a running database as it exists at the current moment.
    • Clone from a backup: Creates a clone from a database backup. If you choose this option, select one of the following options:
      • Specify a timestamp: Creates a point-in-time clone. The timestamp has to be between the first and latest backups of the database.
      • Select from a list of backups: Creates a clone using all data from the specified backup. To limit your list of backups to a specific date range, enter the starting date in the From field and the ending date in the To field.

    Provide basic information for the Autonomous Database.

    • Choose a compartment: Your current compartment is the default selection but you can select a different compartment in which to create the clone from the drop-down list.
    • Source database name: The name of the source database displays in the read-only Source database name field.
    • Display name: Enter a description or other information to identify the database clone. You can change the display name any time and it does not have to be unique. Avoid entering confidential information.
    • Database name: Enter a database name for the clone that contains only letters and numbers, begins with a letter. Avoid entering confidential information.
    • Three additional fields are displayed if you opt to clone from a backup.
      • Exadata Infrastructure: You can choose to create the database clone in the same Exadata Infrastructure where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
      • Autonomous Exadata VM Cluster: You can choose to create the database clone in the same Autonomous Exadata VM Cluster where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
    • Autonomous Container Database: You can choose to create the database clone in the same compartment and container database as the source database, or you can choose a different compartment by clicking CHANGE COMPARTMENT, and a different container database by choosing one from the drop-down list.

    Configure the database

    • OCPU Count: Specify the number of OCPU for your database. The total number of cores available to all databases within the Autonomous Exadata Infrastructure depends on the infrastructure shape and what is already allocated to other Autonomous Databases.

      The selected OCPU count is validated against a list of provisionable OCPUs, and if the database can not be scaled up to the chosen OCPU count, you will be provided with the two nearest provisionable OCPU values.

      You can use the GetAutonomousContainerDatabase API to get a complete list of provisionable OCPU values.

      The default is 1. However, you can assign a fractional OCPU value from 0.1 to 0.9 (in increments of 0.1) to databases that do not need a full OCPU. For databases that need 1 or more OCPU cores, you must specify the number of assigned OCPUs as an integer. For example, you cannot assign 3.5 OCPU to a database. The next available number of OCPU above 3 is 4.

      • Default: 1
      • Minimum: 0.1
      • Maximum: Set by quota
      • Increment between 0.1 and 0.9: 0.1
      • Increment between 1 and maximum: 1
    • Storage (GB): Specify the amount of storage, in GB, that you want to make available to your cloned Autonomous Database, and it depends on the storage available to use. For full clones, the size of the source database determines the minimum amount of storage you can make available.
      • Default: 1024 GB
      • Minimum: 32 GB
      • Increment: 1 GB
    • Auto scaling: Enabling autoscaling allows the system to automatically use up to three times more CPU and I/O resources to meet workload demand.

    Create administrator credentials

    Set the password for the Autonomous Database administrator user by entering a password that meets the following criteria.

    • Password cannot be one of the three most recently used passwords of the source database
    • Between 12 and 30 characters long
    • Contains at least one lowercase letter
    • Contains at least one uppercase letter
    • Contains at least one number
    • Does not contain the double quotation mark (")
    • Does not contain the string "admin", regardless of casing

    Use this password when accessing the service console and when using a SQL client tool.

    Configure Network Access

    You can change the access control list to enable or disable database-level access control or add or modify entries to the access control list.

    • Click Modify Access Control.

    • Select the Enable database level access control check box.

    • Click Access Control Rule.

      Note: The database-level access control will be enabled without any IP addresses in the access control list. Enabling an access control list with an empty list of IP addresses makes the database inaccessible to all clients.

    • Specify the following types of addresses in your list by using the IP notation type drop-down selector:
      • IP Address allows you to specify one or more individual public IP addresses. Use commas to separate your addresses in the input field.

      • CIDR Block allows you to specify one or more ranges of public IP addresses using CIDR notation. Use commas to separate your CIDR block entries in the input field.
    Advanced Options:
    • Encryption Key:
      • Clone from a database instance: The source and the target ACD must be the same Keystore type. When the source is OKV, the target must also be the same OKV destination.

      • Clone from a backup: The source and the target ACDs can be different Keystore types. When the source is OKV, the target must also be the same OKV destination.
    • Management: Choose a Character Set and National Character from the drop-down list.
    • Tags: Optionally, you can apply tags. If you have permission to create a resource, you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator. Avoid entering confidential information.
  6. Click Create Autonomous Database Clone.

The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:

  • The new clone displays the Provisioning lifecycle state until the provisioning process completes.
  • The source database remains in the Available lifecycle state.
  • Backups associated with the source database are not cloned for either the full-clone or the metadata-clone option.

The Clone source is displayed in the General Information section of the cloned database details page. Click the name to view details of the source database. Note that if the source database is deleted, then this key/value pair is not displayed.

Clone an Autonomous Database Backup

Follow these steps to clone an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.

You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics. To clone only the database schema of your source database, choose the metadata clone option.

Clone Types

The clone feature offers the following two types of Autonomous Database clones:
  • The full-clone option creates a database that includes the metadata and data from the source database.
  • The metadata-clone option creates a database that includes only the metadata from the source database.

Steps

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you want to clone.
  4. Under Resources, click Backups.
  5. In the list of backups, find the backup that you want to clone, click the action icon (three dots), and then click Create Clone.
  6. On the Create Autonomous Database Clone page, provide the following information:

    In the Clone Type section, select Full Clone.

    Clone Source: The clone source section displays the source backup details.

    Provide basic information for the Autonomous Database.

    • Choose a compartment: Your current compartment is the default selection but you can select a different compartment in which to create the clone from the drop-down list.
    • Source database name: The name of the source database displays in the read-only Source database name field.
    • Display name: Enter a description or other information to identify the database clone. You can change the display name any time and it does not have to be unique. Avoid entering confidential information.
    • Database name: Enter a database name for the clone that contains only letters and numbers, begins with a letter. Avoid entering confidential information.
    • Exadata Infrastructure: You can choose to create the database clone in the same Exadata Infrastructure where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
    • Autonomous Exadata VM Cluster: You can choose to create the database clone in the same Autonomous Exadata VM Cluster where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
    • Autonomous Container Database: You can choose to create the database clone in the same compartment and container database as the source database, or you can choose a different compartment by clicking CHANGE COMPARTMENT, and a different container database by choosing one from the drop-down list.
      Note

      When the target Autonomous Exadata VM Cluster is the same as the source, then the database name cannot be the same as the source database name.

    Configure the database

    • OCPU Count: There is a minimum requirement of 2 OCPUs for an ADB clone from Backup. After the clone, you can resize to a lower value if needed.
      Note

      The time taken to clone an ADB depends on the OCPU Count and the network bandwidth between the Backup Destination and the target ACD.

      Specify the number of OCPU for your database. The total number of cores available to all databases within the Autonomous Exadata Infrastructure depends on the infrastructure shape and what is already allocated to other Autonomous Databases.

      The selected OCPU count is validated against a list of provisionable OCPUs, and if the database can not be scaled up to the chosen OCPU count, you will be provided with the two nearest provisionable OCPU values.

      You can use the GetAutonomousContainerDatabase API to get a complete list of provisionable OCPU values.

      The default is 1. However, you can assign a fractional OCPU value from 0.1 to 0.9 (in increments of 0.1) to databases that do not need a full OCPU. For databases that need 1 or more OCPU cores, you must specify the number of assigned OCPUs as an integer. For example, you cannot assign 3.5 OCPU to a database. The next available number of OCPU above 3 is 4.

      • Default: 2
      • Minimum: 2
      • Maximum: Set by quota
    • Storage (GB): Specify the amount of storage, in GB, that you want to make available to your cloned Autonomous Database, and it depends on the storage available to use.
      • Default/Minimum: Allocated storage of the source database
      • Increment: 1 GB
    • Auto scaling: Enabling autoscaling allows the system to automatically use up to three times more CPU and I/O resources to meet workload demand.

    Create administrator credentials

    Set the password for the Autonomous Database administrator user by entering a password that meets the following criteria.

    • Password cannot be one of the three most recently used passwords of the source database
    • Between 12 and 30 characters long
    • Contains at least one lowercase letter
    • Contains at least one uppercase letter
    • Contains at least one number
    • Does not contain the double quotation mark (")
    • Does not contain the string "admin", regardless of casing

    Use this password when accessing the service console and when using a SQL client tool.

    Configure Network Access

    You can change the access control list to enable or disable database-level access control or add or modify entries to the access control list.

    • Click Modify Access Control.

    • Select the Enable database level access control check box.

    • Click Access Control Rule.

      Note: The database-level access control will be enabled without any IP addresses in the access control list. Enabling an access control list with an empty list of IP addresses makes the database inaccessible to all clients.

    • Specify the following types of addresses in your list by using the IP notation type drop-down selector:
      • IP Address allows you to specify one or more individual public IP addresses. Use commas to separate your addresses in the input field.

      • CIDR Block allows you to specify one or more ranges of public IP addresses using CIDR notation. Use commas to separate your CIDR block entries in the input field.
    Advanced Options:
    • Encryption Key:
      • Clone from a database instance: The source and the target ACD must be the same Keystore type. When the source is OKV, the target must also be the same OKV destination.

      • Clone from a backup: The source and the target ACDs can be different Keystore types. When the source is OKV, the target must also be the same OKV destination.
    • Management: Choose a Character Set and National Character from the drop-down list.
    • Tags: Optionally, you can apply tags. If you have permission to create a resource, you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator. Avoid entering confidential information.
  7. Click Create Autonomous Database Clone.

The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:

  • The new clone displays the Provisioning lifecycle state until the provisioning process completes.
  • The source database remains in the Available lifecycle state.

Clone a Standby Database

Follow these steps to clone a standby autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.

You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics.

Clone Types: The clone feature offers the full-clone option to create a database that includes the metadata and data from the source database.

Steps

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the primary database.
  4. Under Resources, click Autonomous Data Guard.
  5. In the list of standby databases, find the database that you want to clone, and then click the display name to view details.
  6. From the More Actions drop-down list, select Create Clone.
  7. On the Create Autonomous Database Clone page, provide the following information:

    In the Clone Type section, select Full Clone.

    Clone Source: You can clone the standby database only from a backup.
    • Clone from a backup: Creates a clone from a database backup. If you choose this option, select one of the following options:
      • Specify a timestamp: Creates a point-in-time clone.
      • Select from a list of backups: Creates a clone using all data from the specified backup. To limit your list of backups to a specific date range, enter the starting date in the From field and the ending date in the To field.

    Provide basic information for the Autonomous Database.

    • Choose a compartment: Your current compartment is the default selection but you can select a different compartment in which to create the clone from the drop-down list.
    • Source database name: The name of the source database displays in the read-only Source database name field.
    • Display name: Enter a description or other information to identify the database clone. You can change the display name any time and it does not have to be unique. Avoid entering confidential information.
    • Database name: Enter a database name for the clone that contains only letters and numbers, begins with a letter. Avoid entering confidential information.
    • Three additional fields are displayed if you opt to clone from a backup.
      • Exadata Infrastructure: You can choose to create the database clone in the same Exadata Infrastructure where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
      • Autonomous Exadata VM Cluster: You can choose to create the database clone in the same Autonomous Exadata VM Cluster where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
    • Autonomous Container Database: You can choose to create the database clone in the same compartment and container database as the source database, or you can choose a different compartment by clicking CHANGE COMPARTMENT, and a different container database by choosing one from the drop-down list.

    Configure the database

    • OCPU Count: There is a minimum requirement of 2 OCPUs for an ADB clone from Backup. After the clone, you can resize to a lower value if needed.

      Specify the number of OCPU for your database. The total number of cores available to all databases within the Autonomous Exadata Infrastructure depends on the infrastructure shape and what is already allocated to other Autonomous Databases.

      The default is 1. However, you can assign a fractional OCPU value from 0.1 to 0.9 (in increments of 0.1) to databases that do not need a full OCPU. For databases that need 1 or more OCPU cores, you must specify the number of assigned OCPUs as an integer. For example, you cannot assign 3.5 OCPU to a database. The next available number of OCPU above 3 is 4.

      • Default: 1
      • Minimum: 0.1
      • Maximum: Set by quota
      • Increment between 0.1 and 0.9: 0.1
      • Increment between 1 and maximum: 1
    • Storage (GB): Specify the amount of storage, in GB, that you want to make available to your cloned Autonomous Database, and it depends on the storage available to use. For full clones, the size of the source database determines the minimum amount of storage you can make available.
      • Default: 1024 GB
      • Minimum: 32 GB
      • Increment: 1 GB
    • Auto scaling: Enabling autoscaling allows the system to automatically use up to three times more CPU and I/O resources to meet workload demand.

    Create administrator credentials

    Set the password for the Autonomous Database administrator user by entering a password that meets the following criteria.

    • Password cannot be one of the three most recently used passwords of the source database
    • Between 12 and 30 characters long
    • Contains at least one lowercase letter
    • Contains at least one uppercase letter
    • Contains at least one number
    • Does not contain the double quotation mark (")
    • Does not contain the string "admin", regardless of casing

    Use this password when accessing the service console and when using a SQL client tool.

    Configure Network Access

    You can change the access control list to enable or disable database-level access control or add or modify entries to the access control list.

    • Click Modify Access Control.

    • Select the Enable database level access control check box.

    • Click Access Control Rule.

      Note: The database-level access control will be enabled without any IP addresses in the access control list. Enabling an access control list with an empty list of IP addresses makes the database inaccessible to all clients.

    • Specify the following types of addresses in your list by using the IP notation type drop-down selector:
      • IP Address allows you to specify one or more individual public IP addresses. Use commas to separate your addresses in the input field.

      • CIDR Block allows you to specify one or more ranges of public IP addresses using CIDR notation. Use commas to separate your CIDR block entries in the input field.
    Advanced Options:
    • Encryption Key:
      • Clone from a database instance: The source and the target ACD must be the same Keystore type. When the source is OKV, the target must also be the same OKV destination.

      • Clone from a backup: The source and the target ACDs can be different Keystore types. When the source is OKV, the target must also be the same OKV destination.
    • Management: Choose a Character Set and National Character from the drop-down list.
    • Tags: Optionally, you can apply tags. If you have permission to create a resource, you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator. Avoid entering confidential information.
  8. Click Create Autonomous Database Clone.

The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:

  • The new clone displays the Provisioning lifecycle state until the provisioning process completes.
  • The source database remains in the Available lifecycle state.
  • Backups associated with the source database are not cloned for either the full-clone or the metadata-clone option.

The Clone source is displayed in the General Information section of the cloned database details page. Click the name to view details of the source database. Note that if the source database is deleted, then this key/value pair is not displayed.

Related Topics

Clone a Standby Database Backup

Follow these steps to clone an autonomous database backup on an Oracle Exadata Database Service on Cloud@Customer system.

You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics. To clone only the database schema of your source database, choose the metadata clone option.

Clone Types

The clone feature offers the following two types of Autonomous Database clones:
  • The full-clone option creates a database that includes the metadata and data from the source database.
  • The metadata-clone option creates a database that includes only the metadata from the source database.

Steps

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the primary database.
  4. Under Resources, click Autonomous Data Guard.
  5. In the list of standby databases, find the database that you want to clone, and then click the display name to view details.
  6. Under Resources, click Backups.
  7. In the list of backups, find the backup that you want to clone, click the action icon (three dots), and then click Create Clone.
  8. On the Create Autonomous Database Clone page, provide the following information:

    In the Clone Type section, select Full Clone.

    Clone Source: The clone source section displays the source backup details.

    Provide basic information for the Autonomous Database.

    • Choose a compartment: Your current compartment is the default selection but you can select a different compartment in which to create the clone from the drop-down list.
    • Source database name: The name of the source database displays in the read-only Source database name field.
    • Display name: Enter a description or other information to identify the database clone. You can change the display name any time and it does not have to be unique. Avoid entering confidential information.
    • Database name: Enter a database name for the clone that contains only letters and numbers, begins with a letter. Avoid entering confidential information.
    • Exadata Infrastructure: You can choose to create the database clone in the same Exadata Infrastructure where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
    • Autonomous Exadata VM Cluster: You can choose to create the database clone in the same Autonomous Exadata VM Cluster where the source database resides, or you can choose a different compartment by clicking CHANGE COMPARTMENT and choosing one from the drop-down list.
    • Autonomous Container Database: You can choose to create the database clone in the same compartment and container database as the source database, or you can choose a different compartment by clicking CHANGE COMPARTMENT, and a different container database by choosing one from the drop-down list.
      Note

      When the target Autonomous Exadata VM Cluster is the same as the source, then the database name cannot be the same as the source database name.

    Configure the database

    • OCPU Count: There is a minimum requirement of 2 OCPUs for an ADB clone from Backup. After the clone, you can resize to a lower value if needed.
      Note

      The time taken to clone an ADB depends on the OCPU Count and the network bandwidth between the Backup Destination and the target ACD.

      Specify the number of OCPU for your database. The total number of cores available to all databases within the Autonomous Exadata Infrastructure depends on the infrastructure shape and what is already allocated to other Autonomous Databases.

      The default is 1. However, you can assign a fractional OCPU value from 0.1 to 0.9 (in increments of 0.1) to databases that do not need a full OCPU. For databases that need 1 or more OCPU cores, you must specify the number of assigned OCPUs as an integer. For example, you cannot assign 3.5 OCPU to a database. The next available number of OCPU above 3 is 4.

      • Default: 2
      • Minimum: 2
      • Maximum: Set by quota
    • Storage (GB): Specify the amount of storage, in GB, that you want to make available to your cloned Autonomous Database, and it depends on the storage available to use.
      • Default/Minimum: Allocated storage of the source database
      • Increment: 1 GB
    • Auto scaling: Enabling autoscaling allows the system to automatically use up to three times more CPU and I/O resources to meet workload demand.

    Create administrator credentials

    Set the password for the Autonomous Database administrator user by entering a password that meets the following criteria.

    • Password cannot be one of the three most recently used passwords of the source database
    • Between 12 and 30 characters long
    • Contains at least one lowercase letter
    • Contains at least one uppercase letter
    • Contains at least one number
    • Does not contain the double quotation mark (")
    • Does not contain the string "admin", regardless of casing

    Use this password when accessing the service console and when using a SQL client tool.

    Configure Network Access

    You can change the access control list to enable or disable database-level access control or add or modify entries to the access control list.

    • Click Modify Access Control.

    • Select the Enable database level access control check box.

    • Click Access Control Rule.

      Note: The database-level access control will be enabled without any IP addresses in the access control list. Enabling an access control list with an empty list of IP addresses makes the database inaccessible to all clients.

    • Specify the following types of addresses in your list by using the IP notation type drop-down selector:
      • IP Address allows you to specify one or more individual public IP addresses. Use commas to separate your addresses in the input field.

      • CIDR Block allows you to specify one or more ranges of public IP addresses using CIDR notation. Use commas to separate your CIDR block entries in the input field.
    Advanced Options:
    • Encryption Key:
      • Clone from a database instance: The source and the target ACD must be the same Keystore type. When the source is OKV, the target must also be the same OKV destination.

      • Clone from a backup: The source and the target ACDs can be different Keystore types. When the source is OKV, the target must also be the same OKV destination.
    • Management: Choose a Character Set and National Character from the drop-down list.
    • Tags: Optionally, you can apply tags. If you have permission to create a resource, you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator. Avoid entering confidential information.
  9. Click Create Autonomous Database Clone.

The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:

  • The new clone displays the Provisioning lifecycle state until the provisioning process completes.
  • The source database remains in the Available lifecycle state.

Related Topics

Terminate an Autonomous Database

Follow these steps to terminate an Autonomous Database on an Oracle Exadata Database Service on Cloud@Customer system.

WARNING:

Terminating an Autonomous Database permanently deletes it. The database data will be lost when the system is terminated. However, automatic backups are not deleted if you have chosen Recovery Appliance or NFS as a backup destination. You can delete automatic backups directly from the Recovery Appliance or NFS.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Click Autonomous Databases.
  3. In the list of Autonomous Databases, click the display name of the database you wish to terminate.
  4. From the More Actions drop-down list, select Terminate.
  5. Confirm that you wish to terminate your Autonomous Database in the confirmation dialog.
  6. Click Terminate Autonomous Database.

API to Manage Autonomous Databases

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

The following table lists the REST API endpoints to manage Autonomous Databases.

Operation REST API Endpoint

Create an Autonomous Database

CreateAutonomousDatabase

View a list of Autonomous Databases

ListAutonomousDatabases

View details of an Autonomous Database

GetAutonomousDatabase

View a list of character sets supported by Autonomous Database. ListAutonomousDatabaseCharacterSets

Set the password of an Autonomous Database's ADMIN user

UpdateAutonomousDatabase

Scale the CPU core count or storage of an Autonomous Database

UpdateAutonomousDatabase

Enable or disable auto scaling for an Autonomous Database

UpdateAutonomousDatabase

Move an Autonomous Database to another compartment

ChangeAutonomousDatabaseCompartment

Stop or start an Autonomous Database

StartAutonomousDatabase

Stop or start an Autonomous Database

StopAutonomousDatabase

Restart an Autonomous Database

RestartAutonomousDatabase

Back up an Autonomous Database manually

CreateAutonomousDatabaseBackup

View the list of Autonomous Database backups

ListAutonomousDatabaseBackups

Restore an Autonomous Database

RestoreAutonomousDatabase

Clone an Autonomous Database

CreateAutonomousDatabase

Terminate an Autonomous Database

DeleteAutonomousDatabase

Monitor Performance with Autonomous Database Metrics

You can monitor the health, capacity, and performance of your Autonomous Databases with metrics, alarms, and notifications. You can use Oracle Cloud Infrastructure console or Monitoring APIs to view metrics.

View Top Six Metrics for an Autonomous Database

Displays the top six metrics that are available in the metrics section on the Autonomous Database details page.

To view metrics you must have the required access as specified in an Oracle Cloud Infrastructure policy (whether you're using the Console, the REST API, or other tools). See Getting Started with Policies for information on policies.

Perform the following prerequisite steps as necessary:
  • Open the Oracle Cloud Infrastructure console by clicking the hamburger menu next to Oracle Cloud.

  • From the Oracle Cloud Infrastructure left navigation list click Oracle Databases > Exadata Cloud@Customer.

  • On the Autonomous Databases page select an Autonomous Database from the links under the Name column.

To view metrics for an Autonomous Database instance:

  1. On the Autonomous Database Details page, under Resources, click Metrics.
  2. There is a chart for each metric. In each chart, you can select the Interval and Statistic or use the default values.
  3. To create an alarm on a metric, click Options and select Create an Alarm on this Query.

    See Managing Alarms for information on setting and using alarms.

    For more information about metrics see Database Metrics.

    You can also use the Monitoring API to view metrics. See Monitoring API for more information.

View Aggregated Metrics for Autonomous Databases in a Compartment

Learn to view aggregated metrics for Autonomous Databases in a compartment.

To view metrics you must have the required access as specified in an Oracle Cloud Infrastructure policy (whether you're using the Console, the REST API, or other tool). See Getting Started with Policies for information on policies

Perform the following prerequisite steps as necessary:
  • Open the Oracle Cloud Infrastructure console by clicking the hamburger menu next to Oracle Cloud.

  • From the left navigation list click Solutions and Platform > Monitoring > Service Metrics.

To use the metrics service to view Autonomous Database metrics:

  1. On the Service Metrics page, under Compartment select your compartment.
  2. On the Service Metrics page, under Metric Namespace select oci_autonomous_database.
  3. If there are multiple Autonomous Databases in the compartment you can show metrics aggregated across the Autonomous Databases by selecting Aggregate Metric Streams.
  4. If you want to limit the metrics you see, next to Dimensions click Add (click Edit if you have already added dimensions).
    1. In the Dimension Name field select a dimension.
    2. In the Dimension Value field select a value.
    3. Click Done.
    4. In the Edit dimensions dialog click +Additional Dimension to add an additional dimension. Click x to remove a dimension.

To create an alarm on a specific metric, click Options and select Create an Alarm on this Query. See Managing Alarms for information on setting and using alarms.

Autonomous Database Metrics and Dimensions

You can limit the instances where you see metrics with dimensions. The available dimensions include: workload type, instance display name, region, and the instance OCID.

Use dimensions by selecting values in the Oracle Cloud Infrastructure Console Service Metrics page or by setting dimension values with the API. See View Aggregated Metrics for Autonomous Databases in a Compartment to view metrics and to select metric dimensions.

See Database Metrics for a list of the database metrics and dimensions.