1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
Sorry to hear that you are facing issue with the same. The maximum number of attempts made to restart a task when an environmental error occurs. After the system attempts to restart the task the designated number of times, the task is stopped and manual intervention is required. The default value is -1, which instructs AWS DMS to attempt to restart the task indefinitely. Set this value to 0 to never attempt to restart a task. If a fatal error occurs, AWS DMS stops attempting to restart the task after six attempts.
Refer this link for Trouble-shooting steps= https://aws.amazon.com/blogs/database/debugging-your-aws-dms-migrations-what-to-do-when-things-go-wrong-part-1/
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
The problem isn't the error per se, it's that I need to find out why the DMS migration task that I created isn't initially copying the instance from my EC2 Postgres source to my AWS RDS instance endpoint and then beginning and maintaining replication. How do I get my database that I'm trying to replicate on RDS copied over?