Shows you the steps to change the database name for an Autonomous Database instance.
Before you rename your database, note the following:
A single tenancy in the same region cannot contain two Autonomous Databases with the same name.
The database rename operation changes the connection strings required to connect to the database. Thus, after you rename a database you must download a new wallet for any existing instance wallets that you use to connect to the database (and any applications also must be updated to use the new connection string and the new wallet to connect to the database).
If you are using a regional wallet, you can continue to use the existing wallet to connect to any databases that were not renamed. However, if you want to connect to a renamed database, you must download a new regional wallet.
See Download Client Credentials (Wallets) for more information.
Note:The rename operation terminates all connections to the database. After the rename operation completes, you can reconnect to the database.
Perform the following prerequisite steps as necessary:
Open the Oracle Cloud Infrastructure Console by clicking the 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.
On the Autonomous Databases page select an Autonomous Database from the links under the Display Name column.
To rename an Autonomous Database instance, do the following:
- On the Details page, from the More Actions drop-down list, select
This shows the Rename Database dialog.
Description of the illustration adb_db_rename.png
- On the Rename Database dialog, provide values for the
New database name: the name you enter must consist of letters and numbers only. The maximum length is 14 characters.
Enter the current database name to confirm the name change
- Click Rename Database.
After validating the fields, while the system renames the database the lifecycle state changes to Updating. You can start using the database after the rename operation completes and the lifecycle state shows Available.
Notes for Autonomous Database rename:
Renaming your database does not change global references to your database from existing database links on remote databases. Changing such references is the responsibility of the administrator of the remote databases.
When you rename a database, the Autonomous Database OCID does not change.
If your database has Autonomous Data Guard enabled, the rename operation is not available.
You cannot use the rename operation on a refreshable clone instance or on a database that is the source for a refreshable clone.
The rename operation restarts the database.
If you configured your Autonomous Database for manual backups prior to the rename operation, then your existing manual backups continue to work after the rename operation. If you perform new manual backups after the rename, they are stored in the same bucket that you configured prior to the rename operation.
See Configure Manual Backups on Autonomous Database for information on manual backups.
- You can rename your Autonomous Database using the API. See UpdateAutonomousDatabase for more information.