Create a conversion workspace

This page shows you how to set up a conversion workspace. Before creating a conversion workspace, make sure that you do the following:

• Create a connection profile for your source Oracle database. For more information, see Create an Oracle connection profile.
• Optional: If you want to use the legacy conversion workspace, prepare your Ora2Pg configuration file. See Configure your Ora2Pg.

Conversion workspaces help you convert the schema and objects from your source database into a format that is compatible with your destination database. This conversion lets Database Migration Service migrate your data between the source and destination databases.

Conversion workspaces are available for review and modification on the Conversion workspaces page, and can be reused across migration jobs.

To set up a conversion workspace, follow these steps:

1. Define settings for the conversion workspace.
2. Connect to the source database and pull the source objects into Database Migration Service.

3. Perform source conversion:

   • In conversion workspaces with the built-in editor: By using the integrated conversion workspace editor - a live editor space where you can convert, view, and modify the conversion results.

   • In legacy workspaces: By using Ora2Pg to convert the schema

4. Apply converted schema to your destination database: Database Migration Service uses the converted SQL to create all the required entities in your destination database. This helps ensure migrated data can be correctly loaded to the database.

Database Migration Service comes equipped with a wizard to help you create and configure conversion workspaces. Information on how to populate each panel in the wizard is provided in the various sections of this page.

Define settings for the conversion workspace

1. Go to the Conversion workspaces page in the Google Cloud Console.

   Go to Conversion workspaces

2. Click Set up workspace, and in the dialog window select one of the following:

   • Click Set up new workspace if you want to use the new conversion workspace with the built-in conversion editor.

     OR

   • Click Set up legacy workspace if you want to use the legacy workspace with the Ora2Pg conversion tool.

   Note: For more details on available conversion workspace solutions, see About conversion workspaces.

3. Use the following table to populate the fields of the Create a conversion workspace panel of the Create conversion workspace page:

   Field	Description
   Conversion workspace name	Enter the display name of the conversion workspace. This is used to identify your workspace when you create a migration job, or when you want to locate it in the list of your conversion workspaces.
   Conversion workspace ID	Database Migration Service populates this field automatically based on the conversion workspace name that you enter. You can keep the ID that's auto-generated or change it.
   Region	Select the region where the conversion workspace is stored. Connection profiles and migration jobs can use only conversion workspaces that are stored in the same region. Region selection doesn't impact whether your conversion workspace can connect to the source, but can impact connectivity to the destination and availability if the region experiences downtime. This choice is permanent and can't be changed.
   Source database engine	Oracle is selected for you automatically.
   Destination database engine	Select your destination database engine.

4. Review the prerequisites displayed in the Create a conversion workspace section. These are generated automatically by Database Migration Service to verify what you need to prepare for this migration path. The prerequisites include information how to:

   • Create a connection profile to the source Oracle database

   • Configure your source Oracle database so that the conversion workspace can retrieve data from it

   It's best to complete these prerequisites at this step, but you can complete them at any time before you finish creating the conversion workspace.

5. Click Create workspace and continue.

Connect to the source and convert objects

The path to converting source schema objects depends on which conversion workspace you use.

Workspaces with the built-in editor

1. Select your source connection profile from the Source connection profile drop-down list.

2. Click Run test to verify that Database Migration Service can communicate with the source.

   If a test fails, then it indicates which part of the process had an issue. Necessary changes can be made and then re-tested.

   Navigate to the part of the flow in question to correct the issue, and then re-test.

   The conversion workspace can be created even if tests for the source connection profile fail, but you should fix any issues associated with the connection profile to be able to perform schema conversion.

3. Click Pull schema and continue.

   Database Migration Service is now connecting to your source database to download schema and code information. This operation can take a couple of minutes, depending on factors such as network connectivity or database size.

   Once Database Migration Service finishes pulling source information, the interface automatically switches to the Select and convert objects section.

4. In the Select and convert objects, use the source schema to select all entities you want Database Migration Service to convert into schema and code compatible with your destination database SQL engine.

   This selection isn't permanent. You can later add or remove more objects directly inside the conversion editor. This lets engage with the conversion process in a flexible manner, and work only on the objects that you want to focus on.

   Note: Use the Filter objects button to reduce the number of displayed objects. For more information, see Filter objects in the source schema view.

At this point, you can perform one of the two actions:

• Click Save and continue.

  Database Migration Service creates your conversion workspace. You are able to view the editor space and edit the workspace settings, but the schema and code aren't yet converted. You need to later perform the conversion to prepare the schema and code for your destination database before you run migration jobs.

  Continue to Convert sources.

• Click Convert and continue.

  Database Migration Service creates your conversion workspace and performs the initial schema and code conversion. You can now preview the auto-generated SQL in the conversion workspace editor.

  Continue to Review conversion issues.

Legacy workspaces

1. Select your source connection profile from the Source connection profile drop-down list.

2. Optional. Click View details to see additional information about the connection profile.

3. Click Run Test to verify that Database Migration Service can communicate with the source.

   If a test fails, then it indicates which part of the process had an issue. Necessary changes can be made and then re-tested.

   Navigate to the part of the flow in question to correct the issue, and then retest.

   The conversion workspace can be created even if tests for the source connection profile fail. However, you should fix any issues associated with the connection profile before you create the conversion workspace.

4. Click Browse to select and upload an Ora2Pg configuration file that you configured.

5. Optional. To upload additional Ora2Pg configuration files, click Add file.

   Make sure that you upload all Ora2Pg configuration files you require in this conversion workspace because Database Migration Service doesn't keep previous configuration files.

6. Click Pull schema and convert to validate that Database Migration Service can migrate your data with the supplied Ora2Pg configurations. This includes:

   • Connecting to the source database

   • Retrieving schema and code from the source database

   • Creating table mappings between the source and destination databases

   • Converting the source database schema and code to dialects compatible with that the destination database dialect

   If a test fails, then:

   1. Fix all Ora2Pg configuration files.

   2. Reapply the updated DDLs in the destination Cloud SQL for PostgreSQL instance.

   3. Click Pull schema and convert again.

   For more information about reasons why a test may fail and how to troubleshoot any issues associated with a test failing, see Diagnose issues.
   The conversion workspace can be created even if a test fails. However, we recommend fixing any issues before you create the conversion workspace.

7. Click Save and close.

8. In the dialog box, click Save and close.