Azure Database Migration Service

Khristian Dave Poleracio 131

Hi!

Encountered this error when I'm migrating it from source to flexible server.
See below picture.
I have checked that the parameters listed below on the sqlmode is both check on single and flexible server. Also the time_zone and netwrite are set. Since we are in +8:00. We edited it on +08:00.

Thank you!
User's image

ShaktiSingh-MSFT 16,236 Reputation points

2023-01-27T08:59:44.66+00:00
Hi @Khristian Dave Poleracio ,

Thanks for posting this question in Microsoft Q&A forum and we are sorry about the error you are facing.

As I understand from the question you are using Azure Database Migration service for migration of Azure PostgreSQL single server to Flexible. Please correct me if I my understanding is wrong.

As the error message suggests, could you please try to restart server and check if you are able to proceed.

Let us know this helps.

Additionally, please refer to the below Limitations of DMS:

You can migrate up to 1 TB of data from PostgreSQL to Azure Database for PostgreSQL, using a single DMS service.

Limitation: If there's no primary key on tables, changes might not be synced to the target database.

Workaround: Temporarily set a primary key for the table for migration to continue. Remove the primary key after data migration is finished.

The database name can't include a semicolon (;).

A captured table must have a primary key. If a table doesn't have a primary key, the result of DELETE and UPDATE record operations will be unpredictable.

Updating a primary key segment is ignored. Applying such an update will be identified by the target as an update that didn't update any rows. The result is a record written to the exceptions table.

Migration of multiple tables with the same name but a different case might cause unpredictable behavior and isn't supported. An example is the use of table1, TABLE1, and Table1.

Change processing of [CREATE | ALTER | DROP | TRUNCATE] table DDLs isn't supported.

In Database Migration Service, a single migration activity can only accommodate up to four databases.

Migration of the pg_largeobject table isn't supported.

Please check and let us know your findings. Thanks
ShaktiSingh-MSFT 16,236 Reputation points

2023-01-30T05:10:47.6833333+00:00

Hi @Khristian Dave Poleracio ,

We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.

Share via

Azure Database Migration Service

Your answer