Creating an Oracle Exadata connection

Create an Oracle Exadata connection by performing the following steps:

1. Log in into the OCI Console with your user credentials and the necessary policies to be able to create database connections.
2. Open the navigation menu. Under Database Migrations click Database Connections.
3. Click Create Connection.
4. On the General information step, in the Name field, enter a display name for the database connection resource.

   This is not the actual database name, but a name that will appear in a list of databases connections on completion of this procedure. Note that the database connection resources for all source databases (CDB and PDB) and target databases will appear the same list.

5. Add Description for the database connection resource.
6. In Compartment select the compartment in which the Database Connection resource will be created.
7. In Type, select a connection type. Select the connection type as Oracle Exadata.
8. In Vault in Compartment select the security vault.

   Database Migration uses the OCI Vault to store user secrets such as passwords, wallets, and keys, and encrypts them with the user-supplied encryption key.

   You can select a vault in a different compartment by clicking Change Compartment.

9. In Encryption Key in Compartment select the keystore that you configured in the vault.

   Only AES algorithm type keys are supported.

10. The Advanced Options section allows you to optionally create tags.
11. In the Connection details step, enter the database details for the Oracle Exadata. Select one of the following options:
    • Select database and provide the following information:
      • VM Cluster in Compartment: Select a VM cluster.

      • Database: Select the database.

        Pluggable Database: (Optional):

        Select the Pluggable Database.

      • Enter the database administrator credentials in Initial load database username and Initial load database password.

    • Enter the database information and provide the following information:
      • Database connection string: Provide the full connect string with host, port, and service name, in the following format:

        host:port/db-service-name

        If a private endpoint is specified in the connection, the hostentry should be a valid IP address.

      • Enter the database administrator credentials in Initial load database username and Initial load database password.

12. Select Use different credentials for replication to enter the credentials for replication. Select this option if you want to use a separate database user for performing replication for your online migrations. The following options are available
    • Replication database username
    • Replication database password
13. Optionally, upload the Database wallet drag and drop or select the wallet.zip for this database.

    Note:

    The wallet.zip must contain the cwallet.sso and tnsnames.ora files.

14. In Network Connectivity details, Create private endpoint to access this database indicates whether the database is publicly accessible or if you want to create a private endpoint.
    In Subnet in Compartment, select the subnet to which a private endpoint is created from the Oracle Cloud Infrastructure Database Migration service tenancy. This creates a network route for the Oracle Cloud Infrastructure Database Migration deployment to connect to the database within your customer tenancy. Select the subnet containing the appropriate Virtual Cloud Network (VCN).Click Change Compartment to select a subnet in a different compartment.
15. (Optional) Under Advanced Options, enter the details for SSH settings if you prefer a Secure Shell (SSH) connection. Provide the SSH information for your database hosts if you wish to provide SSH access to the service to perform the migrations. Provide the SSH related information as follows:

    Note:

    Ensure that the private SSH key file is an RSA key in PEM format. See Required Keys and OCIDs for more information.

    • SSH database server hostname: Enter the IP address of the database host. This will be used by the service to connect to your host through/via SSH to perform the migration. Select the valid private key file used for database host access.

      Note:

      Enter a valid SSH username that will be used by the service to create a ssh session to the database host. This user should have the sudo privilege to perform the necessary operations.
    • SSH private key:

      Drop or select the private key file used to access the database server host.

    • SSH username: Enter an OS user name for the database host. This user must be a privileged user allowed to run sudo.
    • SSH sudo location: Enter the sudo binary location on the database host.
16. Click Create.

Note:

After you click Create, the database connection name appears in the Connection list while the creating connection operation runs. The creating connection operation can take a few minutes.

You can monitor the operation status in the State column. When the state is Active, the database connection creation is complete and successful.

When the resource creation is complete and successful, check the Security Vault service to verify that the SSH private key file was uploaded and enabled in the vault you configured.