Managing an Autonomous Database

Autonomous Database

This topic describes the database management tasks for Autonomous Databases that you complete using the Oracle Cloud Infrastructure Console or the API. These tasks apply to Autonomous Databases of either the Data Warehouse, JSON Database, or Transaction Processing workload types. You can filter Autonomous Databases by workload type on the Autonomous Databases page of the Oracle Cloud Infrastructure Console.
Note

Some database management tasks not described here are performed using the Autonomous Transaction Processing service console or the Autonomous Data Warehouse service console.

Prerequisites

To perform the management tasks in this topic, 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.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.

Using the Oracle Cloud Infrastructure Console

Lifecycle Management Operations

To check the lifecycle state of your Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. In the Information tab, note the value displayed for Lifecycle State. For some lifecycle states, an information icon (encircled i) is displayed to provide additional details regarding the lifecycle state or ongoing operations such as backups, restores, or terminations. The database has one of the following lifecycle states:

    • Available
    • Available needs attention
    • Backup in progress
    • Provisioning
    • Restore in progress
    • Scaling in progress
    • Starting
    • Stopping
    • Stopped
    • Terminating
    • Terminated
    • Unavailable
To stop or start an Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then 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.
  • CPU billing is halted
  • You will not be able to connect to your database using database clients or tools.
To restart an Autonomous Database
Tip

Restarting a database is equivalent to manually stopping and then starting the database. Using restart allows you to minimize downtime and requires only a single action.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then 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.
To terminate an Autonomous Database
Caution

Terminating an Autonomous Database permanently deletes it. The database data, including automatic backups, will be lost when the system is terminated. Manual backups remain in Object Storage and are not automatically deleted when you terminate an Autonomous Database. Oracle recommends that you create a manual backup prior to terminating.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then click Terminate.
  5. Confirm that you want to terminate your Autonomous Database in the confirmation dialog.
To scale the CPU core count or storage of an Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Click Scale Up/Down.
  5. Enter a new value for CPU Core Count or Storage from 1 to 128. The number you enter represents the total value for your database's CPU core count or storage.

    The number of available cores is subject to your tenancy's service limits. An Autonomous Database database can have a maximum of 128 cores and 128 TB of storage. Scaling the CPU core count affects your CPU billing.

  6. Click Update.
To enable or disable auto scaling for an Autonomous Database

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. See CPU Scaling for more information.
  • 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. See Managing Concurrency and Priorities on Autonomous Data Warehouse and Managing Priorities on Autonomous Transaction Processing for more information.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  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.
To view OCPU allocation hourly snapshot data for an Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database for which you want to view CPU usage data.
  4. Click the Service Console button. The Service Console opens in a new tab or window.
  5. In the Overview screen, the Number of OCPUs allocated graph shows hourly snapshot data of OCPU allocation over the last eight days. Place your cursor over the graph and move it to the left or right to see data for a specific day and hour.

Database Management Tasks

To set the Admin password
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then click 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.
To access the Autonomous Database service console for databases on shared Exadata infrastructure
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Click Service Console.

For information on using the Autonomous Transaction Processing service console features, see Managing and Monitoring Performance of Autonomous Transaction Processing. For information on using the Autonomous Data Warehouse service console features, see Managing and Monitoring Performance of Autonomous Data Warehouse Cloud.

To change the license type of an Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then click Update License Type.

    The dialog displays the options with your current license type selected.

  5. Select the new license type.
  6. Click Update.

See Known Issue.

To upgrade an Autonomous Database
Note

Depending on your region, Autonomous Database provides Oracle Database 18c, Oracle Database 19c, or both. Both versions are available only while version 19c is available for preview and testing. To learn which database versions are available in which region, see Oracle Database Versions and Availability by Region.

If your Autonomous Database uses Oracle Database version 18c, after notifying you of the upgrade date, Oracle automatically upgrades your instance to Oracle Database version 19c. However, you do not need to wait until the automatic upgrade to view and test the new features that are available in Oracle Database 19c. You can manually upgrade a paid database at any time.

Upgrade Options

There are four ways to upgrade an Autonomous Database:

  • Manually upgrade the existing Autonomous Database instance.
  • Create a full clone of your Autonomous Database and upgrade it.
  • Create a full clone of a backup of your Autonomous Database and upgrade it.
  • Let Oracle automatically upgrade your Autonomous Database. Oracle will automatically upgrade only after notifying you in advance of the upgrade time.

