- Newest
- Most votes
- Most comments
Hello,
Thank you for reaching us. I understand that you have noticed that a small number of records to remain in "pending" state after full load completion and sometimes reloading the table will resolve the issue. While the specific issue needs to be investigated upon by the Premium Support Engineer, a probable reason can be due to the presence of rows which are being continuously modified at the source during validation; then AWS DMS can't validate those rows.
Besides, we also have an option to manually validate the tables again by clicking on the 'Validate again' button on the task console. This will work for a full load and cdc dms task and a cdc only dms task but not for a full load only dms task.
I will also recommend you to let the task run with these pending records for a while to see if they are marked as 'Mismatched records' and then you can make use of the 'awsdms_validation_failures_v1' control table at the target to look them up:
[+] AWS DMS data validation - Troubleshooting - https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Validating.html#CHAP_Validating.Troubleshooting
Relevant content
- asked 5 years ago
- asked 4 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago