Create a source connection profile

The connection details you need to provide can differ depending on what source connectivity you use. This page describes how to create source connection profiles for each available connectivity method:

Before you begin

Before you create a source connection profile, make sure you do the following:

  1. Consider in which region you want to create the source connection profile.

    Database Migration Service is a fully-regional product, meaning all entities related to your migration (source and destination connection profiles, migration jobs, destination databases, conversion workspaces) must be saved in a single region.

  2. Configure your source database and create a dedicated migration user account.

  3. Choose and configure the source connectivity method.

For public IP allowlist connectivity

To create a source connection profile that uses the public IP allowlist connectivity method, follow these steps:

  1. Make sure you configure your source database server to accept connections from Database Migration Service public IP addresses for the region where you create the migration job. For more information, see Public IP allowlist overview.
  2. In the Google Cloud console, go to the Connection profiles page.

    Go to Connection profiles

  3. Click Create profile.
  4. On the Create a connection profile page, from the Profile role list, select Source.
  5. From the Database engine list, select Oracle.
  6. In the Specify connection profile details section, provide the connection profile name, id, and region.
  7. In the Define connection details section, enter the following details:
    1. Your source database public IP and port number, the name of the database you want to migrate, and login details for the dedicated migration user account (name and password).
    2. In the Service name field, enter the service that ensures that the source Oracle database is protected and monitored.
      • For Oracle databases, the database service is typically ORCL.
      • For pluggable databases, SID is the pluggable database name.
  8. In the Secure your connection section, choose the encryption type you want to use for the source database connection.

    You can use your own SSL/TLS certificates for additional network security. For more information, see Encrypt connections with certificates.

  9. In the Define connectivity method section, select Public IP allowlist.
  10. Optional: In the Test connection profile section, click Run test.

    Database Migration Service performs a quick check to verify that the connection details you supplied are sufficient to reach your source database.

  11. Click Create.

    The Connection profiles page appears, and the newly created connection profile is displayed.

For forward-SSH tunnel connectivity

To create a source connection profile that uses the forward-SSH tunnel connectivity method, follow these steps:

  1. Make sure you set up the forward-SSH tunnel server and adjust all firewall rules in your network. For more information, see Forward-SSH tunnel connectivity overview.
  2. In the Google Cloud console, go to the Connection profiles page.

    Go to Connection profiles

  3. Click Create profile.
  4. On the Create a connection profile page, from the Profile role list, select Source.
  5. From the Database engine list, select Oracle.
  6. In the Specify connection profile details section, provide the connection profile name, id, and region.
  7. In the Define connection details section, enter the following details:
    1. Your source database IP and port number, the name of the database you want to migrate, and login details for the dedicated migration user account (name and password).

      The IP address should be an address that is reachable from the forward-SSH tunnel.

    2. In the Service name field, enter the service that ensures that the source Oracle database is protected and monitored.
      • For Oracle databases, the database service is typically ORCL.
      • For pluggable databases, SID is the pluggable database name.
  8. In the Secure your connection section, choose the encryption type you want to use for the source database connection.

    You can use your own SSL/TLS certificates for additional network security. For more information, see Encrypt connections with certificates.

  9. In the Define connectivity method section, do the following:
    1. From the Connectivity method drop-down menu, select Forward-SSH tunnel.
    2. In the next sections, enter the connection details for the SSH server: IP address or hostname, port number, and login.
    3. From the Authentication method drop-down menu, select how you want Database Migration Service to authenticate with your SSH server.

      You can use a password, or a unique private key. If you decide to use a private key, you can upload the file directly to Database Migration Service, or paste the key in text form in the text box.

  10. Click Save.

    The connectivity details panel closes.

  11. Optional: In the Test connection profile section, click Run test.

    Database Migration Service performs a quick check to verify that the connection details you supplied are sufficient to reach your source database.

  12. Click Create at the bottom of the page.

    The Connection profiles page appears, and the newly created connection profile is displayed.

For private connectivity with Virtual Private Cloud peering

To create a source connection profile that uses the private IP connectivity with Virtual Private Cloud peering, follow these steps:

  1. Make sure you configure your network for private IP connectivity. For more information, see Source private connectivity overview.
  2. In the Google Cloud console, go to the Connection profiles page.

    Go to Connection profiles

  3. Click Create profile.
  4. On the Create a connection profile page, from the Profile role list, select Source.
  5. From the Database engine list, select your Oracle source.
  6. In the Specify connection profile details section, provide the connection profile name, id, and region.
  7. In the Define connection details section, enter the following details:
    1. Your source database IP and port number, the name of the database you want to migrate, and login details for the dedicated migration user account (name and password).

      The IP address should be a private IP address that is reachable from the Virtual Private Cloud network that you use with the Database Migration Service private connectivity configuration.

    2. In the Service name field, enter the service that ensures that the source Oracle database is protected and monitored.
      • For Oracle databases, the database service is typically ORCL.
      • For pluggable databases, SID is the pluggable database name.
  8. In the Secure your connection section, choose the encryption type you want to use for the source database connection.

    You can use your own SSL/TLS certificates for additional network security. For more information, see Encrypt connections with certificates.

  9. In the Define connectivity method section, do the following:
    1. From the Connectivity method drop-down menu, select Private connectivity (VPC peering).
    2. From the Private connectivity configuration drop-down menu, select the name of the private connectivity configuration you created to peer with your Virtual Private Cloud.
  10. Click Save.

    The connectivity details panel closes.

  11. Optional: In the Test connection profile section, click Run test.

    Database Migration Service performs a quick check to verify that the connection details you supplied are sufficient to reach your source database.

  12. Click Create at the bottom of the page.

    The Connection profiles page appears, and the newly created connection profile is displayed.

What's next