If you choose to encrypt databases in an Oracle Exadata Database Service on Exascale Infrastructure instance using encryption keys that you manage, then you may update the following two packages (using Red Hat Package Manager) to enable DBAASTOOLS to interact with the APIs that customer-managed key management uses.

Learn how you can create your first or subsequent databases.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure
2. Choose your Compartment.
3. Navigate to the cloud VM cluster or DB system you want to create the database in:

   Cloud VM clusters (The New Exadata Cloud Infrastructure Resource Model): Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

4. Click Create Database.
5. In the Create Database dialog, enter the following:
   Note
   
   You cannot modify the db_name, db_unique_name, and SID prefix after creating the database.
   • Database name: The name for the database. The database name must meet the requirements:
     • Maximum of 8 characters
     • Contain only alphanumeric characters
     • Begin with an alphabetic character
     • Cannot be part of the first 8 characters of a DB_UNIQUE_NAME on the VM cluster
     • DO NOT use the following reserved names: grid, ASM
   • Database unique name suffix:

     Optionally, specify a value for the DB_UNIQUE_NAME database parameter. The value is case insensitive.

     The unique name must meet the requirements:

     • Maximum of 30 characters
     • Contain only alphanumeric or underscore (_) characters
     • Begin with an alphabetic character
     • Unique across the VM cluster. Recommended to be unique across the tenancy.
     If not specified, the system automatically generates a unique name value, as follows:

     <db_name>_<3_chars_unique_string>_<region-name>

   • Database version: The version of the database. You can mix database versions on the Exadata DB system.
   • Database Home: The Oracle Database Home for the database. Choose the applicable option:
     • Select an existing Database Home: The Database Home display name field allows you to choose the Database Home from the existing homes for the database version you specified. If no Database Home with that version exists, you must create a new one.
     • Create a new Database Home: Use this option to provision a new Database Home for your Data Guard peer database.

       Click Change Database Image to use an older Oracle-published image or a custom database software image that you have created in advance, then select an Image Type:

       • Oracle Provided Database Software Images:

         then you can use the Display all available version switch to choose from all available PSUs and RUs. The most recent release for each major version is indicated with a latest label.

         Note
         
         For the Oracle Database major version releases available in Oracle Cloud Infrastructure, images are provided for the current version plus the three most recent older versions (N through N - 3). For example, if an instance is using Oracle Database 19c, and the latest version of 19c offered is 19.8.0.0.0, images available for provisioning are for versions 19.8.0.0.0, 19.7.0.0, 19.6.0.0 and 19.5.0.0.
       • Custom Database Software Images: These images are created by your organization and contain customized configurations of software updates and patches. Use the Select a compartment and Select a Database version selectors to limit the list of custom database software images to a specific compartment or Oracle Database software major release version.
   • PDB name: (Optional) You can specify the name of the pluggable database. The PDB name must begin with an alphabetic character, and can contain a maximum of eight alphanumeric characters. The only special character permitted is the underscore ( _).

     To avoid potential service name collisions when using Oracle Net Services to connect to the PDB, ensure that the PDB name is unique across the entire VM cluster. If you do not provide the name of the first PDB, then a system-generated name is used.

   • Create administrator credentials: (Read only) A database administrator SYS user will be created with the password you supply.
     • Username: SYS
     • Password: Supply the password for this user. The password must meet the following criteria:

       A strong password for SYS, SYSTEM, TDE wallet, and PDB Admin. The password must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be _, #, or -. The password must not contain the username (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reversed order and regardless of casing.

     • Confirm password: Re-enter the SYS password you specified.
     • Using a TDE wallet password is optional. If you are using customer-managed encryption keys stored in a vault in your tenancy, the TDE wallet password is not applicable to your DB system. Use Show Advanced Options at the end of the Create Database dialog to configure customer-managed keys.

       If you are using customer-managed keys, or if you want to specify a different TDE wallet password, uncheck the Use the administrator password for the TDE wallet box. If you are using customer-managed keys, leave the TDE password fields blank. To set the TDE wallet password manually, enter a password in the Enter TDE wallet password field, and then confirm by entering it into the Confirm TDE wallet password field.

   • Configure database backups: Specify the settings for backing up the database to Autonomous Recovery Service or Object Storage:

     • Enable automatic backup: Check the check box to enable automatic incremental backups for this database. If you are creating a database in a security zone compartment, you must enable automatic backups.
     • Backup Destination: Your choices are Autonomous Recovery Service or Object Storage.
     • Backup Scheduling:
       • Object Storage (L0):
         • Full backup scheduling day: Choose a day of the week for the initial and future L0 backups to start.
         • Full backup scheduling time (UTC): Specify the time window when the full backups start when the automatic backup capability is selected.

         • Take the first backup immediately: A full backup is an operating system backup of all datafiles and the control file that constitute an Oracle Database. A full backup should also include the parameter file(s) associated with the database. You can take a full database backup when the database is shut down or while the database is open. You should not normally take a full backup after an instance failure or other unusual circumstances.

           If you choose to defer the first full backup your database may not be recoverable in the event of a database failure.

       • Object Storage (L1):
         • Incremental backup scheduling time (UTC): Specify the time window when the incremental backups start when the automatic backup capability is selected.
       • Autonomous Recovery Service (L0):
         • Scheduled day for initial backup: Choose a day of the week for the initial backup.
         • Scheduled time for initial backup (UTC): Select the time window for the initial backup.

         • Take the first backup immediately: A full backup is an operating system backup of all datafiles and the control file that constitute an Oracle Database. A full backup should also include the parameter file(s) associated with the database. You can take a full database backup when the database is shut down or while the database is open. You should not normally take a full backup after an instance failure or other unusual circumstances.

           If you choose to defer the first full backup your database may not be recoverable in the event of a database failure.

       • Autonomous Recovery Service (L1):
         • Scheduled time for daily backup (UTC): Specify the time window when the incremental backups start when the automatic backup capability is selected.
     • Deletion options after database termination: Options that you can use to retain protected database backups after the database is terminated. These options can also help restore the database from backups in case of accidental or malicious damage to the database.
       • Retain backups for the period specified in your protection policy or backup retention period: Select this option if you want to retain database backups for the entire period defined in the Object Storage Backup retention period or Autonomous Recovery Service protection policy after the database is terminated.
       • Retain backups for 72 hours, then delete: Select this option to retain backups for a period of 72 hours after you terminate the database.

     • Backup Retention Period/Protection Policy: If you choose to enable automatic backups, you can choose a policy with one of the following preset retention periods, or a Custom policy.

       Object Storage Backup retention period: 7, 15, 30, 45, 60. Default: 30 days. The system automatically deletes your incremental backups at the end of your chosen retention period.

       Autonomous Recovery Service protection policy:

       • Bronze: 14 days
       • Silver: 35 days
       • Gold: 65 days
       • Platinum: 95 days
       • Custom defined by you
       • Default: Silver - 35 days
     • Enable Real-Time Data Protection: Real-time protection is the continuous transfer of redo changes from a protected database to Autonomous Recovery Service. This reduces data loss and provides a recovery point objective (RPO) near 0. This is an extra cost option.

