Error migrating from single to flex postgres

João Dias 0

After 16h in online migration the process failed with the following error:

DB004: Failed to fetch the current migrations status. Please reference MigrationId 3691c83d-e8ba-4fca-a612-88fd534ed620, when contacting Microsoft customer support. Parameter name: SourceDBServerResourceId

Mahesh Kurva 2,835 Reputation points Microsoft Vendor

2025-02-13T18:38:07.12+00:00
Hi @João Dias,

Welcome to Microsoft Q&A forum.

As I understand it, you're facing an issue during the online migration from a single to a flex PostgreSQL setup.

To better assist you, could you please confirm the version you're trying to migrate to?

Additionally, here are a few troubleshooting steps you can try to resolve the issue:

Check that your source and target servers can communicate without network issues and ensure firewalls and security settings are correct.

Make sure the server settings, including SSL, are properly configured. SSL errors can sometimes cause migration failures.

Verify that the account used for migration has the necessary permissions on both databases.

Look at the migration logs for more error details that can help identify the problem.

If you're using the Azure portal, try using the Azure CLI instead.

For more information, please refer the document:

https://learn.microsoft.com/en-us/azure/postgresql/migrate/migration-service/tutorial-migration-service-single-to-flexible?tabs=cli%2Conline

Here is a similar thread that might be helpful to you.

https://learn.microsoft.com/en-us/answers/questions/2128507/issue-migrating-azure-postgress-single-to-flexible

I hope this information helps. Please do let us know if you have any further queries.
Mahesh Kurva 2,835 Reputation points Microsoft Vendor

2025-02-14T20:45:25.0833333+00:00

Hi @João Dias,

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.
João Dias 0 Reputation points

2025-02-15T08:15:30.7433333+00:00

Try another time , but this time with a diferent error:

One or more errors occurred while migrating 'postgres' : Migration failed due to the Source server closing the connection unexpectedly. Please check the server's configuration or check if your application closes long running connections and retry. If the error persists, contact Microsoft support. Migration failed due to the Source server closing the connection unexpectedly. Please check the server's configuration or check if your application closes long running connections and retry. If the error persists, contact Microsoft support. Logs from the migration: 2025-02-14 22:44:44.544 31 ERROR pgsql.c:4562 Failed to get async query results: SSL SYSCALL error: EOF detected 2025-02-14 22:44:44.544 31 ERROR pgsql.c:2428 [SOURCE 0] connection pointer is NULL 2025-02-14 22:44:44.544 31 ERROR pgsql.c:2441 [SOURCE 0] SQL query: select c.oid, format('%I', n.nspname) as nspname, format('%I', c.relname) as relname, c.relkind as relkind, pg_am.amname, c.relpages, c.reltuples::bigint, c.relpages * current_setting('block_size')::bigint * 20 AS bytesestimate, pg_size_pretty(c.relpages * curren... (rest of the failure message is truncated.)
João Dias 0 Reputation points

2025-02-22T22:46:39.1866667+00:00
i have updated the parameters

tcp_keepalives_idle=10

tcp_keepalives_interval=10

tcp_keepalives_count=60

As refered , but the issues continues , after 21 hours the migration failed with the following error:

DB004: Failed to fetch the current migrations status. Please reference MigrationId aaa2ed84-7ffd-480d-9c92-9942c37beb6d, when contacting Microsoft customer support. Parameter name: SourceDBServerResourceId

1 answer

PratikLad 80 Reputation points Microsoft Vendor

2025-02-18T08:35:09.1+00:00
Hi @João Dias,

DB004: Failed to fetch the current migrations status.

The above error message shows the issue with permissions, connectivity problem.

To resolve the permission issue, check the user you are using has proper permission in both source and target databases.

In perspective of connectivity issues please check the network configuration and firewall if it is restricting your databases, so that they can communicate with each other without any network issue.

Migration failed due to the Source server closing the connection unexpectedly.

The main cause of this kind of error is connection timeout. A connection timeout occurs when either the server or the client expects to receive data within a certain duration, but no data is transferred or received, leading the connection to terminate. This issue can be caused by a variety of factors, such as network congestion, incorrect network configurations, or overly strict timeout settings.

To resolve this issue connection timeout issues, adjust the below TCP parameters on both the source and target servers:

tcp_keepalives_idle=10

tcp_keepalives_interval=10

tcp_keepalives_count=60

Please go through these documentations that might help you:

https://learn.microsoft.com/en-us/azure/postgresql/migrate/migration-service/troubleshoot-error-codes

https://learn.microsoft.com/en-us/azure/postgresql/migrate/migration-service/concepts-known-issues-migration-service
Please sign in to rate this answer.
PratikLad 80 Reputation points Microsoft Vendor

2025-02-19T03:48:33.94+00:00

Hi @João Dias,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.

PratikLad 80 Reputation points Microsoft Vendor

2025-02-19T04:05:12.06+00:00

Hi @João Dias,

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.

PratikLad 80 Reputation points Microsoft Vendor

2025-02-19T14:33:48.61+00:00

Hi @João Dias,

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

João Dias 0 Reputation points

2025-02-22T22:47:35.37+00:00

After updating the parameters

tcp_keepalives_idle=10

tcp_keepalives_interval=10

tcp_keepalives_count=60

the issues continues , after 21 hours the migration failed with the following error:

DB004: Failed to fetch the current migrations status. Please reference MigrationId aaa2ed84-7ffd-480d-9c92-9942c37beb6d, when contacting Microsoft customer support. Parameter name: SourceDBServerResourceId

PratikLad 80 Reputation points Microsoft Vendor

2025-02-25T11:16:19.64+00:00

Can we please work on this thread offline? Please send us an email on azcommunity [at] microsoft [dot] com with Sub - "ATTN: PratikLad" and following details in the email body:

Link to this thread/post

Server name and id

Location

Server type

Subscription ID

Tenant ID

Description of the issue
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error migrating from single to flex postgres

1 answer

Your answer