Oracle Cloud Infrastructure Documentation

Base Database - Clone

    1. From the Oracle AI Database@Google Cloud dashboard, select Core Database Service, and then select Base Database Service from the left menu.

    2. From the DB systems list, select the Base Database that you are using.

    3. Select the Manage in OCI link.

      This screenshot shows how to clone a Base Database.

  • Note

    Note: If you use an identity provider such as Okta or Ping instead of Google Cloud Identity, complete the Federation step before proceeding.

    Clone a DB System

    1. From the OCI console, select Oracle Base Database Service.

    2. From the left menu, select DB Systems, and then select the Base Database that you want to clone.

    3. Select the Actions button and then select Clone.

      This screenshot shows how to clone a Base Database.

    4. On the Clone DB system page, configure the settings to create a clone of the source DB system. Cloning creates a copy of the source DB system at a specific point in time, including the storage configuration, software, and database volumes.

      1. In the Source DB system details section, review the source DB system information and configure the settings for the cloned DB system

        1. Source DB system: Review the name of the source DB system to be cloned.

        2. Total node count: Review the total number of nodes in the source DB system.

        3. Oracle Database software edition: Review the Oracle AI Database software edition associated with the source DB system.

        4. DB system name: Enter a name for the cloned DB system or retain the prepopulated name. The Display name must be 1 to 255 characters, of letters, numbers, underscores () and hyphens (-). Display name must start with a letter or underscore() and cannot contain two successive hyphens(-).

        5. Subscription: Review the selected subscription. This field is read-only.

        6. Compartment: Select the compartment in which to create the cloned DB system from the dropdown list.

      2. In the SSH Keys section, configure the SSH keys for accessing the cloned DB system. Select one of the following options:

        1. Generate SSH key pair: Select this option to generate a new SSH key pair. This option is selected by default.

        2. Upload SSH key files: Select this option to upload existing SSH public key files.

        3. Paste SSH keys: Select this option to paste existing SSH public keys.

          This screenshot shows how to clone a Base Database.

        4. Comment: Enter a comment to identify the generated SSH key pair.

        5. Save private key: Select Save private key to download the generated private key. Store the private key securely because it will not be displayed again. The private key is required to connect to the DB system using SSH.

        6. Save public key: Select Save public key to download the generated public key.

      3. In the License type section, select the Oracle AI Database software licensing option for the cloned DB system. Select one of the following options:

        1. License included: Select this option to subscribe to new Oracle AI Database software licenses and the Database service. This option is selected in the screenshot.

        2. Bring Your Own License (BYOL): Select this option to use your organization’s existing Oracle AI Database software licenses with the Database service.

      4. In the Network Information section, configure the network settings for the cloned DB system.

        1. Create VCN: Select Create VCN to create a new virtual cloud network (VCN).

        2. Compartment: Select the compartment containing the VCN from the dropdown list.

        3. Virtual cloud network: Select the VCN from the dropdown list.

        4. Compartment: Select the compartment containing the client subnet from the dropdown list.

        5. Client subnet: Select the client subnet from the dropdown list.

          This screenshot shows how to clone a Base Database.

        6. Use network security groups to control traffic: Enable the option if you want to add the DB system to one or more network security groups (NSGs) that control inbound and outbound traffic. You can configure NSGs later if needed.

        7. Hostname prefix: Enter a hostname prefix for the cloned DB system or retain the prepopulated value.

        8. Host domain name: Review the host domain name displayed for the selected network.

        9. Host and domain URL: Review the generated host and domain URL. This value is determined by the hostname prefix and host domain name.

        10. Select one of the following options as IPv4 address assignment:

          1. Automatically assign IPv4 addresses from subnet: Select this option to automatically assign IPv4 addresses from the selected subnet. This option is selected in the screenshot.

          2. Manually assign IPv4 addresses: Select this option to manually assign IPv4 addresses.

          This screenshot shows how to clone a Base Database.

      5. In the Diagnostics collection section, review the information about diagnostics collection and notifications for the cloned DB system. Enable diagnostics collection and notifications to help you and Oracle Cloud Operations identify, investigate, track, and resolve guest VM issues quickly and effectively. You must subscribe to events to receive notifications.

        1. Enable diagnostic events: Select this checkbox to enable diagnostic event collection.

        2. Enable health monitoring: This option is unavailable.

        3. Enable incident logs and trace collection: Select this checkbox to enable incident logs and trace collection.

      6. Expand the Advanced Options section to manage Security and Tags. From the Security section, you can add a security attribute to control access for your resources using Zero Trust Packet Routing (ZPR) policy. From the Tags section, you can add tags to organize your resources. These are optional steps.

      7. Configure the database details for the cloned DB system.

        1. Database name: Enter a name for the database or retain the prepopulated value.

        2. Database unique name suffix: Enter a suffix for the database unique name.

        3. Database unique name: Review the database unique name displayed in this field.

          This screenshot shows how to clone a Base Database.

      8. In the Administrator credentials section, configure the administrator credentials for the cloned database.

        1. Username: Review the displayed database administrator username.

        2. Password: Enter the password for the database administrator. The Password must be 9 to 30 characters and contain at least 2 uppercase, 2 lowercase, 2 special, and 2 numeric characters. The special characters must be _, #, or -.

        3. Confirm password: Re-enter the password to confirm it matches the value entered in the Password field.

      9. Select the Clone button to initiate the DB system cloning operation.

        This screenshot shows how to clone a Base Database.

    Clone a Pluggable Database

    1. From the OCI console, select Oracle Base Database Service.

    2. From the left menu, select DB Systems, and then select the Base Database that you are using.

    3. Select the Databases tab, and then select the Container Database (CDB) that you are using.

      This screenshot shows how to clone a Base Database.

    4. Select the Pluggable Databases tab, and then select the Pluggable Database (PDB) that you want to clone.

    5. Select More actions in the upper-right corner of the Pluggable Database Details page and then select the Clone.

      This screenshot shows how to clone a Base Database.

    6. In the Clone pluggable database panel, configure the settings to create a clone of the selected pluggable database (PDB).

      1. Select a Clone type according to your requirements from one of the following options:

        1. Local clone: Creates a copy of the source PDB in the same container database.

        2. Remote clone: Creates a copy of the source PDB in a different container database.

        3. Refreshable clone: Creates a copy of the source pluggable database on a different container database and be able to refresh the cloned DPB.

      2. In the Destination section, review the destination details for the cloned PDB.

        1. Compartment: Review the compartment displayed for the destination. This field is read-only.

        2. DB System: Review the destination DB system which the pluggable database will be cloned. This field is read-only.

        3. Database: Select the destination database to which the pluggable database must be cloned.

          This screenshot shows how to clone a Base Database.

      3. In the New PDB section, configure the details for the cloned pluggable database.

        1. PDB name: Enter a name for the cloned pluggable database. The name must begin with an alphabetic character and can contain a maximum of 30 alphanumeric characters.

        2. Database SYS password: Enter the SYS password for the database.

        3. Database TDE wallet password: Enter the database Transparent Data Encryption (TDE) wallet password.

        4. Unlock the PDB admin account: This option is optional. Enable this option if you want to provide a PDB administrator password and unlock the PDB administrator account.

        5. Take a backup of the PDB immediately after cloning it: This option is unavailable, as shown in the screenshot. A PDB backup cannot be created if a backup of the container database has not been created previously.

      4. Expand the Advanced options section to manage Tags for the cloned PDB. This is an optional step.

        This screenshot shows how to clone a Base Database.

      5. Select Clone to initiate the PDB cloning operation.

  • You can clone a DB system using the OCI Console.

  • You can clone a DB system using the OCI Console.

  • There is currently no content for this page. Oracle AI Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle AI Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.