When you run this upgrade, the Autonomous Database will be upgraded to the latest version available in Oracle Cloud Infrastructure.

Important

Oracle recommends that before you upgrade your production database, you create a full clone from the database or a backup, upgrade the clone, and test your applications with the clone running the new Oracle Database version. When everything works correctly, manually upgrade your production database.
Prerequisites and Notes
  • The Autonomous Database must be in the Available lifecycle state.
  • You cannot manually upgrade an Always Free Autonomous Database.
  • After you complete a manual upgrade, only backups made after the upgrade show in the list of backups.
Manually Upgrading an Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to upgrade. The Database Version field shows the Oracle Database software version.
  4. Click the Upgrade to 19c link beside the database version information. The Upgrade Autonomous Database dialog box opens.
  5. Enter the database name and click Upgrade. The database upgrade process begins. While the database is being upgraded, the Lifecycle State field shows Upgrading. The database is available during the upgrade process, although some lifecycle management functions are not available.
  6. The database restarts automatically when the upgrade is complete. It is not available while restarting.
Note

It takes up to 10 minutes for the database to restart and be available again. When the database has restarted, the Lifecycle State field shows Available and the Database Version field shows 19c.
Manually Upgrading by Cloning an Autonomous Database

To upgrade your Autonomous Database from version 18c to 19c by creating a full clone:

  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to clone. The Database Version field shows the Oracle Database software version of your selected source database. Verify that the Oracle Database version of your Autonomous Database instance is Oracle Database 18c.
  4. Using the information below, clone the database by completing the steps in Cloning an Autonomous Database:

    • For Clone type, select Full Clone.
    • For Clone source, specify Clone from database instance to clone your selected database, or Clone from a backup to create a clone based on a single backup or a point-in-time clone.
  5. When configuring the clone, in the Choose database version list, select the newer Oracle Database version.
About Wallets

A upgraded Autonomous Database instance uses the same wallet after the upgrade is complete. You can continue to use your existing instance and regional wallets to connect to the database.

A database that was cloned has its own wallet. You cannot use the wallet of the source database to connect to the clone. Obtain a new wallet for the clone and use it to access the cloned database.

See About Downloading Client Credentials (Wallets) for more information.

To rename an Autonomous Database on shared Exadata infrastructure
Note

Renaming a database changes the contents of the database wallet and requires that you download a new wallet.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Select the compartment, from the Compartment drop-down, that contains the database you want to rename.
  3. From the list of Autonomous Databases contained in the compartment, click the display name of the database you want to rename to display the Autonomous Database Details page for that database.
  4. Click More Actions to display a list of actions.
  5. Click Rename Database to display the Rename Database dialog.
  6. Enter a database name that contains only letters and numbers, begins with a letter, and does not exceed 14 characters.
  7. Enter the current database name to confirm the name change.
  8. Click Rename Database.
To change the workload type of an Autonomous JSON Database
You can change the workload type of an Autonomous JSON Database to transaction processing if you need to additional capabilities offered by Autonomous Transaction Processing.
Note

This change results in billing changes and cannot be reversed.
  1. Open the navigation menu. Under Oracle Database, click Autonomous JSON Database.
  2. Select the compartment, from the Compartment drop-down, that contains the database for which you want to change the workload type.
  3. Click the display name of the Autonomous JSON Database for which you want to change the workload type to display the Autonomous Database Details page for that database.
  4. In the General Information section, click Change Workload Type in the Workload Type field to display the Change Workload Type to Transaction Processing confirmation dialog.

    Alternatively, you can click More Actions to display a list of operations. Click Change Workload Type to display the Change Workload Type to Transaction Processing confirmation dialog.

  5. Click Change Workload Type to Transaction Processing.
To change the access mode of an Autonomous Database
You can select an operation mode for an Autonomous Database. The default mode is read/write but you can select read-only to limit users to querying the database, only. In addition, for either of these modes you can restrict access to only allow a user with administrator privileges to access the database.
Note

