1 回答
- 最新
- 投票最多
- 评论最多
0
-Verify the mapping rules and filters defined in the DMS task. Make sure all the required tables are included as per the filters. -Check the IAM role used by DMS has necessary permissions to read from the source and write to the target S3 bucket. -Go through the replication logs and check for any errors while loading data for specific tables. -Monitor the table statistics section in DMS console - it should list all tables being replicated along with load status. -Try running a smaller subset of tables as a test to isolate the issue.
As a workaround, you can also load the full database dump file directly to S3 using AWS Database Migration Service instead of replicating individual tables.
相关内容
- AWS 官方已更新 6 个月前
- AWS 官方已更新 7 个月前
- AWS 官方已更新 2 年前
Can you pls. elaborate more on the issue? What;s the exact issue