- 最新
- 投票最多
- 评论最多
hello there.
I hear the DMS task is running with errors. This could be due to multiple reasons. Please kindly ensure check the below:
DMS task table statistics. This will help see which tables failed Full Load phase as this can cause "running with errors"
Turn on logging level to detailed debug for SOURCE_UNLOAD and TARGET_LOAD to see more information on table failures.
Ensure that the DMS replication instance has enough resource for the DMS task (.i.e. CPU, Storage, Memory)
Filter through the DMS task log and try find log entry with "]E:" or "]W:" this will display DMS task errors and warnings.
If the above does not work, please try testing with a Full load only DMS task. If the issue persists further please open a support case with AWS Premium Support to get an in-depth look at the DMS task failure
references:
to migrate using MongoDB as a source for AWS DMS for example there are permissions needed which can be found in the below document and other requirements too can be found on the below document [1]https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MongoDB.html
to migrate using postgres as a target there are also requirements that needs to be considered can be found on document below [1]https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.PostgreSQL.html
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前