1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
Hi,
The first thing that you should do is test the connectivity between your on-prem pg server and the replication task on AWS.
So, connect to pg server via ssh and from there try to telnet to the ip addr + port of the replication server / task based on our configuration. See https://netbeez.net/blog/telnet-to-test-connectivity-to-tcp/ for all details.
If tcp session establishes, you may have to look elsewhere, but most of time it is a connectivity issue due to sec group(s) or routing tables in the vpc of your replication server. It can also be an on-prem issue: firewall tcp port to reach replication server on AWS not opened is a very frequent issue.
This older trio of posts will also propose you other aspects to inspect:
- https://aws.amazon.com/blogs/database/debugging-your-aws-dms-migrations-what-to-do-when-things-go-wrong-part-1/
- https://aws.amazon.com/blogs/database/debugging-your-aws-dms-migrations-what-to-do-when-things-go-wrong-part-2/
- https://aws.amazon.com/blogs/database/debugging-your-aws-dms-migrations-what-to-do-when-things-go-wrong-part-3/
Best,
Didier
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 2년 전