On-prem Oracle to Aurora Postgres Migration using SCT/DMS

Question

HI,

I am trying to migrate the tables from on-prem Oracle to Aurora Postgres using AWS DMS.My load was successful but there are few errors when I checked through table statistics:
1. There are few tables which looks not validated because of missing primary/Unique keys at source side. Any recommendations for task or validation settings to make sure table is migrated successfully.
2. There are few tables, migrated successfully but table statics says "Mismatched records" and Validationfailed: 1. When I compare the rows on both side, data seems ok. There is no missing rows or data mismatch. 
3. There are tables with millions of rows where table statistics days:Mismatched records and validationfailed: 150. It would be difficult to compare all the rows with data.

As per "awsdms_validation_failures_v1" Some of the tables have "missing source" and some of the tables have "Missing Target" but there is no as such details provided.

Do I need to skip these errors as task was competed successfully or need to make some changes in task settings. If anyone can provide best recommendations.

As of Now, I am running full load with truncate table, Limited LOb:32.
FYI: In one of the table I have re-run the task with single table and targetmode :drop and create. It was successful without any validation error.

Subhash Raut · Answer

For the first issue table cannot be validated due to missing pk/uk, one workaround could be to add temporary pk on source table and reload the table. Post migration this can be removed.

For the second/third issue seems to be collation difference you could use setting HandleCollationDiff and revalidate the tables.

```

"ValidationSettings": {
     "EnableValidation": true,
     "ThreadCount": 10,
     "HandleCollationDiff": true,
...
...            
```

On-prem Oracle to Aurora Postgres Migration using SCT/DMS

Add your answer

Relevant content