Stitch Documentation
has moved!

Please update your bookmarks to https://www.stitchdata.com/docs

If you're not automatically redirected after 5 seconds, click here.

Redshift: Troubleshooting Data Warehouse Errors

Important!
The info in this doc only applies to the Redshift (and Panoply) destinations.

If you're using a different destination, refer to this doc to find the relevant troubleshooting steps for that destination.

Below is a list of the most common errors that Stitch will encounter when attempting to load data into your Amazon Redshift data warehouse.

Note that 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.

Message received: This means: Fix it by:
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. Verifying that the Stitch user has all the required permissions as outlined in this doc.
ERROR: permission denied for schema [schema_name] Stitch does not have permissions to create tables within a schema in Redshift. Verifying that the Stitch user has all the required permissions as outlined in this doc.
FATAL: password authentication failed for user "stitch_user" The credentials that Stitch has for your Redshift instance are incorrect. Verifying 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. Verifying 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. Verifying that your VPC settings in AWS are configured correctly as outlined in this doc.
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 it

Hint: 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.
  • Adding additional nodes to make your Redshift instance larger, OR
  • Removing tables and/or data from the existing instance to free up disk space.
Was this article helpful?
0 out of 0 found this helpful

Comments

Questions or suggestions? If something in our documentation is unclear, let us know in the comments!