6. Click Show Advanced Options to specify advanced options for the database:

   • Management:

     Oracle SID prefix: The Oracle Database instance number is automatically added to the SID prefix to create the INSTANCE_NAME database parameter. The INSTANCE_NAME parameter is also known as the SID. The SID is unique across the cloud VM Cluster. If not specified, SID prefix defaults to the db_name.

     Note
     
     Entering an SID prefix is only available for Oracle 12.1 databases and above.

     The SID prefix must meet the requirements:

     • Maximum of 12 characters
     • Contain only alphanumeric characters. You can, however, use underscore (_), which is the only special character that is not restricted by this naming convention.
     • Begin with an alphabetic character
     • Unique in the VM cluster
     • DO NOT use the following reserved names: grid, ASM
   • Character set: The character set for the database. The default is AL32UTF8.
   • National character set: The national character set for the database. The default is AL16UTF16.

   • Encryption:

     If you are creating a database in an Exadata Cloud Service VM Cluster, then you can choose to use encryption based on encryption keys that you manage. By default, the database is configured using Oracle-managed encryption keys. To configure the database with encryption based on encryption keys you manage:

     1. Select Use customer-managed keys. You must have a valid encryption key in Oracle Cloud Infrastructure Vault service. See Let security admins manage vaults, keys, and secrets.
        Note
        
        You must use AES-256 encryption keys for your database.
     2. Choose a Vault.
     3. Select a Master encryption key.
     4. To specify a key version other than the latest version of the selected key, check Choose the key version and enter the OCID of the key you want to use in the Key version OCID field.
     Note
     
     The Key version will only be assigned to the container database (CDB), and not to its pluggable database (PDB). PDB will be assigned an automatically generated new key version.
   • Tags: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags . If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
7. Click Create Database.

After database creation is complete, the status changes from Provisioning to Available, and on the database details page for the new database, the Encryption section displays the encryption key name and the encryption key OCID.

Learn to manage administrator (SYS user) and TDE wallet passwords.