Changing access modes and permission level do no not apply to an Autonomous JSON Database.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your compartment from the Compartment drop-down.
  3. In the list of Autonomous Databases, click the name of the database for which you want to change the access mode to display the details page for that database.
    Note

    The database you choose must be in the Available state to successfully change the access mode.
  4. On the Autonomous Database Information tab, click the Edit link in the Mode field.
  5. In the Edit Database Mode dialog, choose either Read/Write or Read-only, depending on the access mode you want. By default, an Autonomous Database is provisioned in read/write mode.

    You can also restrict access to the ADMIN user or users with administrator privileges by checking Allow administrator access only. You can apply this restriction whether the database is in read/write or read-only mode.

  6. Click Confirm to apply the change.
Note

  • Changing the permission level requires that users and applications reestablish connections to the database.
  • When the database is in read-only mode:

    • You cannot change the ADMIN user password.
    • You cannot upgrade the database.
To enable or disable Operations Insights on an Autonomous Database

Operations Insights is an Oracle Cloud Infrastructure service that provides analytics that you can use to monitor an Autonomous Database on either dedicated or shared Exadata infrastructure.

Note

Enabling Operations Insights for the first time takes a few minutes to complete. Subsequent enabling operations take less time.

To enable Operations Insights:

  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse or Autonomous Transaction Processing.
    Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. If necessary, choose the compartment from the Compartment drop-down that contains the Autonomous Database you want to register with Operations Insights.
  3. From the list of Autonomous Databases, click the display name of the database to display the details page for that database.
  4. In the Operations Insights section, click Enable or Disable to display a confirmation dialog.

    Once enabled, click the View link in the Operations Insights section to display the various metrics.

  5. Click Confirm.

Networking Management Tasks

To change the network access type of an Autonomous Database on shared Exadata infrastructure from public endpoint to private endpoint

Autonomous Databases on shared Exadata infrastructure can use either of the following network access options:

  • Virtual cloud network: This option uses a private endpoint within a VCN in your tenancy. The private endpoint conncts to the private endpoint in either an Autonomous Database with private endpoint using dedicated Exadata infrastructureor an Autonomous Database with a private endpoint in the Shared Exadata infrastructure
  • Allow secure access from everywhere: This option uses a public endpoint provided by Oracle.

This topic describes how to switch a database's network access to the Virtual cloud network option. See Autonomous Database with Private Endpoint more information on this option, including the prerequisites needed to switch.

Note

  • Your Oracle Database version must be 19c or higher to perform an in-place switch the network access type after provisioning.
  • To change the network access configuration from a private to a public endpoint, the Autonomous Database must have the Available lifecycle state.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then click Update Network Access.
  5. In the Update Network Access dialog, select Virtual cloud network.
    Note

    If Data Safe is enabled,
    1. Ensure that you have created a private endpoint in the selected VCN for Autonomous Database with a private endpoint
    2. Ensure that you have configured the security rules to allow traffic from Data Safe to Autonomous Database. For more information, see the Data Safe documentation.
  6. Specify the following information:

    • Virtual cloud network: The VCN in which to launch the Autonomous Database. Click Change Compartment to select a VCN in a different compartment.
    • Subnet: The subnet to which the Autonomous Database should attach. Click change compartment to select a subnet in a different compartment. Oracle recommends that you specify a private subnet.
    • Hostname prefix: Optional. This specifies a host name prefix for the Autonomous Database and associates a DNS name with the database instance, in the following form:

      hostname_prefix.adb.region.oraclecloud.com

      The host name must begin with an alphabetic character, and can contain only alphanumeric characters and hyphens (-). You can use up to 63 alphanumeric characters for your hostname prefix.

      If you choose not to specify a hostname prefix, Oracle creates a unique DNS name for your database.

    • Network security groups:  You must specify at least one network security group (NSG) for your Autonomous Database. NSGs function as virtual firewalls, allowing you to apply a set of ingress and egress security rules to your database. A maximum of five NSGs can be specified.

      For more information on creating and working with NSGs, see Network Security Groups.

      Note that if you choose a subnet with a security list, the security rules for the database will be a union of the rules in the security list and the NSGs.

  7. Click Update.
  8. In the Confirm dialog, type the Autonomous Database name to confirm the change.

    Click Update.

Notes:

  • After updating the network access type all database users must obtain a new wallet and use the new wallet to access the database. See About Downloading Client Credentials (Wallets) for more information.
  • If you had access control list (ACL) rules defined for the public endpoint, the rules do not apply for the private endpoint.
