DMS Task has started Logging "Resolving object ID by partition ID could not be accomplished for partition"

Question

Greetings,

We recently periodically started seeing the following warning in one of our DMS Task logs:

Task is on-premises SQL Server --> RDS/SQL Server

**[SOURCE_CAPTURE ]W: Resolving object ID by partition ID could not be accomplished for partition 72057674308190208 (sqlserver_log_utils.c:3571)**

Is this safe to ignore? Search could only return very general info indicating that this may have something to do with replicating partitioned table from a source SQL Server.

The task is not in an errors state and data is replicating normally.

I am unaware of any partitioned tables begin captured at the source and the query below returns no records.

```
select distinct t.name
from sys.partitions p
inner join sys.tables t
on p.object_id = t.object_id
where p.partition_number <> 1
```

re:Post Agent · Accepted Answer

This warning message "Resolving object ID by partition ID could not be accomplished for partition" is related to how AWS DMS processes SQL Server tables during Change Data Capture (CDC) operations.

When running CDC on SQL Server tables, AWS DMS parses the SQL Server transaction logs (tlogs) and needs to understand the table structure, including any partitioning information. During this process, DMS reads table metadata from SQL Server system tables to identify column properties and internal structures.

Even though your query didn't return any explicitly partitioned tables, SQL Server internally uses partitioning for various objects, including heaps and indexes. The warning you're seeing might be related to an internal SQL Server partition that DMS is encountering during the log parsing process.

This warning is generally safe to ignore if:
1. Your migration is proceeding normally
2. Data is being replicated correctly
3. You don't see any actual errors or task failures

If you're concerned about the warning, you might want to check:
- Permissions: Ensure the SQL Server user account used for DMS has the "VIEW SERVER STATE" permission
- SQL Server configuration: Verify CDC is properly enabled on the source database
- Lock issues: In some cases, DMS operations can cause lock contention, which might indirectly relate to partition handling

If the migration is otherwise working correctly, this warning can typically be ignored as it appears to be informational rather than indicating a critical problem with your replication task.  
**Sources**  
[Why I'm receiving dm_db_partition_stats is not supported on DMS task with Sql Server as source? | AWS re:Post](https://repost.aws/questions/QU1AXxgGb5Q8S2O82eVM8CBw/why-i-m-receiving-dm-db-partition-stats-is-not-supported-on-dms-task-with-sql-server-as-source)  
[Troubleshooting migration tasks in AWS Database Migration Service - AWS Database Migration Service](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Troubleshooting.html)  
[On-Prem to RDS SQL Server Replication - Can't Get Exclusive Lock Due to Incoming DMS CDC Churn | AWS re:Post](https://repost.aws/questions/QUZjSqDv85Rm2nxOxNlg_lgQ/on-prem-to-rds-sql-server-replication-can-t-get-exclusive-lock-due-to-incoming-dms-cdc-churn)

DMS Task has started Logging "Resolving object ID by partition ID could not be accomplished for partition"

Add your answer

Relevant content