1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata Database Service on Exascale Infrastructure
2. Choose your Compartment that contains the VM cluster that hosts the database that you want to change passwords.
3. Click the name of the VM cluster that contains the database that you want to change passwords.
4. In the Resources list of the VM Cluster Details page, click Databases.
5. Click the name of the database that you want to change passwords.

   The Database Details page displays information about the selected database.

6. On the Database Details page, click More actions, and then click Manage passwords.
7. In the resulting Manage passwords dialog, click Update Administrator Password or Update TDE Wallet Password.

   Depending on the option you select, the system displays the fields to edit.

   • Update Administrator Password: Enter the new password in both the New administrator password and Confirm administrator password fields.
     Note
     
     The Update Administrator Password option will change the sys user password only. Passwords for other administrator accounts such as system, pdbadmin, and TDE wallet will not be changed.
   • Update TDE Wallet Password: Enter the current wallet password in the Enter existing TDE wallet password field, and then enter the new password in both the New TDE wallet password and Confirm TDE wallet password fields.
8. Click Apply to update your chosen password.

To view the details of a Protected Database, use this procedure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure
2. Choose your Compartment.
3. Navigate to the database:

   Under Exadata at Oracle Cloud, click Exadata VM Clusters.

   In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster details page, in the Databases table, click the name of the database to display the Database Details page.The Backup section displays the state of the automatic backups. If the Autonomous Recovery Service is the destination, a link will be available which includes additional details. You can also check if Real-time Data Protection is enabled or disabled. Click the Autonomous Recovery Service link to be taken to the page containing the Protected Database details.For more information about Protected Databases, see Viewing Protected Database Details.

Learn how to use a backup to create a database on Exadata Database Service on Exascale Infrastructure.

Before you begin, note the following:

• When you create a database from a backup, the availability domain can be the same as where the backup is hosted, or a different one across regions.
• The Oracle Database software version you specify must be the same or later version as that of the backed-up database.
• If you are creating a database from an automatic backup, then you can choose any level 0 weekly backup, or a level 1 incremental backup created after the most recent level 0 backup. For more information on automatic backups, see Using the Console
• If the backup being used to create a database is in a security zone compartment, the database cannot be created 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. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.
3. Navigate to a backup.
   • Standalone backups: Click Standalone Backups under Oracle Exadata Database Service on Exascale Infrastructure.

   • Automatic backups: Navigate to the Database Details page of the database associated with the backup:

     • Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

     Click the name of the database associated with the backup that you will use to create the new database. Locate the backup in the list of backups on the Database Details page.

4. Click the Actions menu icon () for the backup you chose.
5. Click Create Database. On the Create Database from Backup page, configure the database as follows.
6. In the Provide basic information for the Exadata infrastructure section:
   • Select an availability domain: It could be the same as the availability domain that hosts the backup or a different one within the same region
   • Select Exadata infrastructure: Select an Exadata infrastructure from the chosen compartment. Click the Change Compartment hyperlink to choose a different compartment.
7. In the Configure your DB system section:
   • Choose a cloud VM cluster to run the database from the Select a VM cluster drop-down list.
8. In the Configure Database Home section:
   • Select an existing Database Home: If you choose this option, make a selection from the Select a Database Home drop-down list.
     Note
     
     You can not create a database from backup in the same Database home where the source database exists.
   • Create a new Database home: If you choose this option, then enter a name for the new Database home in the Database Home display name field. Click Change Database Image to select a database software image for the new Database home. In the Select a Database Software Image panel, do the following:
     1. Select the compartment containing the database software image you want to use to create the new Database home.
     2. Select the Oracle Database software version that the new Database home will use, and then choose an image from the list of available images for your selected software version.
     3. Click Select.
9. In the Configure database section:
   Note
   
   You cannot modify the db_name, db_unique_name , and SID prefix after creating the database.
   • In the Database name field, name the database or accept the default name. The database name must meet the requirements:
     • Maximum of 8 characters
     • Contain only alphanumeric characters
     • Begin with an alphabetic character
     • Cannot be part of first 8 characters of a different database's db_unique_name on the VM cluster
     • Must not use the following reserved names: grid, ASM
   • Database unique name: Specify a value for the DB_UNIQUE_NAME database parameter. The unique name must meet the requirements:
     • Maximum of 30 characters
     • Contain only alphanumeric or underscore (_) characters
     • Begin with an alphabetic character
     • Unique across the VM cluster. Recommended to be unique across the tenancy.
     If not specified, the system automatically generates a unique name value, as follows:

     <db_name>_<3_chars_unique_string>_<region-name>

   • Administrator username: This read-only field displays the username for the administrator, "sys".
   • In the Password and Confirm password fields, enter and re-enter a password.

     A strong password for SYS administrator must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be _, #, or -. The password must not contain the user name (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reverse order and regardless of casing.