To change the network access of an Autonomous Database on shared Exadata infrastructure from private endpoint to public endpoint

Autonomous Databases on shared Exadata infrastructure can use either of the following network access options:

  • Virtual cloud network: This option uses a private endpoint within a VCN in your tenancy.
  • Allow secure access from everywhere: This option uses a public endpoint provided by Oracle.

This topic describes how to switch a database's network access to the Allow secure access from everywhere option.

Note

  • Your Oracle Database version must be 19c or higher to perform an in-place switch the network access type after provisioning.
  • To change the network access configuration from a private to a public endpoint, the Autonomous Database must have the Available lifecycle state.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then click Update Network Access.
  5. In the Update Network Access dialog, select Allow secure access from everywhere.
  6. Click Update.
  7. In the Confirm dialog, type the Autonomous Database name to confirm the change.
  8. Click Update.

Notes:

To manage the access control list of an Autonomous Database on shared Exadata infrastructure

This task applies to Autonomous Databases using the Allow secure access from everywhere network access option.  This option uses a public endpoint provided by Oracle.

An access control list (ACL) provides additional protection for your Autonomous Database by allowing only the IP addresses in the list to connect to the database. An ACL must contain at least one entry representing an IP address or a range of addresses. To create or edit an ACL for an existing database that uses shared Exadata infrastructure, do the following:

  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  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 add (if no ACL currently exists) or edit (to update an existing ACL).

  5. In the Access Control List dialog, add or modify entries, as applicable.

    Note

    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 + Another Entry.
    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 address. 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.
    • Virtual Cloud Network allows you to specify an existing VCN. The drop-down listing in the input field allows you to choose from the VCNs in your current compartment for which you have access permissions. Click the Change Compartment link to display the VCNs of a different compartment.
    • Virtual Cloud Network (OCID) allows you input the OCID  of a VCN in a text box. You can use this input method if the VCN you are specifying is in a compartment which you do not have permission to access.
    If you add a Virtual Cloud Network to your ACL, you can limit further by specifying allowed VCN IP addresses or CIDR ranges. Enter those addresses or CIDR blocks in the IP Addresses or CIDRs field that is displayed below your Virtual Cloud Network choice. Use commas to separate your VCN addresses and CIDR blocks in the input field. You can specify the following types of IP addresses at the VCN level: Click + Another Entry to add additional access rules to your list.
    Important

    If you are using a service gateway, ensure that the CIDR range 240.0.0.0/4 is included in the list to allow clients accessing the database through the service gateway to connect to it.

    To remove the ACL, simply delete all entries in the list. This action allows all clients to connect to the database.

  6. Click Update.

If the Lifecycle State is Available when you click Update, 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.

For more information about access control lists, see Security Considerations.

To update the network configuration of an Autonomous Database on shared Exadata infrastructure that uses a private endpoint
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer. The Autonomous Database Details page displays.
  4. In the Autonomous Database Information tab, the Network section displays the names of your database's virtual cloud network (VCN), subnet, and network security groups (NSGs). The following networking configuration changes are possible:

    • Clicking the names of your VCN and subnet will take you to the resource details pages of those resources. While you can edit the configurations of those resources, you cannot assign a different VCN or subnet to your Autonomous Database.
    • You can add or remove NSGs by clicking the edit link by the listed NSGs in the Network section on the Autonomous Database Details page. Note that your specified NSGs must contain stateless security rules.
    • You can edit the security rules of any of your Autonomous Database's NSGs by clicking the name of the NSG. Clicking the name takes your to the Network Security Group Details page of the NSG.

Management Tasks for the Oracle Cloud Infrastructure Platform

To view a work request for your Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. In the Resources section, click Work Requests. The status of all work requests appears on the page.
  5. To see the log messages, error messages, and resources that are associated with a specific work request, click the operation name. Then, select an option in the More information section.

    For associated resources, you can click the the Actions icon (three dots) next to a resource to copy the resource's OCID.

For more information, see Work Requests.

