- Newest
- Most votes
- Most comments
Could you please review the execution logs of the zero-ETL process to identify any errors, warnings, or other messages that might provide clues about why it is ending prematurely. Look for any exceptions or failures that could be causing the process to stop unexpectedly.
There no Logging mechanism for zero-ETL Nothing any clue to find why it is stopping after few days, even integration are Active on both side.
There no Logging mechanism for zero-ETL, and Nothing any clue to find why it is stopping after few days, even zero-ETL are Active on both side.
Hi, if you want to see some of the information about the state of the sync of the tables you can use this query:
SELECT * FROM SVV_INTEGRATION_TABLE_STATE
You can also if your tabels are been stuck in failed try to restart the Sync with either:
This only takes the tables that are in error: ALTER DATABASE your-database-name INTEGRATION REFRESH INERROR TABLES IN SCHEMA your-scheme-name;
This just takes all tables: ALTER DATABASE your-database-name INTEGRATION REFRESH ALL tables;
e.g. see more here:
https://docs.aws.amazon.com/redshift/latest/mgmt/zero-etl-using.describing.html
Hope it can help
Relevant content
- Accepted Answerasked 9 months ago
- asked 9 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- What happens to Amazon RDS and Amazon Redshift queries that are running during a maintenance window?AWS OFFICIALUpdated 4 months ago
Could you please review the execution logs of the zero-ETL process to identify any errors, warnings, or other messages that might provide clues about why it is ending prematurely. Look for any exceptions or failures that could be causing the process to stop unexpectedly.