[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-18 (世界標準時間)。"],[],[],null,["# Manage conversion workspaces\n\nThis page describes how to manage multiple conversion workspaces in your projects.\nFrom the list of conversion workspaces, you can:\n\n- Select a specific conversion workspace to access the conversion editor,\n view and modify workspace details, apply generated schema and code to your\n destination database, and create a migration job.\n\n- Use the more_vert**More**\n menu to delete a workspace.\n\nView conversion workspace details\n---------------------------------\n\nTo view conversion workspace details, use the **Conversion workspaces** page in the Google Cloud console or Google Cloud CLI. \n\n### Console\n\n1. In the Google Cloud console, go to **Conversion workspaces**.\n\n[Go to Conversion workspaces](https://console.cloud.google.com/dbmigration/conversion-workspaces)\n\n1. From the list of available workspaces, select the one you want to work with.\n\n Conversion workspace editor page appears.\n2. Select **Edit configuration** \\\u003e **View details**.\n\nThe **Conversion workspace details** panel opens.\n\n### gcloud\n\n1. List all workspaces available in a particular region to retrieve their identifiers:\n\n gcloud database-migration conversion-workspaces list \\\n --region=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\n Replace:\n - `REGION` with the name of the region where the conversion workspace is located.\n\n Example: \n\n gcloud database-migration conversion-workspaces list \\\n --region=us-central1\n\n The list of available workspaces and their identifiers is printed to standard output.\n2. Retrieve details for a specific workspace:\n\n gcloud database-migration conversion-workspaces describe \u003cvar translate=\"no\"\u003eCONVERSION_WORKSPACE\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\n Replace:\n - `CONVERSION_WORKSPACE` with the identifier or the fully qualified name\n of the conversion workspace\n\n - `REGION` with the name of the region where\n the conversion workspace is located.\n\n Example: \n\n gcloud database-migration conversion-workspaces describe my-conversion-workspace-id \\\n --region=us-central1\n\nModify conversion workspace settings\n------------------------------------\n\nInformation that you can modify for a conversion workspace includes the display\nname, source connection profile, add or remove custom conversion configuration files.\n\n1. Go to the **Conversion workspaces** page in the Google Cloud console:\n\n [Go to Conversion workspaces](https://console.cloud.google.com/dbmigration/conversion-workspaces)\n2. Click the display name of the conversion workspace that you want to modify.\n\n The conversion workspace editor opens.\n3. Select **Edit configuration** \\\u003e **View details**.\n\n The **Conversion workspace details** panel opens.\n4. To modify the workspace display name:\n\n 1. In the **Conversion workspace name** row, click the edit**edit** icon.\n 2. In the **Conversion workspace name** field, enter the new display name for the conversion workspace.\n 3. Click **Save**.\n5. To modify the source connection profile:\n\n 1. In the **Source connection profile** row, click the link to the connection profile associated with the workspace.\n 2. On the connection profile page, adjust any details as required. For more information, see [Manage connection profiles](/database-migration/docs/oracle-to-alloydb/manage_connection-profiles). A new version of the conversion workspace is created and the updated version ID also appears on the overview page. This version can be used with a migration job.\n6. You can also modify what custom conversion mapping files are used in your\n workspace. For more information, see\n [Use custom conversion mappings](/database-migration/docs/oracle-to-alloydb/work-with-conversion-workspaces#use-custom-mappings).\n\nDelete a conversion workspace\n-----------------------------\n\nYou can delete a conversion workspace only if it's not used by active migration jobs.\n\nTo delete a conversion workspace that's linked to active migration jobs, first, delete all active migration jobs that are linked to the conversion workspace. Then, delete the conversion workspace.\n\n1. In the Google Cloud console, go to **Conversion workspaces**.\n\n [Go to Conversion workspaces](https://console.cloud.google.com/dbmigration/conversion-workspaces)\n2. Next to the conversion workspace you want to delete,\n click more_vert**More** \\\u003e **Delete**.\n\n3. In the dialog confirmation box, click **Delete**.\n\nReview all conversion workspaces\n--------------------------------\n\nYou can review all conversion workspaces from the\n[](https://console.cloud.google.com/dbmigration/conversion-workspaces) page.\nThe list displays a default set of high-level information for each conversion\nworkspace, including:\n\n- The conversion workspace **display name** and **ID**.\n- The **version ID** of the most-recent version of the conversion workspace that's saved. By having multiple versions of a conversion workspace, you can compare objects in each workspace and identify differences between the workspaces. Versioning can also be used for tracking purposes.\n- The **conversion state** that represents whether this conversion workspace was used to pull objects from the source and convert them.\n- **Activity** indicates if the conversion workspace is in use by one or more active migration jobs, where an active migration job is any migration job that's not in `COMPLETED` status. The number of jobs next to the status indicates the total number of jobs (both active and inactive) referencing the conversion workspace.\n- The **source** and **destination** database engines (database types) for which the conversion workspace is configured.\n- When the conversion workspace was **created**."]]