# Destination Loading Error Reference

In this reference:

* [Common loading errors](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)

* [Amazon Redshift and Panoply loading errors](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)

* [Databricks Delta Lake loading errors](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#databricks-delta-lake-error-reference)

* [Google BigQuery loading errors](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#google-bigquery-error-reference)

* [Microsoft SQL Server loading errors](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#microsoft-sql-server-error-reference)

* [PostgreSQL loading errors](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#postgresql-error-reference)

* [Snowflake loading errors](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#snowflake-error-reference)

## Common loading errors

The following errors are applicable to multiple or all destinations:

* [Column name \[COLUMN\] is too long for \[DESTINATION\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#column-name-limit)
* [column names from client should not include reserved datatype suffix on \[COLUMN_NAME\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#reserved-data-type-suffix)
* [decimal out of range for \[DESTINATION\] on \[DECIMAL\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#decimal-out-of-range)
* [ERROR: too many columns](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#column-limit-exceeded)
* [Field collision on \[COLUMN_NAME\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#field-name-collision)
* [integer out of range for \[DESTINATION\] on \[INTEGER\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#integer-out-of-range)
* [Table name \[TABLE\] is too long for \[DESTINATION\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#table-name-limit)
* [timestamp out of range for \[DESTINATION\] on \[TIMESTAMP\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#timestamp-out-of-range)

### Column name exceeds destination limit

```
Column name [COLUMN] is too long for [DESTINATION]
```

`Column name [COLUMN] is too long for [DESTINATION]`Column name [COLUMN] is too long for [DESTINATION]

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination object naming |
| **Potential cause(s)** | A column name contains more characters than allowed by the destination. |
| **Suggested action(s)** | <ol> <li>If possible, change the column name in the source to be less than the destination’s limit for column names, or</li> <li>De-select the column in Stitch</li></ol><br><br>If neither solution is feasible, you may need to select a destination with a higher character limit for column names. Refer to the table below for each destination’s column name limits:<br><br><table><tr><td><strong>Destination</strong></td><td><strong>Version</strong></td><td><strong>Limit</strong></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-redshift/reference"><strong>Amazon Redshift</strong></a></td><td>v2</td><td>115 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-s3/reference"><strong>Amazon S3</strong></a></td><td>v1</td><td>None</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/data-world/reference"><strong>data.world</strong></a></td><td>v1</td><td>None</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/databricks-delta/reference"><strong>Databricks Delta Lake (AWS)</strong></a></td><td>v1</td><td>122 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1/reference/"><strong>Google BigQuery</strong></a></td><td>v1</td><td>128 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2/reference/"><strong>Google BigQuery</strong></a></td><td>v2</td><td>128 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-azure-synapse-analytics/reference"><strong>Microsoft Azure Synapse Analytics</strong></a></td><td>v1</td><td>128 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-sql-server/reference/"><strong>Microsoft SQL Server</strong></a></td><td>v1</td><td>128 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/mysql/reference"><strong>MySQL</strong></a></td><td>v1</td><td>64 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/panoply/reference"><strong>Panoply</strong></a></td><td>v2</td><td>115 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/postgresql/reference"><strong>PostgreSQL</strong></a></td><td>v1</td><td>59 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/snowflake/reference"><strong>Snowflake</strong></a></td><td>v1</td><td>251 characters</td></tr></table> |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Table or column contains reserved words

```
column names from client should not include reserved datatype suffix on [COLUMN_NAME]
```

`column names from client should not include reserved datatype suffix on [COLUMN_NAME]`column names from client should not include reserved datatype suffix on [COLUMN\_NAME]

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Stitch object naming |
| **Potential cause(s)** | A table or column contains reserved words. |
| **Suggested action(s)** | Remove the reserved words by re-naming the table or column in the source. |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Decimal out of range

```
decimal out of range for [DESTINATION] on [DECIMAL]
```

`decimal out of range for [DESTINATION] on [DECIMAL]`decimal out of range for [DESTINATION] on [DECIMAL]

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination data type limits |
| **Potential cause(s)** | Decimal data exceeds the destination’s allowed range. |
| **Suggested action(s)** | Remove offending values in the source, or change them to be within the allowed range for the destination type:<br><br><table><tr><td><strong>Destination</strong></td><td><strong>Version</strong></td><td><strong>Range</strong></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-redshift/reference"><strong>Amazon Redshift</strong></a></td><td>v2</td><td><p>Precision must be between 1 and 38; scale must be between 0 and the precision value</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/databricks-delta/reference"><strong>Databricks Delta Lake (AWS)</strong></a></td><td>v1</td><td></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1/reference/"><strong>Google BigQuery</strong></a></td><td>v1</td><td><p>-99999999999999999999999999999.999999999 to 99999999999999999999999999999.999999999</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2/reference/"><strong>Google BigQuery</strong></a></td><td>v2</td><td><p>-99999999999999999999999999999.999999999 to 99999999999999999999999999999.999999999</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-azure-synapse-analytics/reference"><strong>Microsoft Azure Synapse Analytics</strong></a></td><td>v1</td><td><p>Precision must be between 1 and 38; scale must be between 0 and the precision value</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-sql-server/reference/"><strong>Microsoft SQL Server</strong></a></td><td>v1</td><td><p>-99999999999999999999999999999999.999999 to 99999999999999999999999999999999.999999</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/mysql/reference"><strong>MySQL</strong></a></td><td>v1</td><td><p>-99999999999999999999999999999999.999999M to 99999999999999999999999999999999.999999M</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/panoply/reference"><strong>Panoply</strong></a></td><td>v2</td><td><p>Precision must be between 1 and 38; scale must be between 0 and the precision value</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/postgresql/reference"><strong>PostgreSQL</strong></a></td><td>v1</td><td><p>Up to 131,072 digits before the decimal; up to 16,383 digits after</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/snowflake/reference"><strong>Snowflake</strong></a></td><td>v1</td><td><p>Precision must be between 1 and 38; scale must be between 0 and the precision value</p></td></tr></table> |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Table contains too many columns

```
ERROR: too many columns
```

`ERROR: too many columns`ERROR: too many columns

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination object limits |
| **Potential cause(s)** | A table contains more columns than the destination allows. |
| **Suggested action(s)** | De-select columns in Stitch to allow data to continue loading into the destination table.<br><br>Refer to the table below for each destination’s columns per table limit:<br><br><table><tr><td><strong>Destination</strong></td><td><strong>Version</strong></td><td><strong>Limit</strong></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-redshift/reference#destination-details"><strong>Amazon Redshift</strong></a></td><td>v2</td><td>1,600</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-s3/reference#destination-details"><strong>Amazon S3</strong></a></td><td>v1</td><td>None</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/data-world/reference#destination-details"><strong>data.world</strong></a></td><td>v1</td><td>None</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/databricks-delta/reference#destination-details"><strong>Databricks Delta Lake (AWS)</strong></a></td><td>v1</td><td>None</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1/reference/#destination-details"><strong>Google BigQuery</strong></a></td><td>v1</td><td>10,000</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2/reference/#destination-details"><strong>Google BigQuery</strong></a></td><td>v2</td><td>10,000</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-azure-synapse-analytics/reference#destination-details"><strong>Microsoft Azure Synapse Analytics</strong></a></td><td>v1</td><td>1,024</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-sql-server/reference/#destination-details"><strong>Microsoft SQL Server</strong></a></td><td>v1</td><td>1,024</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/mysql/reference#destination-details"><strong>MySQL</strong></a></td><td>v1</td><td>1017</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/panoply/reference#destination-details"><strong>Panoply</strong></a></td><td>v2</td><td>1,600</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/postgresql/reference#destination-details"><strong>PostgreSQL</strong></a></td><td>v1</td><td>250-1,600</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/snowflake/reference#destination-details"><strong>Snowflake</strong></a></td><td>v1</td><td>None</td></tr></table> |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Column name collision

```
Field collision on [COLUMN_NAME]
```

`Field collision on [COLUMN_NAME]`Field collision on [COLUMN\_NAME]

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination object naming |
| **Potential cause(s)** | Two columns are replicated that canonicalize to the same name.<br><br>For example: In Amazon Redshift, Stitch lowercases column names `cUsTomErId` and `customerid` would can |
| **Suggested action(s)** | If possible, re-name one of the columns in the source so that both column names will be unique when replicated to the destination. |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Integer out of range

```
integer out of range for [DESTINATION] on [INTEGER]
```

`integer out of range for [DESTINATION] on [INTEGER]`integer out of range for [DESTINATION] on [INTEGER]

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination data type limits |
| **Potential cause(s)** | Integer data exceeds the destination’s allowed range. |
| **Suggested action(s)** | Remove offending values in the source, or change them to be within the allowed range for the destination type:<br><br><table><tr><td><strong>Destination</strong></td><td><strong>Version</strong></td><td><strong>Range</strong></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-redshift/reference"><strong>Amazon Redshift</strong></a></td><td>v2</td><td><p>-9223372036854775808 to 9223372036854775807</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/databricks-delta/reference"><strong>Databricks Delta Lake (AWS)</strong></a></td><td>v1</td><td></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1/reference/"><strong>Google BigQuery</strong></a></td><td>v1</td><td><p>-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2/reference/"><strong>Google BigQuery</strong></a></td><td>v2</td><td><p>-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-azure-synapse-analytics/reference"><strong>Microsoft Azure Synapse Analytics</strong></a></td><td>v1</td><td><p>-2^63 (-9,223,372,036,854,775,808) to 2^63-1 (9,223,372,036,854,775,807)</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-sql-server/reference/"><strong>Microsoft SQL Server</strong></a></td><td>v1</td><td><p>-2^31 (-2,147,483,648) to 2^31-1 (2,147,483,647)</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/mysql/reference"><strong>MySQL</strong></a></td><td>v1</td><td><p>-2147483648 to 2147483647</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/panoply/reference"><strong>Panoply</strong></a></td><td>v2</td><td><p>-9223372036854775808 to 9223372036854775807</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/postgresql/reference"><strong>PostgreSQL</strong></a></td><td>v1</td><td><p>-2147483648 to +2147483647</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/snowflake/reference"><strong>Snowflake</strong></a></td><td>v1</td><td><p>Limited to 38 digits of scale</p></td></tr></table> |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Table name exceeds destination limit

```
Table name [TABLE] is too long for [DESTINATION]
```

`Table name [TABLE] is too long for [DESTINATION]`Table name [TABLE] is too long for [DESTINATION]

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination object naming |
| **Potential cause(s)** | A table name contains more characters than allowed by the destination. |
| **Suggested action(s)** | <ol> <li>If possible, change the table name in the source to be less than the destination’s limit for table names, or</li> <li>De-select the table in Stitch</li></ol><br><br>If neither solution is feasible, you may need to select a destination with a higher character limit for table names. Refer to the table below for each destination’s table name limits:<br><br><table><tr><td><strong>Destination</strong></td><td><strong>Version</strong></td><td><strong>Limit</strong></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-redshift/reference"><strong>Amazon Redshift</strong></a></td><td>v2</td><td>127 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-s3/reference"><strong>Amazon S3</strong></a></td><td>v1</td><td>1,024 bytes</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/data-world/reference"><strong>data.world</strong></a></td><td>v1</td><td>None</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/databricks-delta/reference"><strong>Databricks Delta Lake (AWS)</strong></a></td><td>v1</td><td>78 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1/reference/"><strong>Google BigQuery</strong></a></td><td>v1</td><td>1,024 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2/reference/"><strong>Google BigQuery</strong></a></td><td>v2</td><td>1,024 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-azure-synapse-analytics/reference"><strong>Microsoft Azure Synapse Analytics</strong></a></td><td>v1</td><td>112 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-sql-server/reference/"><strong>Microsoft SQL Server</strong></a></td><td>v1</td><td>113 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/mysql/reference"><strong>MySQL</strong></a></td><td>v1</td><td>60 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/panoply/reference"><strong>Panoply</strong></a></td><td>v2</td><td>127 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/postgresql/reference"><strong>PostgreSQL</strong></a></td><td>v1</td><td>63 characters</td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/snowflake/reference"><strong>Snowflake</strong></a></td><td>v1</td><td>255 characters</td></tr></table> |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Timestamp out of range

```
timestamp out of range for [DESTINATION] on [TIMESTAMP]
```

`timestamp out of range for [DESTINATION] on [TIMESTAMP]`timestamp out of range for [DESTINATION] on [TIMESTAMP]

| **Applicable to** | All destinations |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination data type limits |
| **Potential cause(s)** | Timestamp data exceeds the destination’s allowed range. |
| **Suggested action(s)** | Remove offending values in the source, or change them to be within the allowed range for the destination type:<br><br><table><tr><td><strong>Destination</strong></td><td><strong>Version</strong></td><td><strong>Range</strong></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/amazon-redshift/reference"><strong>Amazon Redshift</strong></a></td><td>v2</td><td><p>4713 BC to 294276 AD</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/databricks-delta/reference"><strong>Databricks Delta Lake (AWS)</strong></a></td><td>v1</td><td><p>Timestamps before <code>1900-01-01T00:00:00Z</code> are not supported.</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1/reference/"><strong>Google BigQuery</strong></a></td><td>v1</td><td><p>0001-01-01 00:00:00 to 9999-12-31 23:59:59.999999 UTC</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2/reference/"><strong>Google BigQuery</strong></a></td><td>v2</td><td><p>0001-01-01 00:00:00 to 9999-12-31 23:59:59.999999 UTC</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-azure-synapse-analytics/reference"><strong>Microsoft Azure Synapse Analytics</strong></a></td><td>v1</td><td><p><strong>Dates</strong>: 0001-01-01/January 1, 0001 AD, through 9999-12-31/December 31, 9999 AD; <strong>Time</strong>: 00:00:00 through 23:59:59.997</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/microsoft-sql-server/reference/"><strong>Microsoft SQL Server</strong></a></td><td>v1</td><td><p><strong>Date</strong>: 0001-01-01 through 9999-12-31; <strong>Time</strong>: 00:00:00 through 23:59:59.999</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/mysql/reference"><strong>MySQL</strong></a></td><td>v1</td><td><p>1000-01-01 to 9999-12-31</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/panoply/reference"><strong>Panoply</strong></a></td><td>v2</td><td><p>4713 BC to 294276 AD</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/postgresql/reference"><strong>PostgreSQL</strong></a></td><td>v1</td><td><p>4713 BC to 294276 AD</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/snowflake/reference"><strong>Snowflake</strong></a></td><td>v1</td><td></td></tr></table> |

[Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#common-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

## Amazon Redshift and Panoply loading errors

Information note **Note**: The errors in this section are applicable to Amazon Redshift and Panoply destinations.

* [Encountered error while attempting to create new schema.](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#error-schema-creation)
* [ERROR: cannot drop table \[SCHEMA_NAME\].\[TABLE_NAME\] column type because other objects depend on it Hint: Use DROP ... CASCADE to drop...](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#dependent-views)
* [ERROR: Cannot execute query because system is in resize mode Detail: System is in resize mode, and ONLY read-only queries...](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#resize-mode)
* [ERROR: Disk Full Detail: ----------------------------- error: Disk Full code: 1016 context: node: 3 query: 1005177 location: fdisk_api.cpp:345 process: query3_66 \[pid=27629\]...](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#disk-full)
* [ERROR: must be owner of relation \[TABLE_NAME\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#table-owner)
* [ERROR: permission denied for schema \[SCHEMA_NAME\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#schema-permission-denied)
* [FATAL: database "\[DATABASE_NAME\]" does not exist](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#database-does-not-exist)

### Cannot create new schema

```
Encountered error while attempting to create new schema.
```

`Encountered error while attempting to create new schema.`Encountered error while attempting to create new schema.

| **Applicable to** | Amazon Redshift destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Database user privileges |
| **Potential cause(s)** | Stitch is unable to create or load data into a schema in your destination. This is usually due to insufficient database user privileges. |
| **Suggested action(s)** | Verify that the database user authorizing the connection has all the required privileges as outlined in the [Amazon Redshift setup instructions](https://help.qlik.com/en-US/stitch/destinations/redshift/connecting-redshift-data-warehouse-to-stitch#create-database-user). |

[Back to Amazon Redshift error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Dependent views

```
ERROR: cannot drop table [SCHEMA_NAME].[TABLE_NAME] column type because other objects depend on it
Hint: Use DROP ... CASCADE to drop the dependent objects too.
```

`ERROR: cannot drop table [SCHEMA_NAME].[TABLE_NAME] column type because other objects depend on it
Hint: Use DROP ... CASCADE to drop the dependent objects too.`ERROR: cannot drop table [SCHEMA\_NAME].[TABLE\_NAME] column type because other objects depend on it Hint: Use DROP ... CASCADE to drop the dependent objects too.

| **Applicable to** | Amazon Redshift destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | [Dependent views](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/redshift-dependent-view-errors) |
| **Potential cause(s)** | Stitch is attempting to widen a `VARCHAR` column and can’t because a view is built on top of the table. |
| **Suggested action(s)** | Temporarily drop the dependent views, which will allow Stitch to widen the columns. This process usually takes about an hour. |

[Back to Amazon Redshift error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### System is in resize mode

```
ERROR: Cannot execute query because system is in resize mode
Detail: System is in resize mode, and ONLY read-only queries are allowed to execute.
```

`ERROR: Cannot execute query because system is in resize mode
Detail: System is in resize mode, and ONLY read-only queries are allowed to execute.`ERROR: Cannot execute query because system is in resize mode Detail: System is in resize mode, and ONLY read-only queries are allowed to execute.

| **Applicable to** | Amazon Redshift destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | End-user destination change |
| **Potential cause(s)** | Someone adjusted (up or down) the number of nodes of your Amazon Redshift instance and Amazon is currently applying that change. |
| **Suggested action(s)** | This is a transient issue. Stitch should be able to resume loading data once the resize is completed. |

[Back to Amazon Redshift error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Disk is full

```
ERROR: Disk Full Detail:
-----------------------------
error:  Disk Full
code:      1016
context:   node: 3
query:     1005177
location:  fdisk_api.cpp:345
process:   query3_66 [pid=27629]
-----------------------------
```

`ERROR: Disk Full Detail:
-----------------------------
error:  Disk Full
code:      1016
context:   node: 3
query:     1005177
location:  fdisk_api.cpp:345
process:   query3_66 [pid=27629]
-----------------------------`ERROR: Disk Full Detail: ----------------------------- ERROR: Disk Full Detail: ----------------------------- error: Disk Full code: 1016 context: node: 3 query: 1005177 location: fdisk\_api.cpp:345 process: query3\_66 [pid=27629] ----------------------------------------------------------

| **Applicable to** | Amazon Redshift destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Destination disk space |
| **Potential cause(s)** | The Amazon Redshift instance is full. |
| **Suggested action(s)** | <ul> <li>Add additional nodes to make your Amazon Redshift instance larger, or</li> <li>Remove tables and/or data from the existing instance to free up disk space</li></ul> |

[Back to Amazon Redshift error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Insufficient table privileges

```
ERROR: must be owner of relation [TABLE_NAME]
```

`ERROR: must be owner of relation [TABLE_NAME]`ERROR: must be owner of relation [TABLE\_NAME]

| **Applicable to** | Amazon Redshift destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Database user privileges |
| **Potential cause(s)** | Stitch is not the owner of a table in Amazon Redshift, which is required to perform functions necessary to load data. |
| **Suggested action(s)** | Verify that the database user authorizing the connection has all the required privileges as outlined in the [Amazon Redshift setup instructions](https://help.qlik.com/en-US/stitch/destinations/redshift/connecting-redshift-data-warehouse-to-stitch#create-database-user). |

[Back to Amazon Redshift error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Insufficient schema privileges

```
ERROR: permission denied for schema [SCHEMA_NAME]
```

`ERROR: permission denied for schema [SCHEMA_NAME]`ERROR: permission denied for schema [SCHEMA\_NAME]

| **Applicable to** | Amazon Redshift destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Database user privileges |
| **Potential cause(s)** | Stitch does not have privileges to create tables within a schema in Amazon Redshift. |
| **Suggested action(s)** | Verify that the database user authorizing the connection has all the required privileges as outlined in the [Amazon Redshift setup instructions](https://help.qlik.com/en-US/stitch/destinations/redshift/connecting-redshift-data-warehouse-to-stitch#create-database-user). |

[Back to Amazon Redshift error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Database doesn't exist

```
FATAL: database "[DATABASE_NAME]" does not exist
```

`FATAL: database "[DATABASE_NAME]" does not exist`FATAL: database "[DATABASE\_NAME]" does not exist

| **Applicable to** | Amazon Redshift destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Connection settings |
| **Potential cause(s)** | Stitch can’t find the database in Amazon Redshift that has been entered into the Destination Settings page. |
| **Suggested action(s)** | Verify that the correct database is entered in the Destination Settings page of Stitch. |

[Back to Amazon Redshift error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#amazon-redshift-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

## Databricks Delta Lake loading errors

* [The authorization header is malformed; the region '\[STITCH_ACCOUNT_REGION\]' is wrong; expecting '\[S3_BUCKET_REGION\]'](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#s3-bucket-region-mismatch)

### Mismatched Amazon S3 and Stitch account regions

```
The authorization header is malformed; the region '[STITCH_ACCOUNT_REGION]' is wrong; expecting '[S3_BUCKET_REGION]'
```

`The authorization header is malformed; the region '[STITCH_ACCOUNT_REGION]' is wrong; expecting '[S3_BUCKET_REGION]'`The authorization header is malformed; the region '[STITCH\_ACCOUNT\_REGION]' is wrong; expecting '[S3\_BUCKET\_REGION]'

| **Applicable to** | Databricks Delta Lake destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Amazon S3 bucket configuration |
| **Potential cause(s)** | The Amazon S3 bucket isn’t in the same AWS region as your Stitch account. |
| **Suggested action(s)** | Use an Amazon S3 bucket that’s in the same AWS region as your Stitch account. Currently, all Stitch accounts are in the `us-east-1` region. Your S3 bucket must be created in this region to use Databricks Delta Lake as your destination. |

[Back to Databricks Delta Lake error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#databricks-delta-lake-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

## Google BigQuery loading errors

* [Numeric out of range for BigQuery on \[NUMERIC\]](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#numeric-out-of-range)
* [Primary key change is not permitted](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#pk-change-not-permitted)

### Numeric data out of range

```
Numeric out of range for BigQuery on [NUMERIC]
```

`Numeric out of range for BigQuery on [NUMERIC]`Numeric out of range for BigQuery on [NUMERIC]

| **Applicable to** | All Google BigQuery destination versions |
| --- | --- |
| **Level** | Warning<br><br>the Warning 2 icon<br><br>Data has been replicated, but something may require your attention. |
| **Category** | Destination data type limits |
| **Potential cause(s)** | Numeric data exceeds the destination’s allowed range. |
| **Suggested action(s)** | Remove offending values in the source, or change them to be within the allowed range for Google BigQuery:<br><br><table><tr><td><strong>Version</strong></td><td><strong>Range</strong></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v1/reference/">v1</a></td><td><p>-99999999999999999999999999999.999999999 to 99999999999999999999999999999.999999999</p></td></tr><tr><td><a href="https://help.qlik.com/en-US/stitch/destinations/google-bigquery/v2/reference/">v2</a></td><td><p>-99999999999999999999999999999.999999999 to 99999999999999999999999999999.999999999</p></td></tr></table> |

[Back to Google BigQuery error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#google-bigquery-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Primary Key change is not permitted

```
Primary key change is not permitted
```

`Primary key change is not permitted`Primary key change is not permitted

| **Applicable to** | Google BigQuery v2 destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | [Primary Keys](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table) |
| **Potential cause(s)** | The Primary Keys of incoming data don’t match the Primary Keys of the table in the destination.<br><br>This can be caused by:<br><br><ol> <li>The Primary Keys being changed in the source, or</li> <li>The <a href="https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table"><code>_sdc_primary_keys</code> table</a> is altered or dropped</li></ol> |
| **Suggested action(s)** | Reset the table(s) mentioned in the error. This will queue a full re-replication of the table(s), which will ensure Primary Keys are correctly captured and used to de-dupe data when loading. |

[Back to Google BigQuery error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#google-bigquery-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

## Microsoft SQL Server loading errors

* [Incoming Primary Key type does not match Primary Key type in existing table](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#pk-type-change-not-permitted)
* [Incoming Primary Keys do not match Primary Keys in existing table](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#pk-change-not-permitted)

### Primary Key type change is not permitted

```
Incoming Primary Key type does not match Primary Key type in existing table
```

`Incoming Primary Key type does not match Primary Key type in existing table`Incoming Primary Key type does not match Primary Key type in existing table

| **Applicable to** | Microsoft SQL Server destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | [Primary Keys](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table) |
| **Potential cause(s)** | The type of the Primary Key of incoming data doesn’t match the the type of the Primary Key of the table in the destination.<br><br>This can be caused by:<br><br><ol> <li>The Primary Key type being changed in the source, or</li> <li>The <a href="https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table"><code>_sdc_primary_keys</code> table</a> is altered or dropped</li></ol> |
| **Suggested action(s)** | Reset the table(s) mentioned in the error. This will queue a full re-replication of the table(s), which will ensure Primary Keys are correctly captured and used to de-dupe data when loading. |

[Back to Microsoft SQL Server error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#microsoft-sql-server-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Primary Key change is not permitted

```
Incoming Primary Keys do not match Primary Keys in existing table
```

`Incoming Primary Keys do not match Primary Keys in existing table`Incoming Primary Keys do not match Primary Keys in existing table

| **Applicable to** | Microsoft SQL Server destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | [Primary Keys](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table) |
| **Potential cause(s)** | The Primary Keys of incoming data don’t match the Primary Keys of the table in the destination.<br><br>This can be caused by:<br><br><ol> <li>The Primary Keys being changed in the source, or</li> <li>The <a href="https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table"><code>_sdc_primary_keys</code> table</a> is altered or dropped</li></ol> |
| **Suggested action(s)** | Reset the table(s) mentioned in the error. This will queue a full re-replication of the table(s), which will ensure Primary Keys are correctly captured and used to de-dupe data when loading. |

[Back to Microsoft SQL Server error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#microsoft-sql-server-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

## PostgreSQL loading errors

* [Encountered error while attempting to create new schema.](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#cannot-create-schema)
* [ERROR: could not extend file "base/16389/t2_285302": No space left on device Hint: Check free disk space. Where: COPY staging_0_\[FILE_NAME\], line...](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#no-space-on-device)
* [ERROR: could not write block XXXX of temporary file: No space left on device](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#database-is-full)

### Insufficient schema privileges

```
Encountered error while attempting to create new schema.
```

`Encountered error while attempting to create new schema.`Encountered error while attempting to create new schema.

| **Applicable to** | All PostgreSQL-backed destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Database user privileges |
| **Potential cause(s)** | Stitch is unable to create or load data into a schema in your destination. This is usually due to insufficient database user privileges. |
| **Suggested action(s)** | Verify that the Stitch database user has the required permissions, [as outlined here](https://help.qlik.com/en-US/stitch/destinations/postgresql/connecting-a-self-hosted-postgresql-data-warehouse-to-stitch#create-stitch-user). |

[Back to PostgreSQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#postgresql-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Disk is full

```
ERROR: could not extend file "base/16389/t2_285302": No space left on device
Hint: Check free disk space.
Where: COPY staging_0_[FILE_NAME], line [LINE_NUMBER]
```

`ERROR: could not extend file "base/16389/t2_285302": No space left on device
Hint: Check free disk space.
Where: COPY staging_0_[FILE_NAME], line [LINE_NUMBER]`ERROR: could not extend file "base/16389/t2\_285302": No space left on device Hint: Check free disk space. Where: COPY staging\_0\_[FILE\_NAME], line [LINE\_NUMBER]

| **Applicable to** | All PostgreSQL-backed destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Destination disk space |
| **Potential cause(s)** | The PostgreSQL instance is full. |
| **Suggested action(s)** | <ul> <li>Add additional space to make your PostgreSQL database larger, or</li> <li>Remove tables and/or data from the existing instance to free up disk space</li></ul> |

[Back to PostgreSQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#postgresql-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

### Insufficient storage space

```
ERROR: could not write block XXXX of temporary file: No space left on device
```

`ERROR: could not write block XXXX of temporary file: No space left on device`ERROR: could not write block XXXX of temporary file: No space left on device

| **Applicable to** | All PostgreSQL-backed destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Destination disk space |
| **Potential cause(s)** | The PostgreSQL instance is full. |
| **Suggested action(s)** | <ul> <li>Add additional space to make your PostgreSQL database larger, or</li> <li>Remove tables and/or data from the existing instance to free up disk space</li></ul> |

[Back to PostgreSQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#postgresql-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)

## Snowflake loading errors

* [Keys for table do not match Primary Keys of incoming data](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#pk-change-not-permitted)

### Primary Key change is not permitted

```
Keys for table do not match Primary Keys of incoming data
```

`Keys for table do not match Primary Keys of incoming data`Keys for table do not match Primary Keys of incoming data

| **Applicable to** | Snowflake destinations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | [Primary Keys](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table) |
| **Potential cause(s)** | The Primary Keys of incoming data don’t match the Primary Keys of the table in the destination.<br><br>This can be caused by:<br><br><ol> <li>The Primary Keys being changed in the source, or</li> <li>The <a href="https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/primary-keys-system-table"><code>_sdc_primary_keys</code> table</a> is altered or dropped</li></ol> |
| **Suggested action(s)** | Reset the table(s) mentioned in the error. This will queue a full re-replication of the table(s), which will ensure Primary Keys are correctly captured and used to de-dupe data when loading. |

[Back to Snowflake error list](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#snowflake-error-reference)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/destinations/destination-data-loading-errors#)