1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I have faced a similar issue before. You can raise a support ticket with AWS to help address the issue.
Meanwhile, here are some options.
- Remove the table from your validation list. You can verify it using SQL queries and hash function later.
- If you know the reason for the mismatch, you can adjust for it using modified validation rules (see section titled Using JSON editor to modify validation rules).
- If the mismatch is due to charset, you can adjust it using Character substitution task settings
- You can use a combination of the 1,2, and 3. For example, you can validate the length of the column using validation settings but then validate the content later using hash function.
Please let us know how you handled it.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Regarding "Remove the table from your validation list. You can verify it using SQL queries and hash function later.", is this even supported in DMS? As per the Mapping rules, excluding selective columns/tables remove those from the migration as well. How can we keep these columns/tables in migration but exclude from validation only?