AWS DMS Migration Project - Schema Conversion Stuck on LAUNCHING (Web Based AWS Console)
Hey all!
I'm having trouble with an AWS DMS migration project's schema conversion stuck on LAUNCHING status.
In the DMS migration project, I have set up & configured all the resources needed, then I go to the "Schema conversion" tab to start the schema conversion tool (not to be confused with the SCT, this is the AWS console web based schema conversion part of the migration project).
I launch it, however, now it is stuck on the status of "Launching". It's been like this for hours. I've created other new migration projects with the same settings, and it is able to launch successfully. There's no option to stop it or close the schema conversion. Deleting the entire migration isn't allowed either because the "migration project is in use." Meanwhile, now I can't modify any of the other resources associated with the project because something like "while the migration project is in use, you cannot modify this resource."
I've tried using the CLI as well to see if there's any additional parameters/options, but doesn't seem like it.
- Tags
- AWS Schema Conversion Tool (AWS SCT)AWS Database Migration ServiceGeneral Database MigrationsDatabase
- Language
- English
asked 2 years ago1.2K views
- Newest
- Most votes
- Most comments
After a couple days, I went back to it and I was able to finally delete it...
answered 2 years ago
Check AWS Service Health: Ensure there are no ongoing service disruptions in the AWS DMS service or related services in your AWS region.
CloudWatch Logs: Check AWS CloudWatch logs for any errors or warnings related to the DMS project to gain more insight into the problem.
Restart the Migration Project via AWS CLI:
Use aws dms list-replication-tasks to find the task ID. Use aws dms stop-replication-task to stop the task. Terminate Associated EC2 Instances:
Check your EC2 dashboard for any instances associated with your DMS project and try to stop them. Contact AWS Support:
If the issue persists, contact AWS Support with details of your project, the steps you've taken, and any logs you've checked. Wait and Retry:
Sometimes, the process might take longer due to backend issues. Consider waiting for some more time if you haven't already done so. If these steps don’t resolve the issue, reaching out to AWS Support is the next best step.
answered 2 years ago
Relevant content
asked 4 months ago
asked 2 years ago
asked 3 years ago
- AWS OFFICIALUpdated 10 months ago
Hey Basel! Appreciate your comment.
list-replication-tasksis about the replication task. In DMS, a migration project is separate from a replication task.