# Sync – “Failed to cache row \[xxxxx\] Array dimensions exceeded supported range” error

**URL:** <https://community.cdata.com/t/sync-failed-to-cache-row-xxxxx-array-dimensions-exceeded-supported-range-error/418>\
**Category:** Editions\
**Tags:** article, cdata-sync\
**Created:** [September 25, 2023, 9:20pm UTC](https://community.cdata.com/t/sync-failed-to-cache-row-xxxxx-array-dimensions-exceeded-supported-range-error/418 "2023-09-25T21:20:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ergesta\_R](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@Ergesta\_R](https://community.cdata.com/u/Ergesta_R)\
**Post date:** [September 25, 2023, 9:20pm UTC](https://community.cdata.com/t/sync-failed-to-cache-row-xxxxx-array-dimensions-exceeded-supported-range-error/418/1 "2023-09-25T21:20:53Z")

</div>

This error commonly arises during the replication of very large tables, indicating that the table contains more records than the internal mechanism can effectively track.

Our REPLICATE command stores extra duplicate checks and Sync keeps a list of primary keys to facilitate these checks. Depending on the size of the tables involved, this side of the replication may overflow, resulting in the above error.

To resolve this issue, you can disable duplicate checks by setting the ‘_EnableDuplicateProtection_’ property to _False_ in the Job Additional Options, as shown in the following screenshots:

 ![e9cd0d89-0c0f-431d-a5cf-85b658759e96.png](https://us1.discourse-cdn.com/cdata/original/2X/a/ab304a4d91c28b4c871fbebe65fc5a29ba96af66.png)

 ![63cef439-e9b7-436b-9900-fe918a1d9cf6.png](https://us1.discourse-cdn.com/cdata/original/2X/5/586bbe3b016925ca62adfed9bf1e869a65f8bbc4.png)

This will help you bypass the error.

Please reach out to [support@cdata.com](mailto:support@cdata.com) if this does not resolve the problem for you.