Below is a list of the most common errors that Stitch will encounter when attempting to load data into your Redshift data warehouse.
- 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.
|ERROR: must be owner of relation
||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
||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
||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.|
||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.|
|Encountered error while attempting to create new schema.||Stitch is unable to create or load data into a schema in your data warehouse.||Verify that the Stitch database user has the required permissions, as outlined here.|
|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.||Verify and test 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
|Stitch is attempting to widen
||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
context: node: 3
process: query3_66 [pid=27629]
|Your Redshift instance is full.||
If you still encounter trouble after following the troubleshooting steps above, please reach out to support for assistance.