To move an Autonomous Database to another compartment
Note

  • To move resources between compartments, resource users must have sufficient access permissions on the compartment that the resource is being moved to, as well as the current compartment. For more information about permissions for Database resources, see Details for the Database Service.

  • Security zone considerations:

    • If your Autonomous Database is in a security zone, the destination compartment must also be in a security zone.
    • If your Autonomous Database uses a public endpoint, you cannot move it to a security zone compartment unless you first switch the networking configuration to use a private endpoint.
    • If your Autonomous Database is not in a security zone and has Data Guard standby database, you cannot move the database into a security zone compartment while the standby remains in a compartment that is not in a security zone.

    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 JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to move.
  4. Go to More Actions, and then click Move Resource.
  5. Select the new compartment.
  6. Click Move Resource.

    For information about dependent resources for Database resources, see Moving Database Resources to a Different Compartment.

To manage tags for your Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to administer.
  4. Go to More Actions, and then click Apply Tag(s) to add new tags. Or click the Tags tab to view or edit the existing tags.

For more information, see Resource Tags.

To upgrade an Always Free Autonomous Database to a paid instance

If you are using a paid account, you can upgrade an Always FreeAutonomous Database to a paid instance. Paid instances include the ability to scale the OCPU count and storage.

  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to ugrade.
  4. Go to More Actions, and then click Upgrade Instance to Paid.
  5. In the Confirm Upgrade dialog, confirm that you want to upgrade the instance by clicking the Upgrade Instance to Paid button.

    The lifecyle state of the Autonomous Database will change to Updating while your upgrade is in progress. You database remains online and accessible while the upgrade is in progress. After your instance is upgraded to paid, you will be able to provision a new Always FreeAutonomous Database in place of your upgraded instance.

Security Management Tasks

For information on network security management tasks, see Networking Management Tasks.

To register or deregister an Autonomous Database with Data Safe

To use Oracle Data Safe with an Autonomous Database, you register your database with Data Safe. To discontinue using Data Safe, you deregister the database. For information about using Data Safe, see the Data Safe documentation.

Prerequisites for Autonomous Databases with private endpoints
Note

If a Data Safe private endpoint does not exist in the same VCN used by the target Autonomous Database, the Data Safe registration will fail. For more information, see the Data Safe documentation.
Note

Additional procedures are required when Database Vault is enabled on the database you are registering or deregistering. See the information at the end of the following procedure.
Registering and deregistering an Autonomous Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
    Note

    The Data Discovery and Data Masking features are not supported for JSON type columns. See Target Database Registration Overview for more information.
  2. Choose your Compartment.
  3. In the list of Autonomous Databases, click the display name of the database you want to manage.
  4. In the Details page, under Data Safe, click register or deregister depending on the status of the database.

    • If the database uses dedicated Exadata infrastructure, enter the ADMIN password and click Confirm to start the registration or deregistration process. The ADMIN password is needed to unlock Data Safe so that it can monitor the database.
    • If the database uses Shared Exadata infrastructure, click Confirm to start the registration or deregistration process.

    If the registration fails and the database is using a private endpoint, ensure that the prerequisites listed in this topic for allowing network access have been met.

  5. You can optionally use either or both of the following to monitor the registration and deregistration process:
    • Use the work request created by the system to monitor the progress of the registration or deregistration.
    • Click View Console to display the Data Safe user interface for the registered database.
Registering and deregistering an Autonomous Database when Database Vault is enabled

When Database Vault is enabled on the database you are registering or deregistering, complete the following additional steps to register or deregister the database. These are needed to accommodate the additional database security provided by Database Vault.

  • The Database Vault account manager must first grant specific access rights to the ADMIN database user before they can register or deregister an Autonomous Database. Otherwise, an "insufficient privileges" error is displayed.
  • After the database has been registered or deregistered, the Database Vault account manager can remove the access rights to limit access during normal operations,
  • After the database registration is complete, the Database Vault owner must grant specific access rights to the DS$ADMIN database user to enable normal operations. See the Data Safe documentation to learn about the access rights needed.

For more information on using Database Vault with an Autonomous Database, see the following user guides:

To rotate the encryption key for an Autonomous Database

Rotating the encryption key creates a new version of the vault key that replaces the current version of the vault key.

  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your compartment from the Compartment drop-down.
  3. Click the display name of the Autonomous Database for which you want to rotate the encryption key to display the details page for that database.
    Note

    The Autonomous Database you choose must be on dedicated Exadata infrastructure and in an Available state.
  4. Click the More Actions drop-down.
  5. Click Rotate Encryption Key to display a confirmation dialog.
  6. Click Rotate Key.

For More Information