Skip to content

AWS DMS Serverless No tables were found when using parallel-load

0

I'm running AWS DMS Serverless replication between two different AWS Aurora Mysql databases. Here example fragment of my mapping rules json:

    {
      "rule-id": "336",
      "rule-name": "336",
      "rule-type": "selection",
      "rule-action": "include",
      "object-locator": {
        "schema-name": "xyz",
        "table-name": "table_name"
      },
      "filters": []
    },
    {
      "rule-type": "table-settings",
      "rule-id": "0336",
      "rule-name": "0336",
      "object-locator": {
        "schema-name": "xyz",
        "table-name": "table_name"
      },
      "parallel-load": {
        "type": "ranges",
        "columns": [
          "ID"
        ],
        "boundaries": [
          ["8000000"],
          ["10000000"],
          ["20000000"],
          ["30000000"],
          ["40000000"],
          ["50000000"],
          ["60000000"],
          ["70000000"],
          ["80000000"]
        ]
      }
    },

In this case replication fails with following error:

Last Error No tables were found at Replication initialization. Either the selected table(s) or schemas(s) no longer exist or no match was found for the table selection pattern(s). If you would like to start a Replication that does not initially capture any tables, set Replication Setting FailOnNoTablesCaptured to false and restart Replication. Stop Reason FATAL_ERROR Error Level FATAL

When I remove table-settings rule leaving only the selection rule, it correctly finds the tables and runs the replication.

Does AWS DMS Serverless support parallel-load? How can I make it work?

  • Please accept the answer if it was useful

2 Answers
0

Is it working fine on a provisioned dms task?

AWS
answered 2 years ago
-1
EXPERT
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.