10. In the Enter the source database's TDE wallet or RMAN password field, enter a password that matches either the Transparent Data Encryption (TDE) wallet password or RMAN password for the source database.
11. Click Show Advanced Options to specify advanced options for the database:
    • Management

      Oracle SID prefix: This option is in the Management tab. The Oracle Database instance number is automatically added to the SID prefix to create the INSTANCE_NAME database parameter. If not provided, then the SID prefix defaults to the first twelve characters of the db_name.

      The SID prefix must meet the requirements:

      • Maximum of 12 characters
      • Contain only alphanumeric characters
      • Begin with an alphabetic character
      • Unique in the VM cluster
      • Must not use the following reserved names: grid, ASM
12. Click Create Database.

Use this procedure to create a database from the latest backup on Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure
2. Choose your Compartment.
3. Navigate to the cloud VM cluster that contains the source database you are using to create the new database:
   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.
4. Under Databases, click the name of the database you are using as the source for the new database.
5. On the Database Details page, click Create Database from Last Backup.
6. In the Provide basic information for the Exadata infrastructure section:
   • Select an availability domain: It could be the same as the availability domain that hosts the backup or a different one within the same region.
   • Select Exadata infrastructure: Select an Exadata infrastructure from the chosen compartment. Click the Change Compartment hyperlink to choose a different compartment.
7. On the Create Database from Backup page, configure the database as follows.
8. In the Configure your DB system section: Choose a cloud VM cluster to run the database from the Select a VM cluster drop-down list.
9. In the Configure Database Home section:
   • Select an existing Database Home: If you choose this option, make a selection from the Select a Database Home drop-down list.
   • Create a new Database home: If you choose this option, enter a name for the new Database Home in the Database Home display name field. Click Change Database Image to select a database software image for the new Database Home. In the Select a Database Software Image panel, do the following:
     1. Select the compartment containing the database software image you want to use to create the new Database Home.
     2. Select the Oracle Database software version that the new Database Home will use, then choose an image from the list of available images for your selected software version.
     3. Click Select.
10. In the Configure database section:
    Note
    
    You cannot modify the db_name, db_unique_name, and SID prefix after creating the database.

    • Database name: The name for the database. The database name must meet the requirements:

      • Maximum of 8 characters
      • Contain only alphanumeric characters
      • Begin with an alphabetic character
      • Cannot be part of first 8 characters of a DB_UNIQUE_NAME on the VM cluster
      • DO NOT use the following reserved names: grid, ASM

    • Database unique name: Optionally, specify a value for the DB_UNIQUE_NAME database parameter. The value is case insensitive.

      The unique name must meet the requirements:

      • Maximum of 30 characters
      • Contain only alphanumeric or underscore (_) characters
      • Begin with an alphabetic character
      • Unique across the VM cluster. Recommended to be unique across the tenancy.
      If not specified, the system automatically generates a unique name value, as follows:

      <db_name>_<3_chars_unique_string>_<region-name>

    • Administrator username: This read-only field displays the username for the administrator, sys.
    • In the Password and Confirm password fields, enter and re-enter a password.

      A strong password for SYS administrator must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be _, #, or -. The password must not contain the user name (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reverse order and regardless of casing.

11. In the Enter the source database's TDE wallet or RMAN password field, enter a password that matches either the Transparent Data Encryption (TDE) wallet password or RMAN password for the source database.
12. Click Show Advanced Options to specify advanced options for the database.
    • Management
      Oracle SID prefix: The Oracle Database instance number is automatically added to the SID prefix to create the INSTANCE_NAME database parameter. The INSTANCE_NAME parameter is also known as the SID. The SID is unique across the cloud VM cluster. If not specified, SID prefix defaults to the first 12 characters of the db_name. The SID prefix must meet the requirements:

      • Maximum of 12 characters
      • Contain only alphanumeric characters
      • Begin with an alphabetic character
      • Unique in the VM cluster
      • DO NOT use the following reserved names: grid, ASM
13. Click Create Database.

To patch a single Oracle Database in your Oracle Exadata Database Service on Exascale Infrastructure instance, you move it to another Database Home.

You can move a database to any Database Home that meets at either of the following criteria:

• The target Database Home uses the same Oracle Database software version (including patch updates) as the source Database Home
• The target Database Home is based on either the latest version of the Oracle Database software release used by the database, or one of the three prior versions of the release

Moving a database to a new Database Home brings the database up to the patch level of the target Database Home. For information on patching Database Homes, see Using the Console to Manage Databases on Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure
2. Choose your Compartment.
3. Navigate to the database you want to move.

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, click the name of the VM cluster that contains the database you wan to move.

