Skip to content

Commit 1e8f8fc

Browse files
authored
Merge pull request #235829 from hsinghjkaur/test
[PostgreSQL] - Add new article for error messages
2 parents e3affa5 + 204d7dc commit 1e8f8fc

File tree

4 files changed

+92
-0
lines changed

4 files changed

+92
-0
lines changed

articles/postgresql/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@
2222
href: migrate/how-to-migrate-single-to-flexible-portal.md
2323
- name: Single to Flexible server migration tool - Using CLI
2424
href: migrate/how-to-migrate-single-to-flexible-cli.md
25+
- name: Common errors
26+
href: migrate/common-errors-and-special-scenarios-fms.md
2527
- name: Migrate data with pg_dump and pg_restore
2628
href: single-server/how-to-migrate-using-dump-and-restore.md
2729
displayName: pg_dump, pg_restore
Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
---
2+
title: "Common errors and special scenarios for PostgreSQL Single Server to Flexible using the FMS migration tool"
3+
description: Common errors and special scenarios for PostgreSQL Single Server to Flexible using the FMS migration tool.
4+
author: harmeet-singh
5+
ms.author: hasingh
6+
ms.reviewer: maghan
7+
ms.date: 05/01/2023
8+
ms.service: postgresql
9+
ms.topic: conceptual
10+
---
11+
12+
# Common errors and special scenarios for PostgreSQL Single Server to Flexible using the FMS migration tool.
13+
14+
This articles explains common errors and special scenarios for PostgreSQL Single Server to Flexible using the FMS migration tool.
15+
16+
## Custom DNS
17+
18+
- Error message
19+
Connecting to the Source DB server failed. ErrorMessage: Validation of one or more databases failed to run `select 1;` with exception 28000: The public network access on this server is disabled. Use the Private Endpoint inside your virtual network to connect to this server.
20+
21+
- Root Cause
22+
23+
The VNet is, by default, not enabled for outbound connections when we use CustomDNS. Migration makes outbound calls, which cause the failure.
24+
25+
- Mitigation/Resolution
26+
27+
While Microsoft is working on a fix as part of the product, customers can use one of the following mitigations to unblock:
28+
Temporarily enable the public network access on the server
29+
OR
30+
Reach out to Microsoft, and we enable the server for outbound connections for the selected DNS addresses.
31+
32+
## Allowlist extensions
33+
34+
- Symptom
35+
Error message appears as "Extensions plpgsql, pg_stat_statements, pg_buffercache aren't allowlisted on target server."
36+
37+
:::image type="content" source="media/common-errors-and-special-scenarios-fms/allow-list-extensions-common-errors-postgresql.png" alt-text="Screenshot of scenario for allow listing extensions." lightbox="media/common-errors-and-special-scenarios-fms/allow-list-extensions-common-errors-postgresql.png":::
38+
39+
- Root Cause
40+
41+
The flexible server doesn't have extensions allow-listed by default and has to be manually allow-listed before migration/use.
42+
43+
- Mitigation/Resolution
44+
45+
Customers need to go to the server parameters of the flexible server and allowlist all the extensions they intend to use. At least the ones mentioned in the error message should be allowed to be listed.
46+
47+
## No pg_hba.conf entry for host
48+
49+
- Error Message
50+
Connecting to the Source DB server failed. ErrorMessage: Validation of one or more databases failed. Failed to run `select 1;` with exception 28000: no pg_hba.conf entry for host "xx.xx.xx.xx", the user "username," database "postgres," SSL on Parameter name: SourceDBServerResourceId.
51+
52+
- Root Cause
53+
54+
The IP address isn't added to the firewall rules.
55+
56+
- Mitigation/Resolution
57+
58+
Add IP addresses in the Firewall rules in the Networking tab of the Flex Server.
59+
60+
:::image type="content" source="media/common-errors-and-special-scenarios-fms/ip-addresses-common-errors-postgresql.png" alt-text="Screenshot of ip addresses." lightbox="media/common-errors-and-special-scenarios-fms/ip-addresses-common-errors-postgresql.png":::
61+
62+
## Migration to Flex server with Burstable SKU isn't Supported
63+
64+
- Error Message
65+
Migration to Flex server with Burstable SKU isn't Supported.
66+
67+
- Root Cause
68+
69+
By Design.
70+
71+
- Mitigation/Resolution
72+
73+
Change the flexible server from Burstable to General Purpose or Memory Optimized by going to compute + storage tab on the left menu.
74+
75+
## Cross-region migration isn't supported
76+
77+
- Error Message
78+
Cross-region migration isn't supported.
79+
80+
- Root Cause
81+
82+
By Design.
83+
84+
- Mitigation/Resolution
85+
86+
This feature is coming soon; in the meantime, only migrations within servers of the same region are supported.
87+
88+
## Next steps
89+
90+
- [Migration tool](concepts-single-to-flexible.md)
Loading
Loading

0 commit comments

Comments
 (0)