AWS DMS task fails

Question

Having some problems using DMS - misconfigure the task selection rule (i guess)

testing it between 2 small rds postgres instances created source and target endpoints created a replication instances
( tested connections successfuly )

The task i run keeps failing : 
" Last Error No tables were found at task initialization. 
Either the selected table(s) or schemas(s) no longer exist or no match was found for the table selection pattern(s)."

Schemas : pg_catalog,information_schema,public

I only want to replicate a single DB called test_db

What should i use in the selection rule ?

Im not very familiar with databases,but i checked ( also in the question body ) and there are 3 schemas ( pg_catalog,information_schema,public ) — Eyal Solomon, Sep 13 '21 at 15:11
Does the above settings give you any errors in cloud watch? is it worth splitting it into 3 task? — NItin Vaja, Sep 14 '21 at 07:10
Hey manged to make it work,but faced another problem..getting error when replicating the data.ERROR: null value in column "name" of relation "users" violates not-null constraint; Error while executing the query but i used INSERT INTO users VALUES(12,'twelve'); — Eyal Solomon, Sep 14 '21 at 09:50
no,chose only to replicate changes and to not drop tables,created a new question if you can check please - thanks ! https://stackoverflow.com/questions/69175814/aws-dms-fails-to-replicate-data — Eyal Solomon, Sep 14 '21 at 10:09

score 1 · Answer 1 · answered Jun 03 '22 at 03:58

1

In my experience, my user didn't have the proper permissions/roles in my source MongoDB. My user couldn't access the schema, nor could it read from the tables, thus the error. If anyone sees this error, I suggest creating a user (or granting your user) with super permissions.

answered Jun 03 '22 at 03:58

Philip Vo

11
1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jun 03 '22 at 14:24
Spot on.. This is usually an error when the user does not have proper permission. This error is because your task, thus the user you are using on the dms task to read the source is not able to find these tables. Also check out the answer above with the kind of selection rule you can use. It would be interesting to check detailed debug logs wherein you can get the exact step where your task is failing. – Mradul Yd Nov 25 '22 at 07:53

score 0 · Answer 2 · answered Oct 08 '21 at 16:51

0

You can pass testDB as the schema.

"rules": [{ "rule-type": "selection", "rule-id": "1", "rule-name": "1", "object-locator": { "schema-name": "test_db", "table-name": "%" }, "rule-action": "include" }]

answered Oct 08 '21 at 16:51

Manu

1

1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Muhammedogz Oct 08 '21 at 20:22

score 0 · Answer 3 · answered Oct 31 '22 at 15:43

I have this error after I set up Selection rules on my migration tasks.

My source and target endpoints test the connection successfully. and I m pretty sure my source database schema and tables name are correct on my Selection rules.

Even I click Action and then modify the Selection rules again, it still showing this error.

However, I fix it by clicking Action and choosing Restart/Reusme, then it works... and migrates the data successfully.

AWS DMS task fails

3 Answers3