Below is a list of the most common errors that Stitch will encounter when attempting to load data into your Redshift data warehouse.
Please note:
- This isn’t an exhaustive list. If you receive an error that isn’t listed here and need help troubleshooting, please reach out to our support team.
- The info in this article is also applicable to Panoply data warehouses, as Panoply uses Redshift.
Tip: Quickly find the fix for the error by entering keywords in the Search box above the table.
| Error Message | Interpretation | Fix |
|---|---|---|
ERROR: must be owner of relation [table_name] |
Stitch is not the owner of tables in Redshift, which is needed to perform functions necessary to loading data. | Verify that the Stitch user has all the required permissions as outlined in this article. |
ERROR: permission denied for schema [schema_name] |
Stitch does not have permissions to create tables within a schema in Redshift. | Verify that the Stitch user has all the required permissions as outlined in this article. |
FATAL: password authentication failed for user "stitch_user" |
The credentials that Stitch has for your Redshift instance are incorrect. | Verify that the correct password for the user Stitch is using to connect to Redshift is entered in the Destination Settings page of Stitch. |
FATAL: database "database_name" does not exist |
Stitch can't find the database in Redshift it has been configured to use. | Verify that the correct database is entered in the Destination Settings page of Stitch. You can also perform a connection check in this page. |
| Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. | Stitch can't connect to the Redshift instance, most likely due to firewall configurations. | Verify that your VPC settings in AWS are configured correctly as outlined in this article. |
| The connection attempt failed. | Stitch cannot connect to the Redshift instance. | Verifying and testing your Redshift configuration in the Destination Settings page of Stitch. |
| An I/O error occured while sending to the backend. | Something went wrong during the communication with Redshift. | This is a transient error, and should clear itself during the next re-sync. |
| 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. |
Someone adjusted (up or down) the number of nodes of your Redshift instance and Amazon is currently applying that change. | This is a transient issue - Stitch should be able to resume syncing data once the resize is completed. |
ERROR: cannot drop table SCHEMA.TABLE column type because other objects depend on itHint: Use DROP ... CASCADE to drop the dependent objects too. |
Stitch is attempting to widen VARCHAR columns in Redshift and can't because a view is built on top of the table. |
Temporarily dropping the dependent views, which will allow Stitch to widen the columns. This process usually takes about an hour. |
|
ERROR: Disk Full Detail: ----------------------------- error: Disk Full code: 1016 context: node: 3 query: 1005177 location: fdisk_api.cpp:345 process: query3_66 [pid=27629] ----------------------------- |
Your Redshift instance is full. |
|
Contacting Support
If you still encounter trouble after following the troubleshooting steps above, please reach out to support for assistance.
Questions? Feedback?
Did this article help? If you have questions or feedback, please reach out to us.