Migration name must be available error while migrating Postgre SQL to flexible server

Hi Jha, RahulKumar

Greeting!

As I understand that you are facing an issue while providing a unique migration name during the migration process.

Here are a few steps and tips that might help resolve this:

Double-Check Naming Rules: Ensure the migration name follows all the rules:

• Only alphanumeric characters and hyphens.
• Cannot start with a hyphen.
• Must be unique for the target server.

Clear Cache and Cookies: Sometimes, browser cache or cookies can cause issues. Try clearing them or using a different browser.

Check for Existing Migrations: Verify that no other migrations to the same target server have the same name. Even if a migration was deleted, it might still be reserved for a short period.

Use a Unique Identifier: Add a unique identifier to the name, such as a timestamp or a specific project code. For example, migration20241126 or project123-migration.

Region-Specific Availability: Ensure that the name you’re trying to use is not restricted by the region you selected when setting up the migration. Some names might be globally reserved or restricted in certain regions.

Note: first Try Using Azure CLI: If you are using the Azure Portal and still encountering issues, try creating the migration through the Azure CLI. This approach can sometimes provide more detailed error messages or guidance that might help resolve the problem.

Hope this helps. Do let us know if you any further queries. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thanks for replying to this thread. I checked all the suggestions you shared and luckily, I tried all before I started this thread. The target server is new, and we never run any migration. Don't know why it is throwing error. This is the very step and without this we are not able to move ahead. I did not try Azure CLI yet but as you suggest, I will that through that as well.

One question I wanted to ask, please advise if this could be permission related error as well which at present, I don't think it should be.

Hi Jha, RahulKumar

Thank you for reaching out with your concerns.

Please try executing this in Azure CLI. I am sure it should work, as we faced similar issues before and resolved them using CLI scripts.

Hope this helps. Do let us know if you any further queries. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Hi Jha, RahulKumar

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

I am trying with Azure CLI and will surely share my experience with CLI.