Oracle Cloud Infrastructure Documentation

Undelete a Terminated Autonomous Database Instance

Describes the steps to undelete an Autonomous Database instance.

You can undelete a database up to 72 hours after the database was terminated, or up to the backup retention period, whichever is lower. Using undelete is not possible after more than three days (72 hours) from the time you terminated the database.

Before you undelete your database, note the following:

  • To undelete an Autonomous Database instance the instance must use the ECPU compute model.

    See Compute Models in Autonomous Database for more information.

  • If a different database with the same name exists in the same region, you must first rename or terminate the existing database before you can successfully undelete the database.

  • If a database was configured with a Private Endpoint within a Virtual Cloud Network (VCN), a VCN must exist before you can undelete the database. If VCN is not available, use Oracle Cloud Support to file a Service Request to recover the VCN.

  • The undelete operation is available when the terminated database is an Oracle Database 19c instance.

  • The undelete operation is not available when the terminated database is an Oracle Database 23ai instance.

  • The undelete operation is not available when the terminated database is an Autonomous Database for Developers instance.

Perform the following prerequisite steps as necessary:

  • Open the Oracle Cloud Infrastructure Console by clicking the navigation icon next to Oracle Cloud.

  • From the Oracle Cloud Infrastructure left navigation menu click Oracle Database and then, depending on your workload click one of: Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
To undelete an Autonomous Database instance:
  1. On the Autonomous Databases page in the Resources area, from the State drop-down list, select Terminated.
  2. In a row that shows your terminated database, click more actionsat the end of the row and select Undelete. This shows the Undelete database dialog.

    Description of adb_undeletedb_dialog.png follows

  3. Click Undelete database.

    The Autonomous Database Lifecycle State changes to Provisioning.

While the system undeletes the database, the Lifecycle State changes from Provisioning to Updating, and then to Available.

You can start using the database after the undelete operation completes and the lifecycle state shows Available.

Notes for Autonomous Database undelete:

  • When an Autonomous Database instance is undeleted, it will be billed as a running database for the time-period that it was terminated. See Oracle Autonomous Database Serverless Features Billing for more information.

  • If you were using a wallet to connect to your database, you must download the wallet again after you undelete the database.

    See Download Client Credentials (Wallets) for more information.

  • Any additional features enabled after the initial creation of the database must be re-enabled after you undelete a database. For example, you need to re-enable Data Safe registration, Autonomous Data Guard, or Flashback Time Travel after you undelete.

  • When you undelete your database, the following are automatically restored:

    • All the backups before the restore timestamp, including automatic backups and if there are any long-term backups.

    • The most recent Network Access options that were specified before the database was deleted.

      See About Network Access Options for more information.

    • The most recent Backup retention period specified for automatic backups and long-term backups before the database was deleted.

  • You cannot perform the undelete operation if the terminated database is:

    • A refreshable clone

    • A Backup-Based Disaster Recovery peer

    • An Autonomous Data Guard standby database

    However, if you delete one of these, you can provision them again from the source database.

Parent topic: Lifecycle Operations