- Newest
- Most votes
- Most comments
Hello,
I understand you are experiencing issues with your Zero-ETL integration between Postgres RDS and Redshift serverless, where the integration has stopped working unexpectedly. Specifically, you're unable to modify the refresh interval, cannot resync tables, and cannot query ZETL tables. The integration settings appear to be missing from the svv_integration table, and tables are no longer updating, despite the integration working correctly a few days ago.
Firstly, the error "UnknownFailure: No response received from connection manager: {"failurereason":12}" may be due to cluster-level issues. Therefore, it's necessary to examine the cluster parameters.
Secondly, the "Zero-ETL database is not available for querying right now" error usually occurs when zero-ETL integration becomes stuck in a recurring resync state. During this time, queries may not process properly.
Recommendations:
Check the current integration status: SELECT * FROM SVV_INTEGRATION WHERE integration_name = '<your_integration_name>'; If you see the state as CATCHING_UP or ERROR, that means the integration is still trying to sync
To help you further with troubleshooting regarding your error, please open a support case with AWS using the following link:
[+] https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
[+] https://support.console.aws.amazon.com/support/home#/case/create
References:
[+] https://docs.aws.amazon.com/redshift/latest/dg/r_SVV_INTEGRATION.html
[+] https://docs.aws.amazon.com/redshift/latest/mgmt/zero-etl-using.describing.html
I hope above information is helpful.
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
Nothing would have changed regarding network configuration or IAM roles from the time that it was working and the time that it broke. Would be useful if there was a way to get a more descriptive error message. Most of what is posted is above is from the documentation which I have already gone through. This error does not seem to be mentioned anywhere in the available AWS docs on ZETL.