4. Click More Actions, then click Move to Another Home.
5. Select the target Database Home.
6. Click Move Database.

7. Confirm the move operation.

   The database is moved in a rolling fashion. The database instance will be stopped, node by node, in the current home and then restarted in the destination home. While the database is being moved, the Database Home status displays as Moving Databse. When the operation completes, Database Home is updated with the current home. Datapatch is run automatically, as part of the database move, to complete post-patch SQL actions for all patches, including one-offs, on the new Database Home. If the database move operation is unsuccessful, then the status of the database displays as Failed, and the Database Home field provides information about the reason for the failure.

Use this procedure to terminate a database on Oracle Exadata Database Service on Exascale Infrastructure.

You'll get the chance to back up the database prior to terminating it. This creates a standalone backup that can be used to create a database later. We recommend that you create this final backup for any production (non-test) database.

You cannot terminate a database that is assuming the primary role in a Data Guard association. To terminate it, you can switch it over to the standby role.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure
2. Choose your Compartment.

3. Navigate to the database:

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster details page, in the Databases table, click the name of the database to display the Database Details page.
4. Click More Actions, and then click Terminate.
   For the database using Oracle Cloud Infrastructure Object Storage or Oracle Database Autonomous Recovery Service: In the confirmation dialog,

   • Review the message about the backup retention policy.
   • Configure automatic backups as needed.
   • Type the name of the database to confirm the termination
5. Click Terminate Database.

   The database's status indicates Terminating.

   Note
   
   The database stays in a terminated state with backups listed until all backups are expired.

Use this procedure to rotate the Vault encryption key or or change the encryption management configuration.

After you provision a database in an Exadata DB system or cloud VM cluster, you can rotate the Vault encryption key or change the encryption management configuration for that database.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure
2. Choose your compartment from the Compartment drop-down.
3. Navigate to the cloud VM cluster that contains the database for which you want to change encryption management or to rotate a key.

   Cloud VM clusters: Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, locate the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

4. In the Databases section, click the name of the database for which you want to change encryption management or to rotate a key to display its details page.
5. Click the More Actions drop-down.
6. Click Manage encryption key.
   To rotate an encryption key on a database using customer-managed keys:

   Note
   
   Generate a new master encryption key version. Only the CDB root key version is changed or rotated to a new one. It doesn't generate a new key version for the dependent PDBs. Rotate customer-managed keys periodically to comply with security compliance and regulatory mandates.
   1. Click Rotate Encryption Key to display a confirmation dialog.
   2. Click Update.

   To assign a new key version:

   Assign a new key version (BYOK) to CDB while creating or after provisioning it.

   1. Click Assign a new key version.
   2. In the Key version OCID field, enter the OCID of the new key version you want to assign.
   3. Click Update.

      To copy the Key version OCID:

      1. Find the Vault and the Key details on the Key Details page (Key Management & Secret Management >> Vault >> <Vault> >> Key Details) by searching with the KMS key OCID provided in the CDB details page.
      2. Copy the OCID and paste it in the Key version OCID field.

   To change key management type from Oracle-managed keys to customer-managed keys:

   1. Click Change Key Management Type.
   2. Select Use customer-managed keys.

      You must have a valid encryption key in Oracle Cloud Infrastructure Vault service and provide the information in the subsequent steps. See Key and Secret Management Concepts.

   3. Choose a vault from the Vault in compartment drop-down. You can change the compartment by clicking the Change Compartment link.
   4. Select an encryption key from the Master encryption key in compartment drop-down. You can change the compartment containing the encryption key you want to use by clicking the Change Compartment link.
   5. If you want to use an encryption key that you import into your vault, then select the Choose the key version check box and enter the OCID of the key you want to use in the Key version OCID field.
      Note
      
      If you do not choose a version, the latest version of the key is used.
7. Click Update.

On the database details page for this database, the Encryption section displays the encryption key name and the encryption key OCID.

To create the PDB, complete this procedure for Oracle Exadata Database Service on Exascale Infrastructure

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster details page, in the Databases table, click the name of the database to display the Database Details page.

4. On the Database Details page, click Pluggable Databases in the Resources section of the page.
5. Click Create Pluggable Database.

