Issue in syncing table in ZETL in redshift target

This error occurs because the column length in your Redshift target table doesn't match the length required for the data coming from your PostgreSQL source.

When tables require resynchronization in zero-ETL integrations, they enter a "Syncing" state and won't be accessible in Amazon Redshift during this period. Your specific error indicates that column 76 in your data has a length of 60 characters, but the target table definition in Redshift has a smaller limit.

To resolve this issue, you have a few options:

1. Use the ALTER DATABASE command with the INTEGRATION REFRESH TABLES statement to resynchronize the specific table:

ALTER DATABASE dbname INTEGRATION REFRESH TABLES table_name;

This will trigger a resynchronization that might properly adjust the column definition.

2. If the issue persists, you may need to manually ensure that the target table in Redshift has the appropriate column length. For the "access_name" column, make sure it's defined as VARCHAR(1000) in Redshift to match your PostgreSQL source.

3. For tables that fail to replicate properly, they will display as "Failed" in the monitoring dashboard, and the overall zero-ETL integration status will change to "Needs attention." Check the monitoring dashboard to confirm the status.

If you continue to experience issues, you might need to review the parameter settings for your source database to ensure they're correctly configured for zero-ETL integration.
Sources
Amazon RDS for MySQL - Redshift Cluster Zero-ETL Integration: schema change | AWS re:Post
Troubleshooting Amazon RDS zero-ETL integrations with Amazon Redshift - Amazon Relational Database Service