6. In the Create Pluggable Database dialog, enter the following:

   • PDB Name: Enter a name for the PDB. The name must begin with an alphabetic character and can contain a maximum of 30 alphanumeric characters. Note: For bare metal DB systems, you cannot have two PDBs in the same database that use the same PDB name. You can use the same name for PDBs in different databases within the same DB system.
   • Unlock my PDB Admin account: Optional. Select this option to specify a PDB Admin password and configure the PDB to be unlocked at creation.
   • PDB Admin password: If you clicked Unlock my PDB Admin account, then create and enter a PDB admin password. The password must contain the following:
     • A minimum of 9 and a maximum of 30 characters
     • At least two uppercase characters
     • At least two lowercase characters
     • At least two special characters. The valid special characters are: underscore ( _ ), a hash sign (#), and a dash (-). You can use two of the same characters or any combination of two of the same characters.
     • At least two numeric characters (0 - 9)
   • Confirm PDB Admin password: Reenter the PDB admin password.
   • TDE wallet password: Applicable only to databases using Oracle-managed encryption keys. Enter the TDE wallet password for the parent CDB.
   • Take a backup of the PDB immediately after creating it: You must enable auto-backup on the CDB to back up a PDB immediately after creating it. This check box is checked by default if auto-backup was enabled on the CDB.
     Note
     
     If the check box is unchecked, the system displays a warning stating that PDB cannot be recovered until the next daily backup has been successfully completed.
7. Click Create Pluggable Database.

WHAT NEXT?

After creating your PDB, you can get connection strings for the administrative service using the OCI Console.

To relocate the PDB, complete this procedure for Oracle Exadata Database Service on Exascale Infrastructure

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster details page, in the Databases table, click the name of the database to display the Database Details page.

4. On the Database Details page, click Pluggable Databases in the Resources section of the page.
5. Click the name of the PDB that you want to relocate.

   From the Pluggable Database details page, click More Actions, and then select Relocate.

   (or)

   Click the Actions menu (three dots) and select Relocate.

6. In the resulting Relocate Pluggable Database window, enter the following:
   • VM Cluster: Use the menu to select the destination VM cluster.
   • Destination database: Use the menu to select an existing database where the PDB will be created. This database can be of the same version as the CDB the source PDB is in or of a higher version.
   • New PDB name for the clone: The name must begin with an alphabetic character and can contain up to 30 characters. To keep the PDB name the same, just re-enter the source PDB name.
   • Database TDE wallet password: Enter the TDE wallet password for the parent CDB of the source PDB.
   • Unlock my PDB Admin Account:
     • To enter the administrator's password, check this check box.
       • PDB Admin Password: Enter PDB admin password. The password must contain the following:
         • a minimum of 9 and a maximum of 30 characters
         • at least two uppercase characters
         • at least two lowercase characters
         • at least two special characters. The valid special characters are underscore ( _ ), a pound or hash sign (#), and dash (-). You can use two of the same characters or any combination of two of the same characters.
         • at least two numeric characters (0 - 9)
       • Confirm PDB Admin Password: Enter the same PDB Admin password in the confirmation field.
     • To skip entering the administrator's password, uncheck this check box. If you uncheck this check box, then the PDB is created but you cannot use it. To use the PDB, you must reset the administrator password.
       Note
       
       When you create a new PDB, a local user in the PDB is created as the administrator and granted the PDB_DBA role locally to the administrator.
       To reset the password:

       1. Connect to the container where your PDB exists using the SQL*Plus CONNECT statement.

          SQL> show con_name;
          CON_NAME
          ------------------------
          CDB$ROOT

          For more information, see Administering a CDB and Administering PDBs in Oracle Multitenant Administrator’s Guide.

       2. Find the administrator name of your PDB:

          SQL> select grantee from cdb_role_privs where con_id = (select con_id from cdb_pdbs where pdb_name = '<PDB_NAME>') and granted_role = 'PDB_DBA';

       3. Switch into your PDB:

          SQL> alter session set container=<PDB_NAME>;
          Session altered.
          SQL> show con_name;
          CON_NAME
          ------------------------
          <PDB_NAME>

       4. Reset the PDB administrator password:

          SQL> alter user <PDB_Admin> identified by <PASSWORD>;
          User altered.

   • Source database SYS password: Enter the database admin password.
   • Database link: Enter the user name and password for the database link. Note that the user must be precreated in the source database. The DB link will be created in the destination using that username and password.
   • Take a backup of the PDB immediately after creating it: You must enable auto-backup on the CDB to back up a PDB immediately after creating it. This check box is checked by default if auto-backup was enabled on the CDB.
     Note
     
     If the checkbox is unchecked, then the system displays a warning stating that PDB cannot be recovered until the next daily backup has been successfully completed.
   • Advanced Options

     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.

7. Click Relocate pluggable database.
   Note
   
   Relocate will incur downtime during the process. The time required is based on the size of the PDB.

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.

Use the CreatePluggableDatabase API to create pluggable databases on Oracle Exadata Database Service on Exascale Infrastructure.

For the complete list of APIs for the Database service, see Database Service API.

To start the PDB, complete this procedure for Oracle Exadata Database Service on Exascale Infrastructure

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database.

   • Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the Cloud VM Cluster details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to start. Click the PDB name to display details about it.
6. Click Start.
7. In the Start PDB dialog, click Start PDB to confirm the start operation.

To stop the PDB, complete this procedure for Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database.

   • Under Oracle Exadata Database Service on Dedicated Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the Cloud VM Cluster details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to stop. Click the PDB name to display details about it.
6. Click Start.
7. In the Stop PDB dialog, click Stop PDB to confirm the stop operation.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Cloud VM clusters (new resource model) Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   DB systems Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

   On the cloud VM cluster or DB system details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to delete. Click the PDB name to display details about it.
6. Click More Actions, then choose Delete.
7. In the Delete PDB dialog box, enter the name of the PDB that you want to delete to confirm the action, then click Delete PDB.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Cloud VM clusters (new resource model) Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   DB systems Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

   On the cloud VM cluster or DB system details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the PDB, and then click its name to display details about it.
6. Click PDB Connection.
7. In the Pluggable Database Connection dialog, use the Show and Copy links to display and copy connection strings, as needed.
8. Click Close to exit the dialog.

Complete this procedure on Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to clone, and then click its name to display details about it.
6. Click Clone.

7. In the Clone PDB dialog box, enter the following:

   • Select clone type: Select Local clone to create a copy of the source PDB to the same CDB.
   • Exadata VM Cluster: Use the menu to select the cloud VM cluster of the target database.
     Note
     
     The target VM Cluster may be on a different Exadata infrastructure.
   • Destination database: This field is disabled.
   • PDB name: Provide a name for the new cloned PDB. The name must begin with an alphabetic character and can contain up to 30 characters.
   • Database TDE wallet password: Not applicable for databases using customer-managed keys from the Vault service. Enter the TDE wallet password for the parent database (CDB) of the source PDB.
   • Unlock my PDB Admin account: Optional. Select this option to specify a PDB Admin password and configure the PDB to be unlocked at creation.
   • PDB Admin password: Create and enter a new PDB Admin password. The password must contain the following:
     • 9–30 characters
     • At least two uppercase characters
     • At least two lowercase characters
     • At least two special characters. The valid special characters are: underscore ( _ ), a hash sign (#), and a dash (-). You can use two of the same characters or any combination of two of these characters.
     • At least two numeric characters (0-9)
   • Confirm PDB Admin password: Enter the PDB Admin password again to confirm.
   • Take a backup of the PDB immediately after creating it: You must enable auto-backup on the CDB to back up a PDB immediately after creating it. This check box is checked by default if auto-backup was enabled on the CDB.
     Note
     
     If the checkbox is unchecked, the system displays a warning stating that PDB cannot be recovered until the next daily backup has been successfully completed.
   • Optional. Enable thin clone: Select this option to leverage Exascale redirect-on-write technology to create a thin clone of the PDB. This option results in the reuse of duplicate blocks with the parent PDB, shared with the clone. Deselecting this option results in a traditional, full clone with all blocks copied, and fully independent from the parent.
   • Advanced Options

     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.

8. Click Clone pluggable database.

Complete this procedure on Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to clone, and then click its name to display details about it.
6. Click Clone.

7. In the Clone PDB dialog box, enter the following:

   • Select clone type: Select Remote clone to create a copy of the source PDB to the same CDB.
   • Exadata VM Cluster: Use the menu to select the cloud VM cluster of the target database.
     Note
     
     The target VM Cluster may be on a different Exadata infrastructure.
   • Destination database: Use the menu to select an existing database where the PDB will be created. This database can be of the same version as the CDB the source PDB is in or of a higher version.
   • PDB name: Provide a name for the new cloned PDB. The name must begin with an alphabetic character and can contain up to 30 characters.
   • Database TDE wallet password: Not applicable for databases using customer-managed keys from the Vault service. Enter the TDE wallet password for the parent database (CDB) of the source PDB.
   • Unlock my PDB Admin account: Optional. Select this option to specify a PDB Admin password and configure the PDB to be unlocked at creation.
   • PDB Admin password: Create and enter a new PDB Admin password. The password must contain the following:
     • 9–30 characters
     • At least two uppercase characters
     • At least two lowercase characters
     • At least two special characters. The valid special characters are: underscore ( _ ), a hash sign (#), and a dash (-). You can use two of the same characters or any combination of two of these characters.
     • At least two numeric characters (0-9)
   • Confirm PDB Admin password: Enter the PDB Admin password again to confirm.
   • Database link: Enter the user name and password for the database link. Note that the user must be precreated in the source database. The DB link will be created in the destination using that username and password.
   • Take a backup of the PDB immediately after creating it: You must enable auto-backup on the CDB to back up a PDB immediately after creating it. This check box is checked by default if auto-backup was enabled on the CDB.
     Note
     
     If the checkbox is unchecked, the system displays a warning stating that PDB cannot be recovered until the next daily backup has been successfully completed.
   • Optional. Enable thin clone: Select this option to leverage Exascale redirect-on-write technology to create a thin clone of the PDB. This option results in the reuse of duplicate blocks with the parent PDB, shared with the clone. Deselecting this option results in a traditional, full clone with all blocks copied, and fully independent from the parent.
   • Advanced Options:
     • 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.
8. Click Clone pluggable database.

Complete this procedure on Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   DB systems Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

   On the cloud VM cluster or DB system details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to clone, and then click its name to display details about it.
6. Click Clone.

7. In the Clone PDB dialog box, enter the following:

   • Select clone type: Select Refreshable clone to create a copy of the source PDB to the same CDB.

     For more information about refreshable clones, see About Refreshable Clone PDBs.

   • Exadata VM Cluster: Use the menu to select the cloud VM cluster of the target database.
     Note
     
     The target VM Cluster may be on a different Exadata infrastructure.
   • Destination database: Use the menu to select an existing database where the PDB will be created. This database can be of the same version as the CDB the source PDB is in or of a higher version.
   • PDB name: Provide a name for the new cloned PDB. The name must begin with an alphabetic character and can contain up to 30 characters.
   • Database TDE wallet password: Not applicable for databases using customer-managed keys from the Vault service. Enter the TDE wallet password for the parent database (CDB) of the source PDB.
   • Unlock my PDB Admin account: Optional. Select this option to specify a PDB Admin password and configure the PDB to be unlocked at creation.
   • PDB Admin password: Create and enter a new PDB Admin password. The password must contain:
     • 9–30 characters
     • At least two uppercase characters
     • At least two lowercase characters
     • At least two special characters. The valid special characters are: underscore ( _ ), a hash sign (#), and a dash (-). You can use two of the same characters or any combination of two of these characters.
     • At least two numeric characters (0-9)
   • Confirm PDB Admin password: Enter the PDB Admin password again to confirm.
   • Database link: Enter the user name and password for the database link. Note that the user must be precreated in the source database. The DB link will be created in the destination using that username and password.
   • Take a backup of the PDB immediately after creating it: You must enable auto-backup on the CDB to back up a PDB immediately after creating it. This check box is checked by default if auto-backup was enabled on the CDB.
     Note
     
     If the checkbox is unchecked, the system displays a warning stating that PDB cannot be recovered until the next daily backup has been successfully completed.
   • Optional. Enable thin clone: Select this option to leverage Exascale redirect-on-write technology to create a thin clone of the PDB. This option results in the reuse of duplicate blocks with the parent PDB, shared with the clone. Deselecting this option results in a traditional, full clone with all blocks copied, and fully independent from the parent.
   • Advanced Options:
     • 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.
8. Click Clone pluggable database.

Complete this procedure on Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Under Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to refresh, and then click its name to display details about it.
6. Click More Actions and select Refresh.
7. In the resulting Refresh dialog box, click Refresh to confirm.

Complete this procedure on Oracle Exadata Database Service on Exascale Infrastructure.

1. Open the navigation menu. Click Oracle Database, then click Exadata Database Service on Exascale Infrastructure.
2. Choose your Compartment.

3. Navigate to the database:

   Under Oracle Exadata Database Service on Exascale Infrastructure, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

   On the cloud VM cluster or DB system details page, in the Databases table, click the name of the database to display the Database Details page.

4. Click Pluggable Databases in the Resources section of the page.
5. In the list of pluggable databases, find the pluggable database (PDB) you want to convert to a regular PDB, and then click its name to display details about it.
6. In the resulting Convert to regular PDB dialog box, enter the following:
   • Database TDE wallet password: Not applicable for databases using customer-managed keys from the Vault service. Enter the TDE wallet password for the parent database (CDB) of the source PDB.
   • Take a backup of the PDB immediately after creating it: You must enable auto-backup on the CDB to back up a PDB immediately after creating it. This check box is checked by default if auto-backup was enabled on the CDB.
     Note
     
     If the checkbox is unchecked, then the system displays a warning stating that PDB cannot be recovered until the next daily backup has been successfully completed.
7. Click Convert.

Learn how to manage pluggable databases (PDBs) using the pluggable database API endpoints.

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.

Use these APIs to clone pluggable databases:

• LocalclonePluggableDatabase
• RemoteclonePluggabledatabase

For the complete list of APIs for the Database service, see Database Service API.